Why an IPTV program guide can show the wrong time

First, work out which kind of “wrong” you have

The pattern of the error tells you where to look. Compare the guide with what's actually on screen on two or three channels, and note your local time.

How guide times are supposed to work

Most IPTV guides use the XMLTV format. Each program has a start and stop time, and the format's definition says a time can carry a time-zone offset at the end; if it doesn't, UTC is assumed. Its own example is 19880523083000 +0300: 8:30 a.m. on May 23, 1988, three hours ahead of UTC.

Your player reads those times and converts them to the local time your device (or the player's own setting) says you're in. So an error can enter in three places: the guide data, the player's conversion settings, and your device's clock and time zone. The checklist below goes through them from the one you control most easily to the one only the provider can fix.

Step 1: Check the device's clock and time zone

Most players display guide times in the device's local time, so this is the most common culprit, especially on a TV box bought abroad or moved between countries.

• Turn on automatic (network-provided) date and time if the device offers it.
• Make sure the time zone is where you are now, not where the device was bought. A named zone or city (for example “Chicago”) is better than a fixed offset (“GMT−6”), because a named zone follows daylight saving and a fixed offset doesn't.
• Restart the player app after changing it.

Step 2: Check the player's own time-zone or offset setting

Some players add their own offset on top of the device time. If someone set an offset in the past, perhaps to work around a different problem, it can now be wrong. Look in the player's settings for anything called EPG time shift, EPG offset, time zone or timeshift, and set it to zero before testing again.

Step 3: Refresh the guide data

Players download guide data and keep it for a while. If the download failed, or the data is old, you'll see empty rows, a guide that ends after a day, or yesterday's schedule.

• Use the player's “update EPG”, “reload guide” or “refresh playlist” option if it has one.
• Give large guides a few minutes to load before judging the result.
• If you entered a separate guide (XMLTV) address yourself, check it was copied in full.

This step is a general suggestion; the exact option name depends on the player.

Step 4: Rule out a daylight-saving mismatch

Daylight saving causes one-hour errors that appear suddenly and sometimes fix themselves a few weeks later. They are especially common for international viewers, because different countries change their clocks on different dates.

Two windows in 2026 are worth noting. Between March 8 and March 29, and again between October 25 and November 1, the United States and the United Kingdom are on different daylight-saving settings, so the usual gap between them is one hour smaller. If you watch a UK channel from the US (or the reverse) and the guide is one hour out only during those weeks, the device or player is probably using a fixed offset instead of a named time zone. Switch to a named zone and refresh the guide.

Step 5: Check whether the channel's guide data itself is wrong

If your device and player are right and only some channels are wrong, the guide data for those channels may be supplied with the wrong time offset, or may be out of date. Everybody using the same data sees the same error, and nothing on your device can fix it properly.

Compare the guide with the broadcaster's own published schedule for that channel, in that channel's local time, and note the difference. That comparison is the most useful thing you can send support.

Step 6: Make sure the guide belongs to the feed you're watching

When a channel has several regional or time-zone versions, the guide data can be matched to a different version from the one you're watching. The symptom is a guide that's always a fixed number of hours out on one channel, or that lists programs the channel never shows. Tell support which feed you're watching (for example, the version for a particular region) so they can check the match.

Regional examples: US, UK and Canada

There is no single “right” offset for a country, which is why fixed offsets cause trouble:

• United States. The country spans several time zones (Eastern, Central, Mountain, Pacific, Alaska and Hawaii-Aleutian among them). A viewer in Phoenix and a viewer in Denver share Mountain Standard Time in winter but are an hour apart in summer, because most of Arizona doesn't observe daylight saving time.
• United Kingdom. One time zone, but it moves between GMT and British Summer Time on dates that differ from North America's.
• Canada. Six official time zones, including Newfoundland's, which is offset by half an hour; a whole-hour offset setting can't correct a half-hour difference. Yukon stays on the same time all year, so a device set to a neighboring zone will drift by an hour twice a year.

In each case the fix is the same: set the device to the named time zone where you are, keep any player offset at zero unless you know why it's needed, and report channel-specific errors to support.

A report template for support

Guide problems are much faster to solve with specifics. Copy this, fill it in, and include a photo of the guide next to the channel if you can.

Subject: Program guide time problem

Channel (name and country/feed): [ ]
Player app and version: [for example "App name 1.2.3"]
Device and model: [ ]
Device time zone setting: [automatic / manual: ...]
Player time-zone or EPG offset setting, if any: [ ]

What the guide shows: [program] at [time]
What is actually on screen: [program] at [time]
My local time when I checked: [time, city]

Is the difference the same on all channels? [yes / no / only these: ...]
Did it start after a clock change or an app update? [ ]
I have already tried: [device time zone / guide refresh / restart]

Send it by email, WhatsApp or live chat.

What support can fix, and what they can't

Support can check the guide data and the channel-to-guide match on the service side, and correct them where they're wrong. They can't change settings on your device or inside a third-party player app, and they don't control how a player displays the guide. That's why steps 1 to 4 come first.