Keep the thirty minutes in every row
Mumbai maps to Asia/Kolkata and uses UTC+05:30 on the displayed dates. At 09:00 Mumbai on 27 October 2026, London reads 03:30 and Singapore reads 11:30. Rounding the offset to five or six hours would move the meeting by thirty minutes for everyone else.
A dated view of the local clock
| UTC date | UTC offset | Abbreviation | Local date and time |
|---|---|---|---|
| 2026-01-15 | UTC+05:30 | IST | Thu, 15 Jan 2026 · 18:30 |
| 2026-07-15 | UTC+05:30 | IST | Wed, 15 Jul 2026 · 18:30 |
| 2026-10-27 | UTC+05:30 | IST | Tue, 27 Oct 2026 · 18:30 |
| 2026-11-03 | UTC+05:30 | IST | Tue, 3 Nov 2026 · 18:30 |
Use a late-afternoon India example for London
At 14:30 Mumbai on 27 October, London reaches 09:00. With illustrative 09:00–17:00 hours in both places, the shared window ends at 17:00 Mumbai, leaving two and a half hours. Review the same plan in July, when London’s different offset changes that window.
Build a plan for this city
Select Mumbai, add the other participants, and enter the actual meeting date. The planner uses Asia/Kolkata; the abbreviation in the table is a display label. Adjust working days, hours, and meeting length before choosing a shared window. The supported planning range is 2026–2035.