Time difference between London and Biratnagar
Biratnagar is 4 hours 45 minutes ahead of London.
Local time in both cities
London · United Kingdom
00:38
Biratnagar · Nepal
05:23
Biratnagar is 4 hours 45 minutes ahead of London.
same day
Time zones
| London | Europe/London · UTC+01:00 |
|---|---|
| Biratnagar | Asia/Kathmandu · UTC+05:45 |
London is currently on daylight saving time (UTC+01:00). Next change: 2026-10-25 01:00.
Biratnagar does not observe daylight saving and stays on UTC+05:45 all year.
Hour-by-hour conversion
Calculated for 2026-09-21 local time in London. The two places start and end daylight saving on different dates, so another day can give a different result.
| London (source) | Biratnagar (target) |
|---|---|
| 00:00 | 04:45 |
| 01:00 | 05:45 |
| 02:00 | 06:45 |
| 03:00 | 07:45 |
| 04:00 | 08:45 |
| 05:00 | 09:45 |
| 06:00 | 10:45 |
| 07:00 | 11:45 |
| 08:00 | 12:45 |
| 09:00 | 13:45 |
| 10:00 | 14:45 |
| 11:00 | 15:45 |
| 12:00 | 16:45 |
| 13:00 | 17:45 |
| 14:00 | 18:45 |
| 15:00 | 19:45 |
| 16:00 | 20:45 |
| 17:00 | 21:45 |
| 18:00 | 22:45 |
| 19:00 | 23:45 |
| 20:00 | 00:45 next day |
| 21:00 | 01:45 next day |
| 22:00 | 02:45 next day |
| 23:00 | 03:45 next day |
Other common differences from London
FAQ
- How many hours apart are London and Biratnagar 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. London uses Europe/London and Biratnagar uses Asia/Kathmandu; 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 London; the right column is the local time in Biratnagar 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.