How to Convert Kickoff Times to Your Time Zone (Without Mistakes)

Most missed kickoffs come from three traps. First, sources mix reference points: some list venue-local time, some broadcaster time, some UTC. Second, daylight saving time shifts differently around the world — the US changes clocks in March and November, Europe in March and October, and much of Asia, Africa and Latin America not at all. For a few weeks each year, the usual gap between New York and London is wrong. Third, late kickoffs cross midnight: a 21:00 match in New York is 03:00 the next day in Berlin, so 'Tuesday's game' is actually Wednesday for you.

UTC (Coordinated Universal Time) is the fixed reference every other time zone is defined against. It never changes for summer, which is why it is the right anchor for a fixture list. GMT is numerically the same as UTC, but in everyday use it names the UK's winter clock. From late March to late October the UK is on British Summer Time, UTC+1, so a listing that says '15:00 GMT' for a July match in England is usually mislabelled: the kick-off is 15:00 UK time, which is 14:00 UTC.

North American abbreviations cause the same problem. 'ET' means Eastern Time, which is EDT (UTC−4) for most of the year and EST (UTC−5) in winter; 'PT' is likewise UTC−7 or UTC−8. Central European Time is UTC+1 in winter and UTC+2 (CEST) in summer. A schedule that gives the abbreviation but not the date can be an hour out if you assume the wrong half of the year.

Some offsets are not whole hours, which defeats quick mental arithmetic. India is on UTC+5:30 all year with no daylight saving, Nepal on UTC+5:45, and parts of Australia on half-hour offsets too: Adelaide is UTC+9:30 in winter and UTC+10:30 in summer. Turkey has stayed on UTC+3 all year since 2016, so its gap to the rest of Europe changes twice a year even though its own clocks do not.

The United States and Canada move their clocks forward on the second Sunday in March and back on the first Sunday in November. The UK and the European Union change on the last Sunday in March and the last Sunday in October, all at the same instant, 01:00 UTC. Those dates do not line up, so the normal five-hour gap between London and New York shrinks to four hours for about three weeks in March and for one week between late October and early November. Those are exactly the weeks when people who 'know' the gap miss kick-offs.

The southern hemisphere runs the other way. New South Wales, Victoria, the ACT, Tasmania and South Australia use daylight saving from the first Sunday in October to the first Sunday in April; Queensland, Western Australia and the Northern Territory do not use it at all. New Zealand moves its clocks on the last Sunday in September and the first Sunday in April. Put those calendars together and the gap between London and Sydney is nine, ten or eleven hours depending on the time of year.

Several countries have stopped changing their clocks altogether: Turkey in 2016, Brazil in 2019 and most of Mexico in 2022. That does not make them simpler to convert to, because their gap to countries that still change keeps moving.

Anchor on UTC, then apply your own offset — or better, let software do it. Your phone and computer already know your timezone and every DST rule; a site that publishes times in UTC and converts them client-side will be correct on the two weird weeks of the year when manual arithmetic fails.

A worked example shows why. A Saturday 15:00 kick-off in England is 14:00 UTC while the UK is on summer time and 15:00 UTC after the clocks go back at the end of October. For a fan in Istanbul, on UTC+3 all year, the same 15:00 UK kick-off moves from 17:00 to 18:00 overnight, even though nothing changed in Turkey. Anyone converting by a fixed rule of thumb gets one of those wrong.

Every event on MatchCountdown is stored as a single instant in UTC. The page arrives with that time written out in UTC, and your browser then rewrites it in your device's own time zone, using the time zone database built into the browser and your operating system. That database carries every country's daylight saving rules, so the conversion is right on both sides of a clock change.

Match pages also list the start time in a fixed set of reference places — New York, Los Angeles, London, Central Europe, India, Japan, Sydney and Brazil — which is useful when you are telling a friend abroad when to tune in. The countdown itself needs no conversion at all: it counts down to the same instant everywhere. And when you add a match to Google Calendar or download it as a calendar file, the start is passed in UTC, so your calendar shows it correctly even if you travel before kick-off.

Two things can still go wrong, and both are on the device. If your phone or computer is set to the wrong time zone, every converted time will be wrong by the same amount, so check the time zone setting before blaming the fixture. And a VPN does not change the times you see: the browser takes your time zone from the device, not from the network location the VPN gives you.

The hour is only half the conversion; the date is the other half. A Monday night game in the United States is Tuesday morning in Europe and Tuesday afternoon in Asia. A Test match in Australia that starts at 10:30 local time begins the previous evening in the UK. When you convert a time, check the weekday and date as well, especially for anything that kicks off late in the evening or early in the morning where it is played.

During multi-timezone tournaments like World Cup 2026, whose venues covered four UTC offsets across North America, ignore venue-local listings altogether and work from a single converted schedule. Add matches you care about to your own calendar — calendar apps store events in UTC internally, so the times will stay correct even if you travel mid-tournament.

If a tournament straddles a daylight saving change, as autumn fixture lists in Europe and North America often do, double-check matches in the week after the change. That is where a time copied into a group chat a fortnight earlier is most likely to be an hour out.