Planning dates run from Thu, Jan 1, 2026 through Mon, Dec 31, 2035. Future rules can be revised; review the data version when a distant schedule matters.
More context and planning advice
Berlin’s finish often sets the Atlantic limit
At 09:00 New York on 27 October 2026, Berlin reads 14:00. Two illustrative 09:00–17:00 schedules share three hours, ending at 17:00 Berlin. A 90-minute call can start no later than 15:30 Berlin or 10:30 New York.
Compare the same local start on four dates
09:00 in Berlin, resolved separately on each date with IANA 2026f. The final column describes New York relative to Berlin.
Berlin
New York
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 03:00
6 hours behind
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 03:00
6 hours behind
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 04:00
5 hours behind
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 03:00
6 hours behind
Find a window for the whole meeting
On 3 November, New York’s 09:00 becomes 15:00 Berlin, leaving only two hours. A weekly slot can stay within the start-time limits while its duration stops fitting. Review the end time on every occurrence, especially if London or another European city joins.
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.