How Many Time Zones Are There, Really? And Why Daylight Saving Makes Your Kickoff Time a Moving Target

August 21, 2026

Most people, asked how many time zones the world has, land on 24 — one per hour, a tidy number from a school geography lesson. The real figure is 38. The gap exists because not every country lines its clock up on a clean hour. India runs on UTC+5:30. Nepal splits it further at UTC+5:45. And a small stretch of Western Australia around the town of Eucla runs on UTC+8:45 — a 45-minute offset that exists basically nowhere else on Earth, adopted informally decades ago and never standardised away.

That's the baseline, and it's already more complicated than the 24-zone picture most people carry around. Then daylight saving gets added on top, and the number stops being fixed at all — it moves twice a year, on different dates, for different countries, none of it synchronised with any of the others.

Here's the part that actually matters for anyone following sport across borders: the US, the UK and EU, and Australia don't change their clocks together. In 2026, UK and EU clocks fall back on Sunday, October 25. US clocks don't fall back until a week later, Sunday, November 1. For that one week in between, the usual gap between US Eastern time and UK time — normally five hours — is only four, because the UK has already moved to winter time and the US hasn't caught up yet. A Premier League kickoff or an NFL Sunday slot converted correctly on October 20 can be off by a full hour if you're still using the same conversion on October 28.

Australia adds a third, completely independent shift into the same stretch of the calendar. Australian clocks spring forward on Sunday, October 4, 2026 — while the Northern Hemisphere is still months from doing the reverse. So for anyone in Melbourne or Sydney following an NFL season opener, an NBA tip-off, or an F1 session from the US or Europe, the real offset to home changes not once but multiple times between early October and early November, as each region moves independently on its own date. Three regions, three different Sundays, and a fan doing the math by hand has no way of knowing which of the three shifts has already happened on any given week without checking.

It's worth saying plainly: not everywhere even participates. Queensland, Western Australia, and the Northern Territory don't observe daylight saving at all, so a fixture converted correctly for Sydney can be wrong by an hour for Brisbane the same week — the exact kind of gap that's caused real, live errors on schedule pages that only test against one region and assume the rest of the country matches.

This is really the whole problem with treating a kickoff time conversion as a one-time calculation. It isn't one. It's a conversion that's only correct until the next region on the list changes its clocks — and there's always a next region, somewhere in the six-week window every October and November where the US, the UK, the EU, and Australia are all adjusting on their own separate schedule.

SportzCal doesn't do the conversion once and hope it holds. Every game, every session, every kickoff is converted using the real, current UTC offset for your actual timezone — and for Season Pass subscribers, that conversion re-runs automatically as each region's clocks change, so a schedule that was correct in September doesn't quietly drift wrong the week the UK falls back, or the week Australia springs forward, or the week the US finally catches up a full seven days later.

Get your team's full season converted to your real, current timezone for $2.99 as a one-off download, or subscribe to the Season Pass for $19.99 a year and let your calendar handle every daylight saving shift automatically — US, UK, EU, or Australia — all season, without you ever having to notice the clocks changed at all.