Articles
EPG wrong time: understand timestamps before changing settings
Work through XMLTV time zones, UTC offsets and daylight-saving examples to distinguish a shifted programme guide from stale or mismatched listings.
Published by InoxTV · Published
Last updated
If your EPG shows the wrong time, establish whether the programmes are consistently shifted, out of date, or attached to the wrong channel. Those symptoms have different causes. A one-hour pattern can suggest an offset problem, but it is not proof. Start with one identifiable programme and compare the source timestamp, the intended channel feed and the device's displayed time.
A timestamp describes a clock reading and an offset
XMLTV timestamps can include a date, a clock time and an offset from UTC. For a complete timestamp, the date and time digits are followed by a signed offset such as +0000 or +0530. In the XMLTV format, omitted time-zone information is treated as UTC; a publisher that writes local time without the appropriate offset can therefore describe the wrong instant.
The offset is not decoration. The fictional timestamp 20261102180000 +0000 means 18:00 UTC on 2 November 2026. The timestamp 20261102233000 +0530 describes the same instant using a clock five hours and thirty minutes ahead. The clock readings differ, but a correct conversion places both at the same point on the timeline.
Convert an explicit example step by step
Imagine a fictional bulletin beginning at 18:00 UTC. A viewer whose local offset on that date is +05:30 expects 23:30. A viewer at -04:00 expects 14:00. Subtract the source offset to obtain UTC, then add the viewer's applicable offset. Do not simply compare the hour digits and assume that different numbers represent different broadcasts.
| Source timestamp | UTC instant | Display at +05:30 |
|---|---|---|
20261102180000 +0000 | 2 November, 18:00 | 2 November, 23:30 |
20261102233000 +0530 | 2 November, 18:00 | 2 November, 23:30 |
20261102210000 +0000 | 2 November, 21:00 | 3 November, 02:30 |
The final row crosses midnight. A programme appearing on the following local calendar day is not automatically wrong. Check the day as well as the hour when reviewing a schedule. This is particularly useful for overnight broadcasts, recordings and guides whose source publishes dates using a different regional convention from the viewer's location.
Why a fixed one-hour repair can stop working
A named time zone contains rules about offsets over time. A fixed numeric offset describes the offset for a particular timestamp but does not, by itself, contain the region's seasonal rules. During a daylight-saving transition, some local clock readings repeat or do not occur. Explicit offsets help distinguish instants that would otherwise look identical on the local clock.
Different regions can change clocks on different dates, and some do not observe daylight saving at all. Avoid assuming that a broadcaster and a viewer change together. A manual adjustment that compensates for today's bad source timestamps may be wrong after either region changes its rules. Prefer correct device settings and source data that states the intended instants accurately.
Distinguish four common patterns
Every programme is shifted by the same amount. Check the device time zone and inspect an explicit source timestamp if available. Compare more than one channel. A uniform shift is useful evidence for a conversion problem, but a source-wide publishing error can look similar. Record what the source actually says before changing anything.
Only one channel is wrong. Check whether the guide refers to a regional edition, delayed feed or different channel identifier. The XMLTV matching article explains how identifiers connect records. An offset adjustment applied to the whole guide would damage the channels that already display correctly.
Yesterday's programmes remain visible. Check the last successful update and the source's date coverage. Refreshing can help when local data is stale, but downloading the same outdated source again cannot create today's programmes. Preserve one example with a programme title and date so the source operator can investigate what was published.
A programme begins later than listed. Live events and scheduling revisions can make a published guide inaccurate even when timestamps are correct. Compare the actual broadcast with an official schedule where available. Do not treat every late start as a clock defect; the programme plan and the real transmission can diverge.
A small record is better than repeated adjustments
Use the fault-isolation worksheet to keep a before-and-after record. If changing one device setting corrects some channels but disrupts others, preserve both examples. Mixed results are useful evidence that the sources may differ, rather than a reason to apply another universal adjustment.
Write down the channel's exact feed, programme title, expected local start, displayed start, device time zone and date of the observation. Include whether the discrepancy affects other channels. If you can inspect the source lawfully, note a redacted timestamp and identifier rather than sharing its private URL. Those details allow another person to repeat the conversion.
In InoxTV, use the guide setup instructions to review the configured source and the guide troubleshooting page to interpret update results. Make one relevant change, refresh if needed and compare the same programme again. Recheck a future date before assuming that a seasonal issue is fully resolved.
