The single most surprising fact about this pair? As fixed abbreviations, EST is always 6 hours behind BST. But right now, neither zone is what it seems: the US East Coast is on Eastern Daylight Time (EDT, UTC−4), and the UK is on British Summer Time (BST, UTC+1). That 6-hour gap is the number you need for most of the year.
Why is London sometimes 4 hours ahead of New York?
The actual gap between New York and London is not constant. It depends entirely on where each region sits in its daylight-saving cycle.
From 29 March to 24 October 2026, the UK is on BST (UTC+1) while the US East Coast is on EDT (UTC−4). That's a 5-hour gap. London is 5 hours ahead of New York. If it's 09:00 in New York, it's 14:00 in London.
Here's the catch most people miss: for a few weeks each year, the UK has already fallen back to Greenwich Mean Time (GMT, UTC+0), but the US is still on EDT. During that brief window, the gap narrows to 4 hours.
In 2026, that happens from 25 October to 31 October. In 2027, it happens from 31 October to 6 November.
And there's an even shorter gap in March: the US springs forward to EDT before the UK switches to BST. In 2026, from 8 March to 28 March, London is only 4 hours ahead. In 2027, that window runs from 14 March to 27 March.
When do the clocks change for EST and BST?
The dates matter more than the offsets. Here's the schedule you need:
Eastern Time (US): - 8 March 2026: 02:00 EST → 03:00 EDT (clocks forward) - 1 November 2026: 02:00 EDT → 01:00 EST (clocks back) - 14 March 2027: 02:00 EST → 03:00 EDT (clocks forward) - 7 November 2027: 02:00 EDT → 01:00 EST (clocks back)
British Time (UK): - 29 March 2026: 01:00 GMT → 02:00 BST (clocks forward) - 25 October 2026: 02:00 BST → 01:00 GMT (clocks back) - 28 March 2027: 01:00 GMT → 02:00 BST (clocks forward) - 31 October 2027: 02:00 BST → 01:00 GMT (clocks back)
How to convert EST to BST without getting it wrong
The most common error is assuming "EST" means "Eastern Time" all year. It doesn't. EST is the winter-only label (UTC−5). Using it in July gives you a wrong conversion by an hour.
Do this instead:
Step 1: Check the date. Is the US on EDT or EST? Is the UK on BST or GMT?
Step 2: Determine the gap. From late March to late October: 5 hours. From early November to mid-March: 5 hours again (EST vs GMT). The only 4-hour windows are the brief transition periods in late October/early November and late March.
Step 3: Add the hours. Converting from New York to London and it's 09:00 EDT? Add 5 hours to get 14:00 BST. It's 09:00 EST? Add 5 hours to get 14:00 GMT.
The way this goes wrong: someone sees "EST" in a schedule, assumes it's UTC−5 year-round, and forgets the US is on EDT in summer. Then they're an hour off.
What is the best meeting overlap from EST to BST?
Book calls between 09:00 and 12:00 New York time. That hits 14:00 to 17:00 in London when the gap is 5 hours. A 3-hour window.
When the gap shrinks to 4 hours during the transition weeks, the overlap stretches to 09:00 to 13:00 New York time. A 4-hour window.
Skip the UK morning entirely. It's still the middle of the night on the US East Coast. Aim for the UK afternoon, which is the US morning. That's where the overlap lives.
Why does everyone get EST and BST wrong?
The deeper issue is that "EST" is a lazy shorthand for "Eastern Time" that persists in software, schedules, and even news broadcasts. The IANA database calls the zone America/New_York, and it switches between EST and EDT automatically. Your computer does this right. Your calendar app does this right. But a printed schedule that says "EST" in July? That's wrong.
If you see "EST" used during US daylight-saving months, the safest assumption is that the author meant Eastern Daylight Time, not the literal UTC−5 standard.