A ninety-minute gap is easy to preserve exactly
New Delhi is one hour and thirty minutes ahead of Dubai on all four sampled dates. At 09:00 Dubai, New Delhi reads 10:30. Two illustrative 09:00–17:00 schedules share the interval from 09:00 to 15:30 Dubai, or 10:30 to 17:00 New Delhi.
Compare the same local start on four dates
| Dubai | New Delhi | Time difference |
|---|---|---|
| 2026-01-15 · 09:00 | Thu, 15 Jan 2026 · 10:30 | 1 hour 30 minutes ahead |
| 2026-07-15 · 09:00 | Wed, 15 Jul 2026 · 10:30 | 1 hour 30 minutes ahead |
| 2026-10-27 · 09:00 | Tue, 27 Oct 2026 · 10:30 | 1 hour 30 minutes ahead |
| 2026-11-03 · 09:00 | Tue, 3 Nov 2026 · 10:30 | 1 hour 30 minutes ahead |
Find a window for the whole meeting
A 90-minute meeting starting at 14:00 Dubai ends exactly at 17:00 New Delhi. Starting half an hour later would not fit. The absence of a sampled seasonal difference does not remove the need to check weekdays, user-entered hours, and the complete duration.
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.