Time difference between Madīnat Ḩamad and London
London is 2 hours behind Madīnat Ḩamad.
Local time in both cities
Madīnat Ḩamad · Bahrain
05:51
London · United Kingdom
03:51
London is 2 hours behind Madīnat Ḩamad.
same day
Time zones
| Madīnat Ḩamad | Asia/Bahrain · UTC+03:00 |
|---|---|
| London | Europe/London · UTC+01:00 |
Madīnat Ḩamad does not observe daylight saving and stays on UTC+03:00 all year.
London is currently on daylight saving time (UTC+01:00). Next change: 2026-10-25 01:00.
Hour-by-hour conversion
Calculated for 2026-09-21 local time in Madīnat Ḩamad. The two places start and end daylight saving on different dates, so another day can give a different result.
| Madīnat Ḩamad (source) | London (target) |
|---|---|
| 00:00 | 22:00 prev day |
| 01:00 | 23:00 prev day |
| 02:00 | 00:00 |
| 03:00 | 01:00 |
| 04:00 | 02:00 |
| 05:00 | 03:00 |
| 06:00 | 04:00 |
| 07:00 | 05:00 |
| 08:00 | 06:00 |
| 09:00 | 07:00 |
| 10:00 | 08:00 |
| 11:00 | 09:00 |
| 12:00 | 10:00 |
| 13:00 | 11:00 |
| 14:00 | 12:00 |
| 15:00 | 13:00 |
| 16:00 | 14:00 |
| 17:00 | 15:00 |
| 18:00 | 16:00 |
| 19:00 | 17:00 |
| 20:00 | 18:00 |
| 21:00 | 19:00 |
| 22:00 | 20:00 |
| 23:00 | 21:00 |
Other common differences from Madīnat Ḩamad
FAQ
- How many hours apart are Madīnat Ḩamad and London right now?
- The answer at the top of the page is calculated for the current moment and states which side is ahead. The gap changes during the year, because the two places usually start and end daylight saving on different dates.
- Is this difference the same all year?
- Not necessarily. Madīnat Ḩamad uses Asia/Bahrain and London uses Europe/London; if either observes daylight saving, the gap shifts during the year. Use “Convert a specific date and time” below to calculate it for a given day.
- How do I read the conversion table?
- The left column lists each whole hour in Madīnat Ḩamad; the right column is the local time in London at that same instant, with date rollovers marked. On the day clocks jump forward, some hours do not exist locally — the table says so instead of showing a plausible but wrong value.