The minutes are part of the time
A time-zone offset does not have to be a whole number of hours. Mumbai and New Delhi use Asia/Kolkata, which is UTC+05:30 on the displayed 2026 dates. Treating that as five or six hours would move a conversion by thirty minutes. The correct result keeps both components.
Work through a London example
On 27 October 2026, London is UTC+00:00. London’s 09:00 is 14:30 in Mumbai, and London’s 11:30 is 17:00 in Mumbai. If both participants offer illustrative 09:00–17:00 hours, the complete common interval is 09:00–11:30 London, corresponding to 14:30–17:00 Mumbai.
A ninety-minute meeting at 10:00 London ends at 11:30 London and 17:00 Mumbai, fitting exactly. Moving it to 10:15 London would overrun the Mumbai finish by fifteen minutes. A timeline with whole-hour tick marks still needs precise minute-based selection and a text table.
Do not round the duration or the destination
The event duration remains ninety minutes in both places. The offset changes the local labels, not the elapsed length. Use a duration field measured in minutes and read the displayed end times before exporting. A two-column note that lists only “London 10, Mumbai 15” would lose information that changes the plan.
The other city can change the gap
In the July 2026 sample, London uses UTC+01:00 while Mumbai remains UTC+05:30. The difference is then four hours and thirty minutes. A London-anchored weekly meeting can move on the Mumbai clock even though the Mumbai offset has not changed. Preview the dates around London’s transition.
Keep the named zone with the plan
The city label explains which participant you mean, and Asia/Kolkata explains the rules used. Mumbai and New Delhi can occupy separate rows with different availability while sharing those clock rules. Save the project if you need to preserve that distinction, and export the resolved instant once the participants agree.
Sources
Follow the original references for the rules and formats used in this guide.