Programme timestamp could not be read
A start or stop attribute is not in XMLTV format, so the programme cannot be placed on the timeline.
What it means
XMLTV timestamps look like 20260101235900 +0100 — fourteen digits and an optional offset. This value does not match, and it is notably not ISO 8601.
Why it matters
A programme whose time cannot be parsed cannot be shown. Clients drop it, leaving a hole. Writing ISO 8601 (2026-01-01T23:59:00Z) is the most common mistake and is rejected by every XMLTV parser.
How to fix it
- Use the XMLTV format: YYYYMMDDHHMMSS followed by a space and a ±HHMM offset.
- Do not use ISO 8601 — dashes, colons and a T are all invalid here.
- Include the offset; without it the time is ambiguous.
Check your own stream
The free EPG checker runs this check on every analysis and links each finding straight back here.
Open the EPG checker →Frequently asked questions
- What does "Programme timestamp could not be read" mean?
- XMLTV timestamps look like 20260101235900 +0100 — fourteen digits and an optional offset. This value does not match, and it is notably not ISO 8601.
- Why does it matter?
- A programme whose time cannot be parsed cannot be shown. Clients drop it, leaving a hole. Writing ISO 8601 (2026-01-01T23:59:00Z) is the most common mistake and is rejected by every XMLTV parser.
- How do I fix it?
- 1. Use the XMLTV format: YYYYMMDDHHMMSS followed by a space and a ±HHMM offset. 2. Do not use ISO 8601 — dashes, colons and a T are all invalid here. 3. Include the offset; without it the time is ambiguous.
- How can I detect this automatically?
- Paste your XMLTV programme guides URL into StreamTest's free EPG checker. It runs this check on every analysis, flags the finding, and links straight back to this page — no sign-up required.
Related Programme guides checks
- XMLTV timestamps have no UTC offsetTimestamps without an explicit offset are ambiguous, and are the usual cause of a guide that appears shifted by whole hours.
- XMLTV guide has holes in a channel scheduleConsecutive programmes do not join up, leaving blank stretches in the guide.
- XMLTV guide does not extend far enough aheadThe guide runs out within hours, so viewers lose programme information partway through the day.
- The guide is not well-formed XMLThe document could not be parsed as XML, so nothing else could be checked.
- The document has no <tv> root elementThe XML parsed, but its root is not <tv>, so it is not an XMLTV guide.
- Guide declares no channelsWithout <channel> elements there is nothing for a playlist to match against.