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