# Why your TV guide is an hour wrong: time zones, clock changes and XMLTV

Every programme an hour early, or an hour late but only in summer: the pattern tells you the cause. We ran made-up guides through the guide readers in our apps and tools and mapped which mistake gives which error.

By the CodoPlayer team. Published 22 November 2026.

- **Tested by:** The CodoPlayer team, who build the apps
- **Where:** The guide readers of our web player, our Samsung TV app and our free EPG tools, run on a made-up guide on 22 November 2026; the Android apps from their code and unit tests
- **Not tested:** Any real TV guide: we never test with viewers' playlists or guide addresses
- **Last checked:** 22 November 2026

## The pattern tells you the cause

A guide that is an hour off is rarely broken at random. When it is wrong, and in which direction, points to the cause:

| What you see | Most likely cause |
|---|---|
| Every programme an hour late, but only between late March and late October | The guide writes local clock times with no offset, with +0000, or with a zone name such as BST |
| Every programme an hour early, but only between late October and late March | The guide's offset is stuck at the summer value, +0100 |
| The same error all year | The guide uses the wrong offset all year, or the device's time zone is set wrong |
| The guide is right, but catch-up starts at the wrong time | The catch-up start time is written in a different time zone from the one the server expects |

The examples on this page use London, where, according to GOV.UK, the clocks go forward one hour at 1am on the last Sunday in March and back one hour at 2am on the last Sunday in October. In 2026 those were 29 March and 25 October. The same reasoning works for any place with summer time; only the dates and the size of the offset change.

## How a TV guide writes a programme's time

Most IPTV guides use the XMLTV format. Each programme carries a start time made of the date, the clock time and an offset from UTC:

```
<channel id="lab.one">
  <display-name>Lab One</display-name>
</channel>
<programme start="20261024200000 +0100" stop="20261024210000 +0100" channel="lab.one">
  <title>Lab Quiz</title>
</programme>
```

`20261024200000 +0100` means 24 October 2026 at 20:00:00, one hour ahead of UTC, which is 19:00 UTC. The XMLTV format definition says that "if no explicit timezone is given, UTC is assumed". Its own examples show both a number (`+0300`) and a zone name (`BST`), with the note "(BST == +0100.)".

A guide that is correct for London therefore writes +0100 from late March to late October and +0000 for the rest of the year. Every app then converts the time to the clock of the device it runs on.

## Seven ways to write the same programme

We wrote one made-up programme, due to start at 20:00 London time, in seven ways. Four are on Saturday 24 October 2026, the last evening of British Summer Time; three are on Sunday 25 October, the first evening after the clocks went back. We then ran each start time through the guide readers of our web player, our Samsung TV app and our free EPG tools.

| Start time in the guide | Read as | Shown on a London device | Result |
|---|---|---|---|
| `20261024200000 +0100` | 19:00 UTC | Sat 20:00 | Correct |
| `20261024190000 +0000` | 19:00 UTC | Sat 20:00 | Correct, written in UTC instead |
| `20261024200000` | 20:00 UTC | Sat 21:00 | One hour late |
| `20261024200000 BST` | 20:00 UTC | Sat 21:00 | One hour late; the EPG tools count it as an unreadable time |
| `20261025200000 +0000` | 20:00 UTC | Sun 20:00 | Correct |
| `20261025200000 +0100` | 19:00 UTC | Sun 19:00 | One hour early |
| `20261025200000` | 20:00 UTC | Sun 20:00 | Correct only because London time equals UTC in winter |

The web player and the Samsung TV app read every line identically. Our Android TV app and our phone and desktop app follow the same rule in their code and unit tests: a numeric offset is applied, no offset means UTC, and anything else after the time is ignored. We did not run those two apps for this article.

## Four causes, one at a time

### A guide in local time with no offset

The publisher writes the clock time people see on their wall and leaves the offset off, or writes +0000 out of habit. The format says that means UTC, so every app reads it as UTC. In winter London time and UTC are the same and nothing looks wrong. From the last Sunday in March, every programme appears one hour late, and it stays that way until the clocks go back.

### An offset that never changes

The publisher sets +0100 once, in summer, and never updates it. All summer the guide is right. From the last Sunday in October, every programme appears one hour early, until the clocks go forward again.

### A zone name instead of a number

The XMLTV definition allows a zone name such as BST. None of our apps reads zone names today: they read the time as UTC, so a guide that writes BST shows programmes one hour late in summer. Our EPG Validator counts these times as unreadable, so they are easy to spot.

### The device's own clock or time zone

Apps convert guide times to the device's time zone. If a TV box is set to the wrong zone, or to GMT with no summer time, every programme moves by that error, all year or only in summer. Our phone and desktop app compares the device's clock with the IPTV server's clock and shows a warning in its settings when the two differ by five minutes or more.

## Catch-up: the same hour, a different cause

Catch-up, or archive, asks the server for an old programme by its start time. Xtream Codes servers report their own time zone, and in our testing a start time written in the device's time zone instead played the wrong hour. Our Android TV app and our Samsung TV app write the catch-up start in the server's reported time zone, and use the device's time only when the server does not report one.

## What each CodoPlayer app does

| App | Offsets like +0100 | No offset | Zone names like BST | Manual correction |
|---|---|---|---|---|
| Android TV app | Applied | Read as UTC | Read as UTC | Per guide source: −12 to +12 hours. Per channel: −10:00 to +10:00 in 30-minute steps |
| Phone and desktop app | Applied | Read as UTC | Read as UTC | Per playlist: −3 to +3 hours, including half hours |
| Web player | Applied | Read as UTC | Read as UTC | Per guide source: −12 to +12 hours |
| Samsung TV app | Applied | Read as UTC | Read as UTC | Per channel: −5:00 to +5:00 in 30-minute steps |
| Free EPG tools | Listed and counted | Read as UTC | Counted as unreadable | The EPG Time Shifter makes a copy moved by whole or half hours |

## How to fix a guide that is an hour off

1. Note when it is wrong: all year, only in summer, or only in winter. The table at the top of this page names the likely cause.
2. Run the guide through the [EPG Validator](https://codoplayer.com/tools/epg-validator). It lists which offsets the guide uses and counts times it cannot read.
3. If the offsets are missing, fixed or written as zone names, ask whoever publishes the guide to write the correct offset for each date. That is the only fix that stays right all year.
4. Until then, set a time shift in the app, or make a shifted copy with the [EPG Time Shifter](https://codoplayer.com/tools/epg-shift). A manual shift fixes the current season only, so undo it when the clocks change.
5. If every guide is off by the same amount all year, check the device's time zone and clock before anything else.

Our guide [TV guide times are wrong](https://codoplayer.com/guides/epg-times-wrong) has the step-by-step version for each app.

## The limits of this test

- **One place, one kind of summer time.** We used London's one-hour change. Places with half-hour offsets or without summer time follow the same rules with different numbers.
- **Made-up guide only.** The channel, the programme and the times were invented for the test. We did not test any real guide.
- **Two apps from their code.** The Android TV app and the phone and desktop app were checked from their code and unit tests, not run for this article.

## Sources

1. [XMLTV project: the XMLTV format definition (xmltv.dtd)](https://github.com/XMLTV/xmltv/blob/master/xmltv.dtd) (read 22 November 2026)
2. [GOV.UK: When do the clocks change? (2026 dates)](https://www.gov.uk/when-do-the-clocks-change) (read 22 November 2026)

Source: https://codoplayer.com/insights/tv-guide-an-hour-wrong
