A named zone that often crosses tomorrow’s boundary
Pacific/Auckland uses UTC+13:00 in the January and late-October examples and UTC+12:00 in July. Its difference from a European zone reflects two distinct sets of clock changes. The local date is therefore a first-class part of any cross-region meeting table.
Offsets in the bundled rules
| Date | UTC offset | Display abbreviation |
|---|---|---|
| 2026-01-15 | UTC+13:00 | NZDT |
| 2026-07-15 | UTC+12:00 | NZST |
| 2026-10-27 | UTC+13:00 | NZDT |
| 2026-11-03 | UTC+13:00 | NZDT |
Resolve the wall time before exporting
02:30 on 27 September 2026 is skipped in this zone. On 5 April, 02:30 occurs twice, at UTC+13:00 and UTC+12:00. Choose a valid local time or an explicit repeated-time instance before generating the event.
Use this identifier in a plan
Find Pacific/Auckland in the zone directory or choose Auckland 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.