Why Your IPTV EPG Shows the Wrong Times

A shifted guide is a different fault from a missing one

These two problems get filed together and they have almost nothing in common. A guide that is empty means the EPG never loaded — wrong URL, expired link, a source that timed out. That is covered in our guide to an EPG that is not working at all.

A guide that is fully populated but says the 8pm match starts at 1pm is the opposite situation: the data arrived intact and is being displayed against the wrong clock. The feed is fine. The conversion is wrong. Nothing you do to refresh, reload or re-add the playlist will change it, which is why people spend an evening re-entering credentials and end up exactly where they started.

Why guides drift by whole hours

EPG data is distributed as XMLTV, and every programme in it carries a timestamp with an explicit offset — something of the shape 20260901183000 +0000. That is a time and a statement about which zone the time is expressed in.

Your player has to turn that into a local time on your screen. To do it, it uses the device clock, the device time zone, and in most cases its own EPG offset setting. Three inputs, and if any one of them is wrong the entire guide moves by the same amount in the same direction.

That uniformity is the diagnostic. If every single programme on every single channel is out by precisely the same interval, you are looking at a conversion problem with a setting behind it. If the errors are inconsistent, you are looking at something else entirely, and the next section covers that case.

Measure the offset before changing anything

Do not start toggling settings. Establish the number first, because the fix depends on its size and sign.

1. Pick a channel with a schedule you can verify independently — a national broadcaster whose listings are published on its own website.
2. Find a programme starting on the hour and compare the guide’s time against the published one.
3. Write down the difference and its direction: is the guide running ahead of reality or behind it?
4. Check a second channel from a different country group. If the offset is identical, it is local. If it differs, it is upstream.

That fourth step is the one people skip, and it is the one that decides whether the next hour is well spent.

The one-hour case is daylight saving

An offset of exactly one hour, especially one that appeared overnight in spring or autumn, is a daylight-saving transition. It happens for one of two reasons.

The device may be set to a fixed UTC offset — “UTC−5” rather than “New York” — in which case it will never observe DST and will be wrong for roughly half the year, every year. Setting a named time zone instead of a numeric offset fixes this permanently, and it is worth doing on every streaming device in the house rather than just the one you noticed.

Alternatively the EPG source may not have shifted yet. This one resolves itself, usually within a day or two of the transition, and applying a manual correction while you wait guarantees the guide will be an hour wrong in the other direction once the source catches up. If the timing coincides with a clock change, wait before you touch anything.

Where the offset setting lives

Every major player exposes a time-shift control, though the naming varies and menus move between versions. Look for the following rather than a specific menu path:

• TiviMate — an EPG time-shift option in the settings, expressed in hours. This is the correct place to apply a deliberate correction.
• IPTV Smarters Pro — a time-format and time-zone option in the general settings, which affects how guide timestamps are rendered.
• Kodi with PVR IPTV Simple Client— the add-on has its own EPG time shift, applied on top of Kodi’s own regional settings. Two places to check, and a correction applied in both will double.
• The device itself — always check this first. A Firestick or Android TV box with the wrong time zone will produce an offset that no player-level setting should be used to mask.

The order matters. Fix the device clock and time zone first, restart the player, and only then apply a player-level shift if a residual offset remains. Correcting a device fault with a player setting works until the device is fixed, at which point the guide breaks again and the cause is now two layers deep.

When some channels are right and others are wrong

This is the case where no setting helps, and recognising it early saves a great deal of time. A guide assembled from multiple EPG sources can carry one source that publishes timestamps without a correct offset. Applying a global shift then fixes that group and breaks every channel that was previously correct.

Mixed correctness is genuinely upstream. Note the specific channels, note the size of the error, and send both to support rather than continuing to configure. Vivimate subscribers can do that on WhatsApp, and the channel names matter far more than a description of the symptom.

Why it is worth fixing properly

A guide that is two hours out is an annoyance while you are browsing and a real problem the moment you use it for anything. Recordings scheduled from the guide fire at the guide’s time, so a shifted EPG records the wrong programme in full. Catch-up windows are calculated from the same timestamps. And on a service where you are navigating tens of thousands of channels, the guide is the only practical way to find anything at all.

If the guide is right and playback is the problem instead, that is a different diagnosis — start with the buffering guide, or the live-sport version if it only happens during matches.

A five-minute checklist

Working in this order avoids the most common mistake, which is stacking two corrections on top of each other and ending up further from the truth than you started.

1. Check the device clock and time zone. Set a named zone, not a numeric UTC offset. Reboot the device afterwards — several platforms do not propagate a time-zone change to running apps.
2. Reopen the player and re-measure. A surprising proportion of cases end here, and any player-level shift applied before this step is now wrong.
3. Confirm the offset is uniform across at least two channel groups from different countries. If it is not, stop configuring and report it.
4. Force an EPG refresh rather than waiting for the scheduled one. Players cache guide data for hours, so a fix can look like it failed simply because you are still looking at the old copy.
5. Only now apply a player-level time shift, and only for whatever offset survives all of the above.

If you have a residual offset that is not a whole number of hours, it is not a time-zone problem at all — zones are defined in whole and half hours, and nothing legitimate produces a seventeen-minute shift. That points at a device clock drifting because it cannot reach a time server, which is worth checking on older boxes on restrictive networks.

Common questions