Time zone research

Why Sydney Drifted Twice as Far as London in Our 2026 Model

The repository's 2026 model fixes a weekly meeting to Vancouver local time and records how that meeting appears in selected target zones. Within that bounded model, London uses two distinct shifts with a 60-minute spread, while Sydney uses three shifts with a 120-minute spread. The difference comes from the recorded transition dates for these three zones.

By BeanNest Studio Reviewed September 20, 2026

What this guide helps you decide

Why did the selected Vancouver-to-Sydney pairing span 120 minutes while the selected Vancouver-to-London pairing spanned 60 in the 2026 evidence file?

This research explains two measured 2026 pairings in the repository's selected ten-zone evidence set. It does not claim a universal northern-versus-southern ratio, describe every southern zone, estimate how teams choose meeting anchors, or recommend a scheduling policy.

Try it on the anchor product: BeanNest Time /, BeanNest Time /meeting-planner/.

The measured London and Sydney result

Against the Vancouver anchor, London records shifts of 420 and 480 minutes for a 60-minute spread. Sydney records 1020, 1080, and 1140 minutes for a 120-minute spread. Those figures are the exact comparison this guide explains.

The three zones change on different 2026 dates

The evidence records Vancouver transitions in March and November, London transitions later in March and October, and Sydney transitions in April and October. The London changes sit in the same northern part of the year as Vancouver's, while Sydney's daylight-saving season occupies the opposite part of the calendar.

Sydney's separated changes produce three shift states

Because Vancouver and Sydney change offset at separate times, the pairing visits one relative offset before a change, another while only one zone has changed, and another after the other transition. The evidence file records those three states directly as 1020, 1080, and 1140 minutes.

London stays within two recorded shift values

The Vancouver-to-London pairing in the same model records only 420 and 480 minutes. Its 60-minute spread is therefore half the measured Sydney spread, but that statement is about these selected 2026 pairings rather than a universal hemisphere rule.

No-DST targets still move when the Vancouver anchor changes

Tokyo and Kolkata each record a 60-minute spread against Vancouver even though those target zones have no transitions in the evidence file. That shows why the anchor's own offset changes must be included when interpreting a target-zone result.

The artifact makes the comparison reproducible

For each selected zone, the evidence stores January and July offsets, transition counts, transition instants, and from/to offsets. The recurring-meeting section then stores each target's distinct shifts and spread, so the London and Sydney comparison can be checked from the file rather than inferred from the prose.

What the selected model cannot generalize

The evidence covers ten selected zones and one 2026 Vancouver-anchored weekly-meeting model. It does not establish how most tools or teams choose anchors, what every southern zone does, or what any participant should do around a transition.

First-party evidence and provenance

How we checked this

We derived every offset and transition from the runtime's own time-zone database by sampling the zone offset hourly across the calendar year, then modelled a weekly meeting pinned to a fixed local wall-clock time in a reference zone. The generator is in this repository and the evidence file is its output. For this guide we compare only the Vancouver-to-London and Vancouver-to-Sydney 2026 recurring-meeting rows and their recorded transition dates. We do not generalize those two pairings into a population estimate.

Method: We derived every offset and transition from the runtime's own time-zone database by sampling the zone offset hourly across the calendar year, then modelled a weekly meeting pinned to a fixed local wall-clock time in a reference zone. The generator is in this repository and the evidence file is its output.
Environment: Node.js on a desktop workstation, using the bundled IANA time-zone data. No network call, no hard-coded offset table, and no user data.
Captured: September 20, 2026
Reviewed by: BeanNest Studio

Repository evidence artifacts:

tools/research-evidence/time/transitions-2026.json
tools/research-evidence/time/README.md