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
Dubai’s afternoon meets London’s morning
At 13:00 Dubai on 27 October 2026, London reads 09:00. Illustrative 09:00–17:00 schedules overlap until 17:00 Dubai, giving four hours. A late Dubai start can still overrun that limit, so compare the full meeting rather than just the shared hour labels.
Compare the same local start on four dates
09:00 in Dubai, resolved separately on each date with IANA 2026f. The final column describes London relative to Dubai.
Dubai
London
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 05:00
4 hours behind
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 06:00
3 hours behind
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 05:00
4 hours behind
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 05:00
4 hours behind
Find a window for the whole meeting
London’s July offset reduces the gap from four hours to three. A London-anchored recurring meeting can therefore move on the Dubai clock across the year. Keep each participant’s working days explicit; the planner does not derive a workweek from the country or city.
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.