Samoa and American Samoa: the clock can match while the date differs

Two locations, two calendar contexts

Pacific/Apia and Pacific/Pago_Pago are separate IANA locations. A shared place-name stem or a similar time on a clock face should not cause them to be merged into one programme-guide setting. The conversion below shows a full calendar-day difference for the selected instant.

This matters for an event announced as Tuesday evening. A viewer who remembers only the hour may open the programme on the wrong day. Writing the source location and date next to the start removes that ambiguity.

Convert one instant without dropping the date

This is a hypothetical scheduling example, not a broadcast announcement. The UTC instant is identical in every column.

Avoid a date-only mistake that looks like missing content

Opening a programme guide a day early or late can look like an absent event, an incorrect category or an expired replay. Before changing an account or reinstalling a player, compare the source announcement with the local calendar date. A correct hour does not prove the correct day was selected.

A reminder should ideally store a complete date and named time zone. A handwritten note can do the same job if it retains the day, date, hour and reference location. A bare number such as 7.30 leaves too much to memory.

Separate local scheduling from access

The time calculation does not establish where a programme may be watched or whether a replay exists. Those are questions for the service carrying the programme. Keeping the clock calculation separate prevents a geographic time reference from becoming an unsupported availability promise.

Questions about this guide

Sources and further reading

• IANA 2026f time-zone source