Time Zones Explained: Why Kickoff Isn't When You Think
The most common reason fans miss the first whistle isn't a wrong schedule. It's an unconverted time. UTC, daylight saving and half-hour zones, explained.
You read "20:00 kickoff," you show up at 20:00, and the match is already twenty minutes old. The number wasn't wrong; it just wasn't yours. Almost every schedule quotes kickoff in the stadium's local time, and unless you happen to live in that zone, that number needs converting before it means anything to you.
One match, one moment, many clocks
A football match kicks off at a single instant. What changes is the number on the clock in each country. The clean way to handle that is to store the kickoff once in UTC, Coordinated Universal Time, the global reference the internet runs on, and convert from there to wherever you happen to be.
That's what When Is Kickoff does: one UTC time in, your local time out, using the same time-zone database (the IANA database) that your phone's clock already trusts. It's why a match reads correctly whether you open it in Berlin, São Paulo or Los Angeles. (Our disclaimer describes how the time zone detection works.)
Why "local time" is slippery
Time zones aren't tidy. They don't follow neat hour lines: India is UTC+5:30, Nepal is +5:45, parts of Australia are +9:30. Any shortcut that assumes every zone is a whole number of hours off will be wrong for hundreds of millions of people.
And a European evening match is a next-day match for much of the world. A 21:00 kickoff in Madrid is early the following morning in Tokyo or Sydney, so the date changes, not just the time. Miss that and you'll set your alarm for the wrong day, not just the wrong hour.
Daylight saving: the twice-a-year trap
The bigger trap is daylight saving time, because it moves, and different regions move on different dates. Europe changes its clocks on the last Sunday of March (forward) and the last Sunday of October (back). North America doesn't match those dates: it springs forward on the second Sunday of March and falls back on the first Sunday of November.
Those mismatched dates open a gap. For about two weeks each spring, North America has already moved its clocks while Europe hasn't yet, so the usual distance between, say, the UK and New York is an hour smaller than normal. It happens again for a week or so in autumn, in the other direction. If your rule of thumb is "the match is always five hours earlier for me," twice a season you'll be exactly one hour out, and both times land in the thick of the fixtures.
Not everyone plays this game. Most of Asia and Africa don't observe daylight saving at all; Brazil scrapped it in 2019. So a fan in São Paulo, one in Lagos and one in London drift relative to each other across the year even though none of them touched a clock, simply because some regions switch and others don't.
Why a good converter earns its keep
All of this is why "just add X hours" quietly fails. The reliable way to know when a match starts for you is to convert the exact UTC kickoff to your zone with the daylight-saving rules for that specific date built in. Do it by hand and you have to know both regions' switch dates and whether either is mid-change. Let software do it and you don't have to think about any of it.
On every match page, the time you see is already converted to your device's time zone, with the correct daylight-saving offset for that date. Set a reminder and it's timed against the real kickoff, not against a number you'd otherwise have to translate in your head. (And if the kickoff itself moves, the reminder moves with it.)
The bottom line
Time zones are the quiet reason fans miss the opening whistle: not because the schedule is wrong, but because a kickoff time only means something once it's in your time. Get the conversion right, with daylight saving handled, and "20:00" finally means 20:00 for you.