The evening cost changes after New York’s clock change
At 09:00 New York on 27 October 2026, Tokyo reads 22:00. On 3 November the Tokyo time becomes 23:00. Tokyo’s sampled UTC+09:00 offset stays the same; New York’s move changes the relationship.
Compare the same local start on four dates
| New York | Tokyo | Time difference |
|---|---|---|
| 2026-01-15 · 09:00 | Thu, 15 Jan 2026 · 23:00 | 14 hours ahead |
| 2026-07-15 · 09:00 | Wed, 15 Jul 2026 · 22:00 | 13 hours ahead |
| 2026-10-27 · 09:00 | Tue, 27 Oct 2026 · 22:00 | 13 hours ahead |
| 2026-11-03 · 09:00 | Tue, 3 Nov 2026 · 23:00 | 14 hours ahead |
Find a window for the whole meeting
There is no overlap between illustrative 09:00–17:00 days on these dates. If a late Tokyo meeting is agreed, check the end time as well as the start: a two-hour session at 23:00 finishes on the next local date. Keep that date visible in the exported timetable.
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.