Different city label, shared Indian rule identifier
New Delhi and Mumbai both map to Asia/Kolkata. Their local clock values match in this data, while their city labels preserve which participants you mean. You can give the two rows different working days or hours even when their clocks are identical; availability belongs to the participant’s row.
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 |
A Dubai call needs the half-hour boundary
On 27 October 2026, 09:00 in Dubai is 10:30 in New Delhi. A ninety-minute call ends at 12:00 New Delhi, not 11:30. Keep the duration in minutes and inspect the end time in the exported table before sharing a calendar file.
Build a plan for this city
Select New Delhi, 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.