Nine and a half hours is already beyond two standard days
Mumbai is nine hours and thirty minutes ahead of New York on 27 October 2026. At 09:00 New York it is 18:30 Mumbai, outside an illustrative 09:00–17:00 day. A 90-minute meeting would end at 20:00 in Mumbai.
Compare the same local start on four dates
| New York | Mumbai | Time difference |
|---|---|---|
| 2026-01-15 · 09:00 | Thu, 15 Jan 2026 · 19:30 | 10 hours 30 minutes ahead |
| 2026-07-15 · 09:00 | Wed, 15 Jul 2026 · 18:30 | 9 hours 30 minutes ahead |
| 2026-10-27 · 09:00 | Tue, 27 Oct 2026 · 18:30 | 9 hours 30 minutes ahead |
| 2026-11-03 · 09:00 | Tue, 3 Nov 2026 · 19:30 | 10 hours 30 minutes ahead |
Find a window for the whole meeting
The following week, New York’s 09:00 start becomes 19:30 Mumbai. A recurring preview makes that additional evening hour visible before import. If the team agrees to an early New York or late Mumbai exception, enter those hours explicitly and keep the half-hour boundary intact.
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.