Planning dates run from Thu, Jan 1, 2026 through Mon, Dec 31, 2035. Future rules can be revised; review the data version when a distant schedule matters.
More context and planning advice
Put both local dates in the invitation
At 09:00 London on 27 October 2026, Sydney reads 20:00 on the same day. At 17:00 London it is already 04:00 the following day in Sydney. The pair needs an explicit date label whenever the London meeting approaches evening.
Compare the same local start on four dates
09:00 in London, resolved separately on each date with IANA 2026f. The final column describes Sydney relative to London.
London
Sydney
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 20:00
11 hours ahead
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 18:00
9 hours ahead
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 20:00
11 hours ahead
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 20:00
11 hours ahead
Find a window for the whole meeting
With illustrative 09:00–17:00 hours in both cities, there is no shared window on this October date. A practical discussion might start by asking whether an early London or late Sydney exception is acceptable, then rotating that burden if the meeting recurs. The tool cannot infer that agreement.
Make the plan specific
Enter each participant’s actual working days and hours. The 09:00–17:00 examples here are editable assumptions, not local business-hour facts.
Choose a duration from 15 to 240 minutes and check both local end times.
For a weekly meeting, choose one anchor city and review all twelve dates. Resolve repeated or missing local times explicitly.
Reversing the base city changes how you enter the meeting, not the pair’s information page. Share the configuration or export the resolved event after the participants agree on the time.