Explore · time zones
London to Brunei converter
UK Time (GMT/BST) (London) → Brunei Time (Bandar Seri Begawan)
Quick answer
The difference changes with daylight saving time. Bandar Seri Begawan is 8 hours ahead of London from Jan 1, 2026 to Mar 29, 2026 01:00 UTC (London on GMT · UTC+0); 7 hours ahead of London from Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTC (London on BST · UTC+1); 8 hours ahead of London from Oct 25, 2026 01:00 UTC to Dec 31, 2026 (London on GMT · UTC+0).
- Jan 1, 2026 to Mar 29, 2026 01:00 UTCLondon (GMT, UTC+0) → Bandar Seri Begawan (UTC+8)Bandar Seri Begawan is 8 hours ahead of London
- Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTCLondon (BST, UTC+1) → Bandar Seri Begawan (UTC+8)Bandar Seri Begawan is 7 hours ahead of London
- Oct 25, 2026 01:00 UTC to Dec 31, 2026London (GMT, UTC+0) → Bandar Seri Begawan (UTC+8)Bandar Seri Begawan is 8 hours ahead of London
9:00 AM GMT (UTC+0) in London is 5:00 PM UTC+8 in Bandar Seri Begawan, the same day. Bandar Seri Begawan is 8 h ahead of London.
| Format | Result | Copy |
|---|---|---|
| Bandar Seri Begawan, BruneiWednesday, January 14, 2026 · the same day | 5: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768381200 | |
| RFC 2822UTC | Wed, |
Conversions use London (Europe/London) and Bandar Seri Begawan (Asia/Brunei). Other cities reached through search aliases may have different historical rules.
Current time in London and Bandar Seri Begawan
Hour by hour: London (GMT, UTC+0) → Bandar Seri Begawan (UTC+8)
There is no time when both London and Bandar Seri Begawan are inside 9:00–17:00.
| London | Bandar Seri Begawan | Day |
|---|---|---|
| 12:00 AM | 8:00 AM | same day |
| 1:00 AM | 9:00 AM | same day |
| 2:00 AM | 10:00 AM | same day |
| 3:00 AM | 11:00 AM | same day |
| 4:00 AM | 12:00 PM | same day |
| 5:00 AM | 1:00 PM | same day |
| 6:00 AM | 2:00 PM | same day |
| 7:00 AM | 3:00 PM | same day |
| 8:00 AM | 4:00 PM | same day |
| 9:00 AM | 5:00 PM | same day |
| 10:00 AM | 6:00 PM | same day |
| 11:00 AM | 7:00 PM | same day |
| 12:00 PM | 8:00 PM | same day |
| 1:00 PM | 9:00 PM | same day |
| 2:00 PM | 10:00 PM | same day |
| 3:00 PM | 11:00 PM | same day |
| 4:00 PM | 12:00 AM | next day |
| 5:00 PM | 1:00 AM | next day |
| 6:00 PM | 2:00 AM | next day |
| 7:00 PM | 3:00 AM | next day |
| 8:00 PM | 4:00 AM | next day |
| 9:00 PM | 5:00 AM | next day |
| 10:00 PM | 6:00 AM | next day |
| 11:00 PM | 7:00 AM | next day |
Hour by hour: London (BST, UTC+1) → Bandar Seri Begawan (UTC+8)
Both sides are inside 9:00–17:00 from 9:00 AM to 10:00 AM BST (UTC+1) in London (1 hour).
| London | Bandar Seri Begawan | Day |
|---|---|---|
| 12:00 AM | 7:00 AM | same day |
| 1:00 AM | 8:00 AM | same day |
| 2:00 AM | 9:00 AM | same day |
| 3:00 AM | 10:00 AM | same day |
| 4:00 AM | 11:00 AM | same day |
| 5:00 AM | 12:00 PM | same day |
| 6:00 AM | 1:00 PM | same day |
| 7:00 AM | 2:00 PM | same day |
| 8:00 AM | 3:00 PM | same day |
| 9:00 AM | 4:00 PM | same day |
| 10:00 AM | 5:00 PM | same day |
| 11:00 AM | 6:00 PM | same day |
| 12:00 PM | 7:00 PM | same day |
| 1:00 PM | 8:00 PM | same day |
| 2:00 PM | 9:00 PM | same day |
| 3:00 PM | 10:00 PM | same day |
| 4:00 PM | 11:00 PM | same day |
| 5:00 PM | 12:00 AM | next day |
| 6:00 PM | 1:00 AM | next day |
| 7:00 PM | 2:00 AM | next day |
| 8:00 PM | 3:00 AM | next day |
| 9:00 PM | 4:00 AM | next day |
| 10:00 PM | 5:00 AM | next day |
| 11:00 PM | 6:00 AM | next day |
Worked examples
| When | London | Bandar Seri Begawan | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 2:00 PM GMT (UTC+0), January 14, 2026 | 10:00 PM UTC+8, January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 3:00 PM BST (UTC+1), July 15, 2026 | 10:00 PM UTC+8, July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 12:00 AM GMT (UTC+0), January 1, 2027 | 8:00 AM UTC+8, January 1, 2027 | 2027-01-01T00:00:00.000Z | 1798761600 |
The ISO 8601 and Unix columns are the same instant written without a zone — how APIs and databases should store it. Need this for a whole column? Convert a CSV file.
London — UK Time (GMT/BST)
- IANA identifier
- Europe/London
- Standard time
- GMT · UTC+0
- Daylight time
- BST · UTC+1
- On this clock today
- London, Edinburgh, Cardiff, Belfast, Dublin
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Europe/London; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 29, 2026, 2:00 AM local (2026-03-29 01:00 UTC): clocks go forward to UTC+1 (BST)
- Oct 25, 2026, 1:00 AM local (2026-10-25 01:00 UTC): clocks go back to UTC+0 (GMT)
- Mar 28, 2027, 2:00 AM local (2027-03-28 01:00 UTC): clocks go forward to UTC+1 (BST)
- Oct 31, 2027, 1:00 AM local (2027-10-31 01:00 UTC): clocks go back to UTC+0 (GMT)
GMT (UTC+0) in winter, BST (UTC+1) from the last Sunday of March to the last Sunday of October. Ireland follows the same clock and calls summer time IST (Irish Standard Time), not to be confused with India Standard Time.
Brunei — Brunei Time
- IANA identifier
- Asia/Brunei
- UTC offset
- UTC+8
- Daylight saving
- Not observed
- On this clock today
- Bandar Seri Begawan, Brunei
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Asia/Brunei; a listed place's past or future rules may differ.
Related conversions
File workspace
Converting a whole column of timestamps?
The free converter handles one value at a time across 82 formats and 92 zones. The file workspace converts an entire CSV column between any two formats and zones, previews the first rows, and leaves unreadable cells exactly as they were.
Offsets and change dates on this page are computed from IANA time zone database 2026f for 2026–2027; the live tool uses the same data.