Time difference between Batang Berjuntai and Tokyo
Tokyo is 1 hours ahead of Batang Berjuntai.
Local time in both cities
Batang Berjuntai · Malaysia
20:33
Tokyo · Japan
21:33
Tokyo is 1 hours ahead of Batang Berjuntai.
same day
Time zones
| Batang Berjuntai | Asia/Kuala_Lumpur · UTC+08:00 |
|---|---|
| Tokyo | Asia/Tokyo · UTC+09:00 |
Batang Berjuntai does not observe daylight saving and stays on UTC+08:00 all year.
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 Batang Berjuntai. The two places start and end daylight saving on different dates, so another day can give a different result.
| Batang Berjuntai (source) | Tokyo (target) |
|---|---|
| 00:00 | 01:00 |
| 01:00 | 02:00 |
| 02:00 | 03:00 |
| 03:00 | 04:00 |
| 04:00 | 05:00 |
| 05:00 | 06:00 |
| 06:00 | 07:00 |
| 07:00 | 08:00 |
| 08:00 | 09:00 |
| 09:00 | 10:00 |
| 10:00 | 11:00 |
| 11:00 | 12:00 |
| 12:00 | 13:00 |
| 13:00 | 14:00 |
| 14:00 | 15:00 |
| 15:00 | 16:00 |
| 16:00 | 17:00 |
| 17:00 | 18:00 |
| 18:00 | 19:00 |
| 19:00 | 20:00 |
| 20:00 | 21:00 |
| 21:00 | 22:00 |
| 22:00 | 23:00 |
| 23:00 | 00:00 next day |
Other common differences from Batang Berjuntai
FAQ
- How many hours apart are Batang Berjuntai 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. Batang Berjuntai uses Asia/Kuala_Lumpur 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 Batang Berjuntai; 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.