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
A late London call can be an early Pacific start
On 27 October 2026, 16:00 London is 09:00 Los Angeles. One week later, the same London time is 08:00 Los Angeles. The changing gap comes from different clock-change dates, so a slot copied from the last week of October needs another check.
Compare the same local start on four dates
09:00 in London, resolved separately on each date with IANA 2026f. The final column describes Los Angeles relative to London.
London
Los Angeles
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 01:00
8 hours behind
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 01:00
8 hours behind
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 02:00
7 hours behind
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 01:00
8 hours behind
Find a window for the whole meeting
Two illustrative 09:00–17:00 schedules share just one hour on 27 October and have no positive-length overlap on 3 November. Touching at 17:00 London and 09:00 Los Angeles is not a meeting window. Ask about a shorter call or a deliberately extended day.
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.