Set a meeting or flight time from the clock-change examples
These examples use only New York and Tokyo in 2026: a local time that does not exist, a local time that happens twice, a year with no change, and a refusal outside the range. There is no page that only swaps a city name.
Spring 2:30 in New York does not exist
On 8 March 2026 in New York the last existing local time is 01:59:59 (UTC−05:00) and the next is 03:00:00 (UTC−04:00). Clocks move forward 60 minutes. 02:30 that morning is not a local time, so do not put a meeting or a flight there. Keep 01:30, which still exists, or move to 03:00 or later, and write UTC−04:00 on the time after the jump.
Fall 1:30 is the same clock time twice
On 1 November 2026 in New York the local time just before the change is 01:59:59 (UTC−04:00) and the local time just after is 01:00:00 (UTC−05:00). Clocks move back 60 minutes. 01:30 happens twice: the earlier one at UTC−04:00 and the later one at UTC−05:00. An invite or a ticket that only says 1:30 does not pick one instant. Name earlier or later and add the offset.
Tokyo that year does not move the clock
Asia/Tokyo in 2026, which Osaka shares, has no clock-change row. In this data each local time happens once, so a clock change is not a reason to move the meeting. If someone joins from another city, write that one instant’s offset in World Time.
Outside the range is not “no change”
A year outside 1970–2100, or a zone that is not in the list, is refused. That is different from zero rows. Do not invent a transition. Put the year inside the range or pick a listed city.
How to settle the time
List the changes for the city and year first. Drop a local time that falls in a gap, move it to a time that exists, and write the offset. For a repeated local time, choose the earlier or the later one and add the offset. Zero rows means you do not move the meeting because of a clock change. A refusal is not “no change”; correct the input. A shared window is the deadline planner, one typed instant is World Time, and a civil-date gap is the date-line itinerary.
Basis
The basis is the runtime IANA time-zone data through Luxon. It is not a copy of a government notice. The seconds shown are the sample just before and just after the offset changes.
What this page covers
This page explains whether to keep or move a meeting or flight’s local time for one listed time zone and one year. It does not reinterpret one typed instant, find a window shared by several cities, cross the date line, or plan bridged days off.
When you need to update the time
Update it when a local rule changes and the runtime data does not have it yet, when the meeting year is not the year you opened, when the city is not the zone you selected, or when a repeated time has no offset. List the changes again and rewrite the invite or the flight time.
List that year’s rows in Clock changes
Read one instant in World Time