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 half-hour defines the edge of the window
Mumbai is five hours and thirty minutes ahead of London on 27 October 2026. At 09:00 London, Mumbai reads 14:30. With illustrative 09:00–17:00 hours, the shared interval lasts until 11:30 London, making its exact half-hour boundary relevant to the duration.
Compare the same local start on four dates
09:00 in London, resolved separately on each date with IANA 2026f. The final column describes Mumbai relative to London.
London
Mumbai
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 14:30
5 hours 30 minutes ahead
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 13:30
4 hours 30 minutes ahead
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 14:30
5 hours 30 minutes ahead
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 14:30
5 hours 30 minutes ahead
Find a window for the whole meeting
A 90-minute meeting can start at 09:00 London and end at 16:00 Mumbai, while a 10:30 London start would overrun the Mumbai limit. In July, London’s different offset changes the gap to four and a half hours. Keep minutes and the selected date in every comparison.
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.