Time Zones

UK Time: GMT vs BST, 2026 Clock Change Dates, and Scheduling Tips

A practical guide to UK time zones: GMT in winter, BST in summer, 2026 clock change dates, and tips for scheduling across the Atlantic.

AM
Arjun Mehta

Geospatial Engineer

6. MÀrz 2026·6 Min. Lesezeit

UK Time: Two Offsets, One Country

The United Kingdom uses two time offsets throughout the year. In winter, it's Greenwich Mean Time (GMT, UTC+0). In summer, clocks advance to British Summer Time (BST, UTC+1). The switch happens twice a year, and the exact dates follow a predictable rule — though whether those rules remain unchanged is an open question post-Brexit.

The IANA identifier is Europe/London. Use this in all software — it handles the GMT/BST transition automatically. Don't use Etc/GMT or hardcode UTC+0, because you'll be wrong for seven months of the year.

The UK's timezone situation is actually simpler than most countries its geographic spread might suggest. The mainland, Northern Ireland, Wales, Scotland, and the Channel Islands all follow the same rules. Only the British Overseas Territories (Gibraltar, Bermuda, the Falklands, etc.) operate on different offsets, and they're governed separately.

2026 Clock Change Dates

EventDateTime ChangeResulting Offset
Clocks Spring ForwardSunday, 29 March 20261:00 AM → 2:00 AMBST (UTC+1)
Clocks Fall BackSunday, 25 October 20262:00 AM → 1:00 AMGMT (UTC+0)

The rule: clocks go forward on the last Sunday of March, back on the last Sunday of October. This aligns with the EU's schedule (for now — the UK is no longer bound by EU directives post-Brexit, but hasn't changed the practice). If the EU ever does abolish clock changes — a proposal that's been stalled since 2019 — the UK would face a decision: follow suit, or become the odd one out relative to its nearest trading partners.

A Brief History of British Summer Time

The Summer Time Act of 1916 first introduced BST during World War I, following a campaign by builder William Willett, who'd been lobbying for "daylight saving" since 1907. Willett never saw his idea implemented — he died in 1915, a year before the legislation passed. The original motivation was wartime energy savings: less coal burned for lighting if people's waking hours aligned better with daylight.

During World War II, Britain went further. From 1940 to 1945, the country used "Double Summer Time" — UTC+2 in summer and UTC+1 in winter. The idea was to maximize daylight hours for agricultural and industrial production. It was effective but extremely unpopular in Scotland and northern England, where winter mornings under UTC+1 were pitch dark until 9:30 or 10:00 AM.

The current BST framework was codified in the Summer Time Act 1972 and has been remarkably stable since. The only change was aligning the dates with the EU's standardized schedule in 1996 (last Sunday of March and October, rather than the previous British dates). Even after Brexit, the UK kept the same dates.

The UK-US Time Difference Is Not Constant

This catches people every year. The UK and US don't switch on the same dates. The US springs forward on the second Sunday of March; the UK waits until the last Sunday. Similarly, the US falls back on the first Sunday of November; the UK does it the last Sunday of October.

This creates awkward transition periods:

PeriodUKUS EastGap (UK − NYC)
Jan–early MarGMT (UTC+0)EST (UTC−5)5 hours
Early Mar–late MarGMT (UTC+0)EDT (UTC−4)4 hours
Late Mar–early NovBST (UTC+1)EDT (UTC−4)5 hours
Late Oct–early NovGMT (UTC+0)EDT (UTC−4)4 hours

In 2026 specifically: the US springs forward on March 8, the UK on March 29. So from March 8 to March 29, the gap is 4 hours instead of the usual 5. Then the UK falls back on October 25, while the US waits until November 1 — giving another week of 4-hour gap. These windows are short but real. I've seen entire teams miss calls over this, especially recurring meetings that were set up during the "normal" 5-hour gap period.

For UK-West Coast US, the same logic applies but the numbers are 8 hours (normal) vs 7 hours (transition). And for UK-Central US: 6 hours normally, 5 during the messy weeks.

Scheduling Tips

The sweet spot for UK–US East Coast meetings is 2:00–5:00 PM London time, which maps to 9:00 AM–12:00 PM Eastern. Start earlier in London and your US colleagues haven't had their coffee yet. Go later and you're eating into London's evening. That 2–5 PM window is the transatlantic goldilocks zone, and every company with offices in both cities fights over it.

For UK–India calls, morning UK time works well: 9:00 AM London is 2:30 PM IST (during BST) or 1:30 PM IST (during GMT). The 4.5- or 5.5-hour gap is manageable enough that most UK-India teams can maintain a solid block of overlap. This is one reason London remains a natural hub for companies with Indian development teams — the timezone overlap is significantly better than US-India.

For UK-Australia, prepare for pain. Sydney is 10 or 11 hours ahead of London depending on DST status (and whose DST — the gap oscillates because Australia and the UK switch on different dates, in different directions). The only overlap for UK-Sydney is early UK morning catching late Sydney evening, or vice versa. A 7:00 AM London meeting hits 6:00 PM Sydney during AEDT/GMT — tolerable but not great.

Always specify the timezone explicitly. Don't say "3 PM UK time" — say "3 PM GMT" or "3 PM BST" depending on the season, or better yet, "3 PM London time" and let people's calendar software sort it out. Google Calendar and Outlook both resolve Europe/London correctly, so "London time" is an unambiguous shorthand.

The Ireland Complication

Ireland follows the exact same clock change dates as the UK — clocks go forward on the last Sunday of March and back on the last Sunday of October. But here's a legal oddity: under Irish law, the "standard" time is Irish Standard Time (IST, UTC+1), which is the summer offset. Winter time in Ireland is technically the exception, not the norm. The UK defines it the opposite way: GMT is standard, BST is the exception.

In practice, this makes zero difference — the clocks show the same time in Dublin and London year-round. But the legal distinction matters for contracts or legal documents that reference "standard time." In Ireland, "standard time" is UTC+1. In the UK, "standard time" is UTC+0. If a cross-border contract says "10:00 AM standard time," you've got an ambiguity — is it 10:00 AM GMT or 10:00 AM IST?

The IANA identifier for Ireland is Europe/Dublin. It produces the same times as Europe/London, but the metadata differs to reflect Ireland's legal framework.

Double Summer Time?

Britain experimented with staying on BST year-round from 1968 to 1971. It worked well for the southeast — longer evening light in London, more time for outdoor activities after work. But it was miserable for Scotland, where winter mornings stayed dark until nearly 10 AM. Schoolchildren were walking to school in pitch darkness. Road accident data from the experiment was mixed: fewer evening accidents but a spike in morning ones, with the net effect being debated for decades.

The experiment was scrapped, and the status quo returned. There's been periodic talk since then of moving to "double summer time" (CET in winter, CEST in summer), aligning Britain with France and Germany rather than Iceland and Portugal. The arguments for it are compelling: more usable evening daylight, alignment with key European trading partners, potential tourism revenue. But Scotland's objections have kept it off the table. The political dynamics are delicate — any government that imposes dark Scottish mornings for the benefit of London commuters risks a serious backlash north of the border.

The devolved Scottish Parliament doesn't have authority over time zones — that's reserved to Westminster. But in practice, no Westminster government wants the fight. The issue has been studied by multiple select committees, most recently in 2012, and each time the recommendation has been some version of "it's probably a good idea but too politically risky." So the clocks keep changing, twice a year, as they have since 1972.

Frequently Asked Questions

When does the UK change clocks in 2026?

Clocks spring forward on Sunday, 29 March 2026 (1:00 AM becomes 2:00 AM). They fall back on Sunday, 25 October 2026 (2:00 AM becomes 1:00 AM).

How many hours between the UK and New York?

Usually 5 hours (UK is ahead). But for about three weeks in March and one week in late October/November, the gap shrinks to 4 hours because the US and UK switch DST on different dates.

Does the UK follow EU DST rules?

Currently, the UK's clock change dates match the EU schedule (last Sunday of March and October). Post-Brexit, the UK isn't legally bound by EU time directives, but it hasn't announced any plans to change. If the EU eventually abolishes seasonal clock changes, the UK would need to decide independently.

What is the IANA code for UK time?

Use Europe/London. This identifier automatically handles the switch between GMT (UTC+0) in winter and BST (UTC+1) in summer. Never hardcode a UTC offset for UK time in software.

What time is it in the UK when it's noon in New York?

Usually 5:00 PM (UK is 5 hours ahead). However, for about three weeks in March and one week in late October/November, the gap shrinks to 4 hours because the US and UK switch DST on different dates.

Is BST the same as CET?

BST (UTC+1) and CET (UTC+1) share the same offset, but they apply at different times of year. BST is UK summer time (March–October), while CET is continental European winter time (October–March). In summer, Europe moves to CEST (UTC+2), so London and Paris are one hour apart again.

Has the UK ever considered permanent summer time?

Yes. Britain tried permanent BST from 1968 to 1971, but it was scrapped because Scottish mornings stayed dark until nearly 10 AM in winter. Proposals for "double summer time" (CET/CEST) resurface periodically but face the same opposition from Scotland and Northern Ireland.

Sources

  • UK Government — Summer Time Act 1972
  • IANA Time Zone Database — Europe/London
  • Royal Observatory Greenwich — History of British Time

AM

Über den Autor

Arjun Mehta

Geospatial Engineer

Arjun Mehta is a geospatial data engineer who has spent the last twelve years building timezone-aware infrastructure for companies ranging from airline booking platforms to global logistics firms. He has contributed patches to the IANA Time


VollstĂ€ndige Bio lesen →
ZurĂŒck zum Blog

Verwandte Artikel