Time difference between Tokyo and Pangkalan Brandan
Pangkalan Brandan is 2 hours behind Tokyo.
Local time in both cities
Tokyo · Japan
04:23
JapanPangkalan Brandan · Indonesia
02:23
IndonesiaPangkalan Brandan is 2 hours behind Tokyo.
same day
Time zones
| Tokyo | Asia/Tokyo · UTC+09:00 |
|---|---|
| Pangkalan Brandan | Asia/Jakarta · UTC+07:00 |
Tokyo does not observe daylight saving and stays on UTC+09:00 all year.
Pangkalan Brandan does not observe daylight saving and stays on UTC+07:00 all year.
Hour-by-hour conversion
Calculated for 2026-09-22 local time in Tokyo. The two places start and end daylight saving on different dates, so another day can give a different result.
| Tokyo (source) | Pangkalan Brandan (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 Tokyo
FAQ
- How many hours apart are Tokyo and Pangkalan Brandan 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. Tokyo uses Asia/Tokyo and Pangkalan Brandan uses Asia/Jakarta; 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 Tokyo; the right column is the local time in Pangkalan Brandan 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.