---
title: "What is BST (British Summer Time)?"
url: https://meet.barq.dev/glossary/bst-british-summer-time
updated: 2026-11-17
author: "Hammad Ali"
---

# What is BST (British Summer Time)?

> **Short answer:** BST, British Summer Time, is the UK's summer clock label at UTC+01:00, one hour ahead of UTC; London's clock at 09:00 on 15 July 2026 corresponds to 08:00 UTC. It isn't a year-round synonym for London time, so attach a date and location to every manually proposed appointment.


## When is London on British Summer Time in 2026?

London moves onto British Summer Time on 29 March 2026 and returns to its winter clock on 25 October 2026 under the checked transition schedule. The date matters. A July appointment and a November appointment can share a London clock hour while corresponding to different UTC hours.


The checked UK transition times are 01:00 for the March change and 02:00 for the October change. Sources: timeanddate's [spring 2026 table](https://www.timeanddate.com/time/dst/2026a.html) and [autumn 2026 table](https://www.timeanddate.com/time/dst/2026b.html), as of 17 November 2026.


Don't apply these dates to every country that changes clocks. The [time-zone abbreviations guide](https://meet.barq.dev/glossary/time-zone-abbreviations) explains why the city and date carry information that a short suffix can't supply on its own.


## How do you convert a BST meeting to UTC?

Subtract one hour from a British Summer Time reading to express the same instant in UTC, retaining the date when the conversion crosses midnight. For the London example below, 09:00 on 15 July 2026 becomes 08:00 UTC. Keep both labels visible.


| London appointment | Calculated offset | Same instant in UTC |
| --- | --- | --- |
| 15 January 2026, 09:00 | UTC+00:00 | 15 January, 09:00 |
| 15 July 2026, 09:00 | UTC+01:00 | 15 July, 08:00 |

We calculated the table using Luxon and Europe/London. The research identifies [IANA's time-zone database](https://www.iana.org/time-zones) and [its change history](https://data.iana.org/time-zones/tzdb/NEWS) as the named-zone sources, as of 17 November 2026.


For a forty-five-minute July call, the London interval 09:00 to 09:45 is 08:00 to 08:45 UTC. Conversion preserves the duration; it changes the clock labels used to describe it.


## Why shouldn't a summer London meeting say GMT?

A literal GMT instruction uses a zero-offset clock, while the London July example uses UTC+01:00, so the two instructions differ by an hour. Name London's clock explicitly. Don't make the guest infer what your suffix was meant to say.


Suppose an email promises 09:00 GMT on 15 July but the host intends 09:00 London time. A recipient following the stated zero offset would join at 10:00 in London, after the intended start.


The [GMT and UTC terminology comparison](https://meet.barq.dev/glossary/gmt-vs-utc) separates reference clocks from seasonal London time. The [glossary's other time definitions](https://meet.barq.dev/glossary/scheduling-glossary) help when an invitation mixes offsets and zone names.


## Can Barq Meet offer hours in London's local clock?

Barq Meet can attach availability hours to Europe/London and display the resulting appointment choices in the guest's selected zone, keeping the host's offered hours local. We store a schedule zone alongside its hours. That avoids treating BST as a permanent fixed offset. For a conversation spanning [dated London and Lagos hours](https://meet.barq.dev/meeting-planner/london-and-lagos), check the shared workday before repeating a familiar start in another season.


We support date overrides when one particular day needs different availability. We also check selected Google calendars again during booking, because a correctly converted time can still have become busy after the guest opened the page.


Conversion isn't conflict detection. Hosts who keep their working calendar only in iCloud can't connect that calendar to Barq Meet; the calendar connection currently uses Google accounts.


Check [what's included for international bookings](https://meet.barq.dev/pricing), then [offer London-time appointments through a booking link](https://meet.barq.dev/app/sign-in).

## Frequently asked questions

### Is BST the same as UTC?

No. British Summer Time is one hour ahead of UTC. In the dated London summer example, 09:00 BST is 08:00 UTC; treating those clock readings as identical would make the proposed appointment an hour late. Use Europe/London for dated conversions when the meeting follows London's clock, keeping BST only for dates on which it applies.

### Can I write BST on every London invitation?

Use London time with a date instead. London's January and July examples have different offsets, so putting BST on an appointment throughout the year can contradict the local clock you intended the guest to follow. Check the actual appointment date before writing the abbreviation, especially when sending an invitation weeks before a UK clock change.

### Does the guest have to change their own clock to BST?

No. The guest can read the agreed appointment in their own local zone. Confirm the full date and time in the calendar invitation, especially if the conversion puts the meeting on a different day for either person. Guests can use their local display zone and compare the full date, instead of manually changing their device to the host's clock.

## Related pages

- [GMT vs UTC: what's the difference?](https://meet.barq.dev/glossary/gmt-vs-utc)
- [Time zone abbreviations list for scheduling](https://meet.barq.dev/glossary/time-zone-abbreviations)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)
- [Best time to meet: London and Lagos (2026)](https://meet.barq.dev/meeting-planner/london-and-lagos)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
