# Why writing "BST" is dangerous

**Mon, 2026-06-15, 12:00 in Europe/London is Mon, 2026-06-15, 17:00 in Asia/Dhaka.**

- Input: `2026-06-15 12:00` in `Europe/London`
- Target zone: `Asia/Dhaka`
- UTC instant: 2026-06-15T11:00:00.000Z

## Readings

| Zone | Local time | Offset | Abbreviation |
| --- | --- | --- | --- |
| Europe/London | Mon, 2026-06-15, 12:00 | UTC+01:00 | GMT+1 |
| Asia/Dhaka | Mon, 2026-06-15, 17:00 | UTC+06:00 | GMT+6 |

## Warnings

### Asia/Dhaka does not observe daylight saving (info)

Asia/Dhaka keeps the same offset all year, so its clocks never change. If the other zone does observe it, the gap between them shifts twice a year even though nothing changes on this side.

## Upcoming clock changes in Europe/London

- `2026-10-25T01:00:14.062Z`: Clocks fall back an hour: the wall clock returns to 01:00, so that hour happens twice.
- `2027-03-28T01:00:14.062Z`: Clocks jump forward an hour: 02:00 is followed by 02:00, and the times in between never happen.

## Upcoming clock changes in Asia/Dhaka

None — this zone keeps one offset all year.

---

Canonical URL: https://timezone-truth.gumballtools.com/tz/why-bst-is-dangerous
JSON API: `GET https://timezone-truth.gumballtools.com/api/v1/convert?time=...&from=...&to=...`
MCP endpoint: `https://timezone-truth.gumballtools.com/api/mcp`