The distinction that matters
A local time without a date or location can be ambiguous. Countries can have multiple time-zone locations, and a location can follow seasonal rules. A programme may also fall on a different local date after conversion from UTC. Keep the full instant rather than only changing the hour shown on a poster.
A controlled way to check
Use the actual published UTC start time and the viewing location. The country planner accepts that dated input and displays a local result using the browser’s time-zone rules. Its static reference tables provide a separate, explicitly dated IANA-based example. A conversion tool does not verify the fixture, broadcaster schedule or source availability.
An illustrative comparison
For instance, an event announced late in the UTC evening may occur on the following local date for another viewer. Saving only the converted hour loses that distinction. Another viewer might use a country’s capital despite living in a different time-zone location. Naming the city and retaining the date makes the enquiry more precise.
What to record or ask next
If a browser does not recognise a location, do not replace it with an invented fixed offset. Use the dated reference and the broadcaster’s actual schedule. Report the input UTC instant, selected location and displayed result when discussing a mismatch.
Guide time offsets: compare one dated programme first
An apparent schedule shift can involve the source edition, guide data, device clock or selected viewing location. The date matters because seasonal clock rules can change a location’s UTC offset. A programme on a different regional feed may also be a different schedule rather than an incorrectly displayed time.
Record one known programme, its displayed start time, the expected dated local time and the exact feed. Confirm the viewing city and the device’s date/time information. Use a named time-zone reference when converting a published UTC start. Keep the original configuration before making a relevant adjustment, and compare the same programme again afterwards.
For example, a programme appears one hour away from a broadcaster’s dated schedule. Before changing a setting, confirm that both references describe the same regional edition and date. If they do, the device/location comparison becomes useful. If they describe different editions, a clock correction could make other guide entries less accurate.
A clear report includes both times, the date, city, feed and player version. Do not turn one successful correction into a permanent rule for every country or future fixture. Use the country reference planner for a specific UTC instant.
Seasonal clock changes and programme-guide checks
A named time-zone location describes more than its current offset. Its rules can change by date, and some clock transitions repeat or skip local times. A country label or a familiar abbreviation may not identify the viewing location precisely enough. Keep the programme date, source edition and actual city with any time complaint.
Choose a known programme with a published dated start. Record the player’s displayed time, expected local time and location setting before changing a value. If the source schedule is given in UTC, convert that exact instant. Compare the result on the actual date instead of copying an offset from an older screenshot or another country.
Imagine that a guide comparison was correct in one month and differs later in the year. That change is evidence to investigate, not proof that the service randomly moved the programme. Confirm the date and regional edition, then the relevant location rule. A repeated local clock interval is another reason to retain UTC in the test record.
Use the country planner and actual broadcaster schedule as separate references. The planner converts an input; it does not certify a fixture or repair an account. Do not apply a global correction to every source after comparing only one ambiguous listing.