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
Review the Australian weekday, not just the hour
At 09:00 Los Angeles on 27 October 2026, Sydney reads 03:00 on 28 October. An afternoon Pacific meeting can therefore fall in Sydney’s following morning. A Friday Los Angeles plan may reach Saturday in Sydney, when a Monday–Friday availability setting should reject it.
Compare the same local start on four dates
09:00 in Los Angeles, resolved separately on each date with IANA 2026f. The final column describes Sydney relative to Los Angeles.
Los Angeles
Sydney
Time difference
2026-01-15 · 09:00
Fri, 16 Jan 2026 · 04:00
19 hours ahead
2026-07-15 · 09:00
Thu, 16 Jul 2026 · 02:00
17 hours ahead
2026-10-27 · 09:00
Wed, 28 Oct 2026 · 03:00
18 hours ahead
2026-11-03 · 09:00
Wed, 4 Nov 2026 · 04:00
19 hours ahead
Find a window for the whole meeting
For Tuesday 27 October and illustrative weekday hours of 09:00–17:00, the shared interval is 15:00–17:00 Los Angeles and 09:00–11:00 Sydney on Wednesday. A 90-minute meeting fits only with a start no later than 15:30 Los Angeles. Recheck the window after either city changes offset.
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.