Whole-hour assumptions create persistent errors
A guide that stores only a whole-hour offset cannot represent every location accurately. Asia/Kathmandu, Asia/Kolkata and Asia/Colombo are separate named locations. Their calculated offsets below retain the minute component instead of rounding it away.
This type of error can be mistaken for a delayed stream. A clock conversion changes the label attached to an instant; video latency describes when pictures reach the screen. A repeatable 15- or 30-minute listing difference should be investigated as a timestamp or location issue before changing video quality.
Convert one instant without losing precision
The following examples are hypothetical programme-planning instants. They demonstrate the local clock differences rather than a real broadcast schedule.
| UTC example | Asia/Kathmandu | Asia/Kolkata | Asia/Colombo | Asia/Karachi |
|---|---|---|---|---|
| 2026-11-03 18:00:00 UTC | 2026-11-03 23:45 (UTC+05:45) | 2026-11-03 23:30 (UTC+05:30) | 2026-11-03 23:30 (UTC+05:30) | 2026-11-03 23:00 (UTC+05:00) |
| 2027-07-15 18:00:00 UTC | 2027-07-15 23:45 (UTC+05:45) | 2027-07-15 23:30 (UTC+05:30) | 2027-07-15 23:30 (UTC+05:30) | 2027-07-15 23:00 (UTC+05:00) |
A common language does not imply a common clock
A language-based television group can contain programmes from several countries. The language is useful for choosing entertainment, but it should not become the guide’s clock setting. A programme from one country may be watched by a household in another country and needs a dated conversion.
Save the service name and source zone with recurring international programmes. That leaves the device free to keep its actual local clock while the guide interprets each source correctly.
Avoid correcting the same difference twice
Some services already supply guide data converted to a chosen local zone. Adding another manual shift can make correct data wrong. Compare one known programme time with the displayed result before adjusting an entire list, and remove an earlier correction when a source or setting changes.
Questions about this guide
Can a 15-minute error be caused by a time-zone setting?
Yes. Minute-based location differences can be lost by a whole-hour conversion or an incorrect substitute city.
Should I change video bitrate to fix an EPG clock difference?
Bitrate changes concern delivery and picture quality. Compare source timestamps and location settings for a clock-label error.