North American Timezones Explained
World Cup venues span multiple US timezones. During June–July (summer), daylight saving time is active everywhere:
- ET (Eastern) — New York, Miami, Boston, Atlanta = UTC−4
- CT (Central) — Dallas, Kansas City, Chicago = UTC−5
- MT (Mountain) — Denver = UTC−6
- PT (Pacific) — Los Angeles, Seattle, San Francisco = UTC−7
- Mexico City — CDT, same as Central Time in summer = UTC−5
💡 Easy rule: Most official match times are published in ET (Eastern Time). During the tournament, ET = UTC−4. So a 3:00 PM ET match = 19:00 UTC. Add your UTC offset to get your local time.
Conversion Table — Major Timezones
| ET (NY) | UTC | BST (UK) | CEST (DE/FR) | IST (India) | CST (China) | AEST (Sydney) |
|---|---|---|---|---|---|---|
| 12:00 PM | 16:00 | 17:00 | 18:00 | 21:30 | 00:00+1 | 02:00+1 |
| 3:00 PM | 19:00 | 20:00 | 21:00 | 00:30+1 | 03:00+1 | 05:00+1 |
| 6:00 PM | 22:00 | 23:00 | 00:00+1 | 03:30+1 | 06:00+1 | 08:00+1 |
+1 means the following calendar day. All times use summer/daylight saving rules active during the World Cup.
Why Manual Conversion Goes Wrong
- Some countries observe daylight saving time; others don't — and some change dates mid-tournament
- India (UTC+5:30) and Nepal (UTC+5:45) have 30 and 45-minute offsets that catch people out
- A 6 PM ET match is already the next calendar day in Japan, South Korea, and Australia
- Some regions in a country use a different timezone than the capital (e.g. parts of Australia, Russia, Brazil)
The Easiest Solution
TimeForMatch.com reads your device's timezone automatically using the browser's built-in Intl API — the same system your phone uses to set its clock. Every one of the 104 World Cup matches is instantly converted to your exact local time. No settings, no calculations, no room for error.
⏰ See All 104 Matches in Your Local Time
Automatic timezone conversion for every World Cup 2026 match. Works everywhere in the world.
Open TimeForMatch →Frequently Asked Questions
What if my timezone has a 30 or 45-minute offset?
TimeForMatch handles all offsets correctly including India (UTC+5:30), Nepal (UTC+5:45), and other non-standard timezones. The browser API accounts for these automatically.
Does it account for daylight saving time?
Yes. The Intl.DateTimeFormat browser API automatically applies the correct daylight saving rules for your specific location and the date of each match.
What if I'm travelling?
Times reflect your device's current timezone setting. If you're travelling and want your home timezone, adjust your device's timezone in settings, or use the manual converter on the site.
Why do different sources show different times?
Always check which timezone a source is using — ET, CT, and UTC are all different. TimeForMatch always shows your local time, removing any ambiguity.