Time difference between Hong Kong and Johor Bahru
Johor Bahru and Hong Kong are on the same clock.
Local time in both cities
Hong Kong · China
09:04
ChinaJohor Bahru · Malaysia
09:04
MalaysiaJohor Bahru and Hong Kong are on the same clock.
same day
Time zones
| Hong Kong | Asia/Hong_Kong · UTC+08:00 |
|---|---|
| Johor Bahru | Asia/Kuala_Lumpur · UTC+08:00 |
Hong Kong does not observe daylight saving and stays on UTC+08:00 all year.
Johor Bahru does not observe daylight saving and stays on UTC+08:00 all year.
Hour-by-hour conversion
Calculated for 2026-09-22 local time in Hong Kong. The two places start and end daylight saving on different dates, so another day can give a different result.
| Hong Kong (source) | Johor Bahru (target) |
|---|---|
| 00:00 | 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 |
Other common differences from Hong Kong
FAQ
- How many hours apart are Hong Kong and Johor Bahru 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. Hong Kong uses Asia/Hong_Kong and Johor Bahru uses Asia/Kuala_Lumpur; 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 Hong Kong; the right column is the local time in Johor Bahru 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.