Time difference between Pekalongan and London
London is 6 hours behind Pekalongan.
Local time in both cities
Pekalongan · Indonesia
06:41
London · United Kingdom
00:41
London is 6 hours behind Pekalongan.
same day
Time zones
| Pekalongan | Asia/Jakarta · UTC+07:00 |
|---|---|
| London | Europe/London · UTC+01:00 |
Pekalongan does not observe daylight saving and stays on UTC+07: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 Pekalongan. The two places start and end daylight saving on different dates, so another day can give a different result.
| Pekalongan (source) | London (target) |
|---|---|
| 00:00 | 18:00 prev day |
| 01:00 | 19:00 prev day |
| 02:00 | 20:00 prev day |
| 03:00 | 21:00 prev day |
| 04:00 | 22:00 prev day |
| 05:00 | 23:00 prev day |
| 06:00 | 00:00 |
| 07:00 | 01:00 |
| 08:00 | 02:00 |
| 09:00 | 03:00 |
| 10:00 | 04:00 |
| 11:00 | 05:00 |
| 12:00 | 06:00 |
| 13:00 | 07:00 |
| 14:00 | 08:00 |
| 15:00 | 09:00 |
| 16:00 | 10:00 |
| 17:00 | 11:00 |
| 18:00 | 12:00 |
| 19:00 | 13:00 |
| 20:00 | 14:00 |
| 21:00 | 15:00 |
| 22:00 | 16:00 |
| 23:00 | 17:00 |
Other common differences from Pekalongan
FAQ
- How many hours apart are Pekalongan 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. Pekalongan uses Asia/Jakarta 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 Pekalongan; 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.