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
One local time can keep two meanings
New York is a useful anchor when an East Coast team needs a steady weekly start. A Tuesday meeting at 09:00 is 13:00 in London on 27 October 2026 and 14:00 there on 3 November. The local New York instruction is unchanged; the offset used to resolve it is different. Review the two dates as separate occurrences.
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−05:00
EST
Thu, 15 Jan 2026 · 08:00
2026-07-15
UTC−04:00
EDT
Wed, 15 Jul 2026 · 09:00
2026-10-27
UTC−04:00
EDT
Tue, 27 Oct 2026 · 09:00
2026-11-03
UTC−05:00
EST
Tue, 3 Nov 2026 · 08:00
Resolve the November repeated hour
On 1 November 2026, 01:30 occurs twice in America/New_York: first at UTC−04:00 and then at UTC−05:00. Choose the earlier or later instance before exporting. A screenshot of “01:30” alone cannot identify the intended meeting; keep the offset and date beside it.
Build a plan for this city
Select New York, add the other participants, and enter the actual meeting date. The planner uses America/New_York; 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.