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
Tuesday in New York can be Wednesday in Sydney
On 27 October 2026, 09:00 New York is 00:00 on 28 October in Sydney. The following Tuesday at 09:00 New York is 01:00 on Wednesday in Sydney. Both occurrences must carry the Sydney date when the team reviews the schedule.
Compare the same local start on four dates
09:00 in New York, resolved separately on each date with IANA 2026f. The final column describes Sydney relative to New York.
New York
Sydney
Time difference
2026-01-15 · 09:00
Fri, 16 Jan 2026 · 01:00
16 hours ahead
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 23:00
14 hours ahead
2026-10-27 · 09:00
Wed, 28 Oct 2026 · 00:00
15 hours ahead
2026-11-03 · 09:00
Wed, 4 Nov 2026 · 01:00
16 hours ahead
Find a window for the whole meeting
Two illustrative 09:00–17:00 days have no overlap in these examples. A correct midnight conversion should not be presented as a recommended working-hour slot. Discuss an early or late exception with the participants, consider alternating the inconvenience, and verify every occurrence before exporting.
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.