The Chatham Islands are forty-five minutes ahead of New Zealand's main-island time. A national sports reminder copied from Auckland can therefore be wrong for a Chatham viewer even when its date is otherwise correct.
Use Pacific/Chatham and retain the full minute component. A country-level “New Zealand time” setting is not always precise enough for the actual viewing locality.
Keep standard and daylight relationships clear
New Zealand Government guidance defines standard time as UTC+12 and the Chatham Islands as forty-five minutes ahead of that. During the current daylight-saving period, the respective offsets are UTC+13 and UTC+13:45.
The island relationship is not a forty-five-minute daylight-saving change. It is a locality difference that remains relevant when both follow their applicable seasonal rules. Confusing those ideas can produce the right answer in one month and the wrong explanation afterward.
Convert the complete instant
For an illustrative instant of 20:00 UTC on November 4, 2026, Auckland displays 09:00 on November 5 and the Chatham Islands display 09:45 on November 5. These are calculated examples under IANA 2026f, not fixture announcements.
The next-day date belongs in both entries. Adding forty-five minutes to a clock without carrying the date can also fail near midnight. Use the calendar's complete date-and-zone conversion rather than editing only the visible hour.
| Viewing zone | Illustrative display |
|---|---|
| Pacific/Auckland | November 5, 2026, 09:00 |
| Pacific/Chatham | November 5, 2026, 09:45 |
Check imported sports calendars
After importing a fixture, inspect the selected display zone and one known event. A correctly encoded instant should localize appropriately, but a manually created floating local time can be interpreted differently. The filename ending in ICS does not by itself prove the event is zone-aware.
If a friend sends an Auckland time, ask whether it is the actual scheduled play time or the start of coverage. Those are separate adjustments; the locality conversion should not absorb an unrelated pregame interval.
- Identify the original schedule’s zone and event date.
- Select Pacific/Chatham for the viewing locality.
- Preserve the forty-five-minute component.
- Check the resulting day and time after import.
- Reconcile any official fixture update before relying on the reminder.
Keep availability out of the calculation
A precise time conversion does not establish a service's territorial rights, commentary or replay access. Confirm those through current competition and broadcaster information for the actual account and location.
The useful output is an invitation that says which event, local day and local start it represents. That is enough to prevent an avoidable calendar error without turning a geographic reference into an IPTV USA channel-availability claim.
Useful answers
Is Chatham time the same as Auckland time?
No. The current relationship places the Chatham Islands forty-five minutes ahead, so use the actual locality’s zone.
Does an ICS file guarantee correct local conversion?
No. Its event must encode an unambiguous time appropriately, and the calendar’s display zone should be checked after import.