Work from the same programme
Write the programme name, station edition, date, and displayed time. Compare them with the broadcaster’s own schedule. If a news bulletin appears in both schedules at different times, check the location of the edition first. A nationally named station may list a programme in a market you are not watching.
A timestamp such as 20261113200000 +0000 means 20:00 UTC on 13 November 2026. In Europe/Paris on that date, that same moment is 21:00. In Europe/London, it is 20:00. A bare “20:00” in a screenshot does not tell you which of those readings you have.
Compare two stations and two dates
Use a second channel from the same guide. If both are off by exactly one hour, look at the device or player zone and any global offset. If one is correct, find out whether the wrong one points to a different station edition. If only dates near a clock change are wrong, check the original timestamp on each side of the change.
| What shifted | What to inspect first |
|---|---|
| Every station, every date | Device zone and global player offset. |
| One station | Feed selection and guide ID. |
| One time period after the clocks change | Source time zone and daylight-saving conversion. |
| Two channels show different offsets | The two feeds may use separate zones or guide sources. |
Save the setting you can return to
Record the old value before changing it. Set the device zone to your actual location where possible, then refresh the guide and test two programmes. A fixed +1 adjustment might help a single feed today and be wrong at another time of year. Keep it only when the supplier or app documents the offset and your checks show which feed needs it.
What to post if it is still wrong
Include the exact programme and date, the station or feed edition, your device zone and the time the broadcaster lists. If you know the XMLTV time and offset, share a short redacted example. That gives a reader enough to reproduce the conversion without access to your account.