Why guide times drift, and what re-pointing a channel means

Measure the error before you change anything

Open four channels from four unrelated groups and compare what the listing claims against what is on screen. If all four are wrong by the same amount, the data is almost certainly fine and reporting individual channels achieves nothing. If three are right and one is not, that is a single-channel fault with a completely different cause.

The size of the gap matters as much as how widely it is spread. Anything landing on a whole hour, or a whole half hour if you are in India or parts of Australia, is arithmetic. Six minutes, or eleven, or nineteen, is not, and no setting anywhere will reconcile it.

A whole number of hours means the offset was applied twice

Programme data does not carry your local time inside it. Every entry is stamped with a start, an end and an offset from UTC, and each piece of software between that file and your television is entitled to convert it. The player converts, then asks the device what time it is and converts again if the answer disagrees. Some set-top boxes convert a third time, using a region set in a factory and never touched since.

When two of those conversions fire, the whole list slides by the difference and stays there, which is how a guide ends up two hours ahead across the entire line-up while every stream plays correctly. Listings and video travel by separate routes, so one being wrong says nothing about the other.

The repair order matters. Set the time-shift or EPG offset inside the player to zero or automatic first, then set the device region, then reload. Most people work the other way round, set both to their own region, and double the offset they were trying to remove.

The fortnight each spring and autumn when half the guide is wrong

Twice a year there is a stretch of one to three weeks when part of the line-up is an hour out and the rest is perfect. Europe changes its clocks on the last Sunday in March and October, North America on the second Sunday in March and the first Sunday in November. In between, London and New York are four hours apart rather than five.

A source file built with a fixed numeric offset rather than a named region does not know any of that happened, and its channels sit an hour adrift until whoever generates it notices. Leave it two or three days. If it survives into the following week, report it.

Minutes of slippage is the broadcast, not the file

A match goes to extra time, rain stops play, a news special eats into the programme behind it. The guide is a schedule published in advance, not a description of what is currently on air, and channels carrying a lot of live output wander through their own evening before snapping back at the next junction, usually the top of an hour.

So never trust a guide end time on a live event. Going back to one on catch-up, look an entry further down than you expect, because the closing twenty minutes of a fixture often sit inside the next programme.

What re-pointing actually changes

Every channel holds two pointers that have nothing to do with each other. One says where the video comes from. The other is a short identity code that has to match a code inside the guide file. When the two agree, listings appear. When they do not, the row is empty and the video is unaffected either way.

Re-pointing means changing one of those and leaving the other alone. A channel that plays perfectly but shows the wrong programmes needs its identity re-pointed, because the code was matched against the wrong entry. A channel with flawless listings and a stalling picture needs its source re-pointed instead. Two different jobs, which is why a reply sometimes fixes half of what you reported.

The mismatch that catches everyone out is the timeshift variant. Plenty of broadcasters run a copy of a channel delayed by exactly one hour, and if a code has been matched to that copy, that channel is out by an hour while its neighbours are correct. It looks exactly like a timezone problem, and no timezone setting will touch it.

Reporting it so it gets fixed once

Send the channel name exactly as written in your list, the group it sits in, one programme title, the time the guide gave it and the time it really started. Then add the line that does most of the work: say whether other channels in that group are wrong by the same amount. A whole group out together points at one source file and a single edit that fixes it for everybody. One channel out alone points at an identity mismatch and a two-minute change. Without that line somebody has to open a dozen channels to find out which.

None of this belongs to one provider

All of it is a property of the file formats rather than of any particular service, which is why the same offset setting appears in every player under a different name. Instructions written for your exact device are often a quicker route to that setting than the manual for the app you are using.

Trex IPTV Official publishes device-by-device setup pages for its own separate subscription, and the timezone and first-build steps there are the same two described above, worded for different apps. Read whichever version names the box in front of you.

The reason to learn the difference is narrow and practical. Only one of these shapes of error is a provider fault, and knowing which you have is the difference between a message answered the same afternoon and a fortnight of changing settings that were never wrong.