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 Pacific morning becomes an Asian night
On 27 October 2026, 09:00 in Los Angeles is 01:00 on 28 October in Tokyo. The date change matters as much as the sixteen-hour gap. If a Tokyo colleague offers a Tuesday morning, make sure that means Tuesday in Tokyo rather than the Tuesday selected on the Los Angeles row.
A dated view of the local clock
Four examples at 13:00 UTC, calculated with IANA 2026f. These are selected dates, not a live clock.
UTC date
UTC offset
Abbreviation
Local date and time
2026-01-15
UTC−08:00
PST
Thu, 15 Jan 2026 · 05:00
2026-07-15
UTC−07:00
PDT
Wed, 15 Jul 2026 · 06:00
2026-10-27
UTC−07:00
PDT
Tue, 27 Oct 2026 · 06:00
2026-11-03
UTC−08:00
PST
Tue, 3 Nov 2026 · 05:00
Recheck Vancouver after November
Los Angeles and Vancouver share UTC−07:00 on 27 October in the bundled rules. They differ on 3 November: Los Angeles is UTC−08:00 and Vancouver remains UTC−07:00. Keep both named zones in a plan; a shared “Pacific” label is not enough to describe this comparison.
Build a plan for this city
Select Los Angeles, add the other participants, and enter the actual meeting date. The planner uses America/Los_Angeles; the abbreviation in the table is a display label. Adjust working days, hours, and meeting length before choosing a shared window. The supported planning range is 2026–2035.