No transition occurs in this named zone during the selected year.
Before and after show the boundary labels at the exact UTC transition. A missing or repeated local label still requires an explicit choice in the planner.
Why an identifier matters
An offset describes one moment. A named zone carries the date-specific rules used to calculate each meeting.
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.
Asia/Tokyo uses UTC+09:00 across the four displayed samples. The identifier expresses the intended local rules; the numeric offset describes the result at a particular date. Keep both visible when reviewing a calendar event with someone using a different display zone.
Offsets in the bundled rules
Sampled at 12:00 UTC on each date, using IANA 2026f.
Date
UTC offset
Display abbreviation
2026-01-15
UTC+09:00
JST
2026-07-15
UTC+09:00
JST
2026-10-27
UTC+09:00
JST
2026-11-03
UTC+09:00
JST
Resolve the wall time before exporting
01:00 on 28 October 2026 is 16:00 UTC on 27 October and 09:00 on 27 October in Los Angeles. This is a date-boundary example, not a clock-change ambiguity: the local time has one valid instant.
Use this identifier in a plan
Find Asia/Tokyo in the zone directory or choose Tokyo from the city directory. Add the other meeting locations, enter their availability, and check the complete duration. The supported planning years are 2026–2035; future political rule changes may require a new data version.
A calendar export uses the resolved UTC start and end times. The zone remains part of the planning context, while the exported instant stays unambiguous when another calendar displays it in its own time zone.