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
The Australian offset changes the Asian handover
Sydney is three hours ahead of Singapore in the January and late-October 2026 samples, but two hours ahead in July. A 09:00 Singapore start reaches 12:00 Sydney on 27 October. If Sydney needs the same local start year-round, choose Sydney as the recurring anchor.
Compare the same local start on four dates
09:00 in Singapore, resolved separately on each date with IANA 2026f. The final column describes Sydney relative to Singapore.
Singapore
Sydney
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 12:00
3 hours ahead
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 11:00
2 hours ahead
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 12:00
3 hours ahead
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 12:00
3 hours ahead
Find a window for the whole meeting
On the October example, illustrative 09:00–17:00 hours overlap from 09:00 to 14:00 Singapore, or 12:00 to 17:00 Sydney. A long workshop needs an early start in that interval. The July window has a different edge, so save the actual date with the plan.
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.