IPTV & Media
EPG Time Zones and Incorrect Programme Times
Diagnose programme-guide times that are offset by an hour or more, including XMLTV timestamps, regional feeds and daylight-saving changes.

Incorrect EPG times can come from the guide's timestamps, the device's time zone, a mismatched regional channel or an offset applied twice. Start with one programme whose actual start time you can confirm. Compare the source timestamp, the intended channel and the displayed time before changing a global guide offset.
EPG means electronic programme guide. Support for importing or displaying a guide depends on the player, so check that capability separately. This article explains guide data and diagnosis; it does not establish that CarCast supports an EPG feature or any particular guide setting.
A Programme Time Has a Zone Context
A timestamp identifies more than the hour printed on a television schedule. It may include an explicit numeric offset from UTC. For example, an illustrative timestamp with a 19:00 time and +0000 offset represents 19:00 UTC. In a location currently using UTC-05:00, the same instant is 14:00 local time.
The XMLTV document definition documents the date and time conventions used by XMLTV guide data. Check the actual source representation rather than assuming that all guides contain local wall-clock times. A missing or incorrectly interpreted offset can shift every programme even when the channel names look correct.
Do not edit real guide timestamps based only on a screenshot. First retain a private copy of the original entry and establish which instant the guide intended to describe.
Verify the Device Clock and Location
Check that the device shows the correct date, time and time zone. A correct-looking clock is not sufficient if the underlying zone is wrong; two zones can share an offset today and differ after a seasonal transition. Use the operating system's supported automatic settings where appropriate.
The IANA Time Zone Database tracks changes in civil time rules. Governments can change those rules, so an old client or stale time-zone data can behave differently from an updated device. A time-zone name represents rules over dates, while a fixed UTC offset represents a particular displacement.
If a player has its own display-zone setting, document it separately from the system setting. Avoid changing both at once. You need to know whether the guide is being converted by the device, the player or both before applying a manual correction.
Confirm That the Guide Matches the Feed
A guide can be correctly timed for the wrong channel version. Regional editions, delayed feeds and alternate language channels can share similar names or logos while airing different programmes. A one-hour delayed service may look like a daylight-saving error when it is actually the wrong feed association.
Inspect the channel identifier used by the playlist and the guide. Do not rely only on the visible name. A provider may use a stable ID that differs from its branding. See M3U groups and logos for the distinction between display metadata and identity.
Compare several programme titles, not just one start time. If titles differ throughout the day, a global offset is unlikely to solve the underlying mismatch. Ask the source owner for the intended channel-to-guide mapping rather than inventing a replacement identifier.
Distinguish a Constant Shift from Drift
A constant one-hour difference across otherwise matching programmes suggests a zone or offset issue, but it is not proof. A difference that changes around midnight, varies by channel or increases over time points to other possibilities, including mixed source zones, stale data or incorrect programme boundaries.
Make a small comparison table with the channel, programme title, guide start, confirmed start and device zone. Include the date because seasonal rules depend on it. Three or four entries across affected and unaffected channels can reveal more than repeatedly adjusting an entire guide.
Also distinguish the broadcast from a delayed stream. Internet delivery can be behind the original transmission, but that delay is not necessarily a reason to rewrite the published schedule. HLS live windows and buffering are separate from civil time conversion; HLS playlist types explains that layer.
Avoid Applying the Same Correction Twice
A provider may already publish timestamps with explicit offsets. If a player converts those timestamps to local time and you then add a manual shift intended for raw UTC data, the result can become wrong. Similarly, editing the file and setting an application offset can duplicate the same correction.
Return to a documented baseline before experimenting. Use an unmodified current guide, the correct device zone and no optional manual shift where the player permits that configuration. Then inspect one known programme. Only apply a correction when you can explain what error it compensates for.
Some applications offer per-source or per-channel offsets, while others do not. Do not assume a universal setting name or invent a menu sequence. Consult the actual player's documentation, and record every changed value so you can restore the baseline after an unsuccessful test.
Check Refreshes Around Seasonal Changes
A guide downloaded before a time-zone change may contain upcoming entries generated under incorrect assumptions, or the player may still be displaying a cached older version. Confirm the guide's retrieval time and the programme dates. A refreshed file can help only if the source itself is correct.
Test programmes before and after the transition date when relevant. A fixed one-hour manual correction that seems useful today may produce the opposite error later. Prefer correctly expressed source timestamps and current time-zone rules over a permanent workaround whose scope is unclear.
If you maintain the guide, use a proper date-time library and named zones when generating future local schedules. Do not perform time-zone conversion by adding the current offset to every future date. Local rules can change across the schedule period and may differ by region.
Send a Precise Guide Report
Provide the guide owner with the affected channel ID, date, programme title, raw timestamp where available and your display zone. State whether the mismatch is constant and whether other channels behave correctly. A harmless excerpt usually suffices; there is no need to share an entire credential-bearing playlist.
If the source timestamps are wrong, the publisher should correct them. If correct timestamps display incorrectly in one documented client, provide the same minimal example to that client's support team. Keep the content provider, guide provider and player roles distinct.
An offset control can mask a symptom, but a durable correction identifies the intended instant and converts it once. Verify that relationship on a small set of real programme entries before applying changes to a whole catalogue.
Sources
Bring your own media.
Explore CarCast for iPhone with your own authorized sources and supported display configurations.


