To convert a kickoff time, take the time in the stadium’s local zone, turn it into UTC, then apply your own offset for that specific date. The date is what trips people up this month: Europe changes its clocks on 25 October 2026 and the US and Canada follow on 1 November, so the gap between them changes in between.
What do you need before you start?
You need three things: the kickoff time as published, the time zone that time refers to, and the date of the match. Without the zone, a time like 15:00 is just a number. Most fixture lists state it, and if yours does not, treat the time as unconfirmed until you find the league or club’s own page.
A general sports site can also help you cross-check. For example, this multi-sport schedule lookup page is a general sports site covering football, basketball and tennis, and it is one place to compare fixture dates and times. Whatever source you use, confirm the zone behind the time before you convert it.
Why do kickoff times shift in late October?
Because Europe and North America do not change their clocks on the same day. Europe moves back one hour on Sunday 25 October 2026 at 01:00 UTC. In the UK that means 2:00 goes back to 1:00 (BST to GMT), in Central Europe 3:00 goes back to 2:00 (CEST to CET), and in Eastern Europe 4:00 goes back to 3:00 (EEST to EET). It is one single moment in UTC, shown differently on each local clock.
The US and Canada move back a week later, on Sunday 1 November 2026, at 2:00 local time (back to 1:00). That leaves a one-week window, 25 October to 1 November, when the London–New York gap shrinks from 5 hours to 4.
The same thing happens in spring, in reverse. The US started daylight saving on 8 March 2026 and the EU and UK started on 29 March, so there is another mismatched window from 8 to 29 March. The US switches on the second Sunday of March and the first Sunday of November, while the EU and UK switch on the last Sunday of March and October. The EU has kept the twice-yearly change for now, despite strong opposition in its 2018 consultation, so expect these windows to return.
How do you convert a kickoff time, step by step?
- Write down the original time and its zone. For a UK fixture, check whether it is BST or GMT on that date. UK clocks are on BST until 25 October and on GMT after.
- Convert it to UTC. In the UK, BST is one hour ahead of UTC and GMT equals UTC. Working through UTC avoids guessing which side of a clock change you are on.
- Apply your own offset for the match date, not for today. This is the step most people skip. If you are in New York and the match is on 28 October, use EDT, which is 4 hours behind UTC. If it is on or after 1 November, use EST, which is 5 hours behind.
- Check whether the day changes. A late evening kickoff in Europe can land after midnight on your clock, which puts it on the next calendar date for you.
- Save the result as a calendar event with the correct time zone (see the next section).
- Re-check after the clocks change. Look at every saved fixture in the week after 25 October and again after 1 November.
Here is a worked example for a hypothetical 15:00 UK kickoff. It matches the logic above, but it is not a real fixture, so replace it with your own match.
| Match date | UK clock | UTC | New York | Vietnam (UTC+7) |
|---|---|---|---|---|
| Sat 24 Oct | 15:00 BST | 14:00 | 10:00 EDT | 21:00 |
| Wed 28 Oct | 15:00 GMT | 15:00 | 11:00 EDT | 22:00 |
| Sat 7 Nov | 15:00 GMT | 15:00 | 10:00 EST | 22:00 |
The same 15:00 UK kickoff shows up at 10:00, then 11:00, then 10:00 again for a viewer in New York. The Vietnam column moves by one hour once, because Vietnam does not change its clocks. That is the pattern to expect when one side changes and the other does not.
Ảnh: Sergey Norin from Moscow, Russia, Wikimedia Commons (CC BY 2.0)
How do you save a match so your calendar does not drift?
Set the event’s time zone to the one the kickoff was published in, instead of typing your own local time. A calendar that knows the event is at 15:00 in London will place it correctly on your clock even after one of you changes. Typing in 10:00 as your own local time bakes in today’s offset, and that is what breaks the following week.
The exact menu names differ between Google, Apple and Outlook, so check how your app labels the event time zone setting. After saving, view the event on a day when the offset has changed and confirm the time looks right. If a match is on the far side of a clock change, it is worth checking that one twice.
Which mistakes cause people to miss kickoff?
- Using a fixed gap. Saying London is always five hours ahead of New York is wrong for the week of 25 October to 1 November, and for 8 to 29 March. I would rather convert through UTC every time than trust a rule of thumb.
- Assuming everyone changes on the same day. The US and Europe do not, and a friend watching from elsewhere may be on a different schedule again.
- Forgetting places that do not change. Hawaii and most of Arizona stay on one offset all year, and Moscow (MSK) does not change either. Vietnam is on UTC+7 with no daylight saving, so its gap to Europe moves by one hour at each European change.
- Ignoring the date line of your own clock. A match that ends after midnight for you may be listed on a different date than your calendar shows.
- Trusting an old reminder. A reminder created months ago may not reflect the new offset unless it was saved with a time zone.
If you also like to read about the players behind the fixtures, a site such as W88 https://w88.inc/ covers football, basketball and tennis and includes football player information alongside its sports pages. Treat it as a reference for background reading, and check kickoff times against the league or club’s own published schedule.
What should you watch next?
The next mismatched window opens in March, when the US moves clocks about three weeks before Europe does. Put a reminder for the weekend before it, because that is when saved fixtures are most likely to look wrong. Until the EU actually drops its twice-yearly change, the safest habit is the one in step 2: convert through UTC and let the date decide the offset.
