Time difference between Cacoal and Hong Kong
Hong Kong is 12 hours ahead of Cacoal.
Local time in both cities
Brazil
ChinaHong Kong is 12 hours ahead of Cacoal.
same day
Time zones
| Cacoal | America/Porto_Velho · UTC-04:00 |
|---|---|
| Hong Kong | Asia/Hong_Kong · UTC+08:00 |
Cacoal does not observe daylight saving and stays on UTC-04:00 all year.
Hong Kong does not observe daylight saving and stays on UTC+08:00 all year.
Hour-by-hour conversion
Calculated for 2026-09-21 local time in Cacoal. The two places start and end daylight saving on different dates, so another day can give a different result.
| Cacoal (source) | Hong Kong (target) |
|---|---|
| 00:00 | 12:00 |
| 01:00 | 13:00 |
| 02:00 | 14:00 |
| 03:00 | 15:00 |
| 04:00 | 16:00 |
| 05:00 | 17:00 |
| 06:00 | 18:00 |
| 07:00 | 19:00 |
| 08:00 | 20:00 |
| 09:00 | 21:00 |
| 10:00 | 22:00 |
| 11:00 | 23:00 |
| 12:00 | 00:00 next day |
| 13:00 | 01:00 next day |
| 14:00 | 02:00 next day |
| 15:00 | 03:00 next day |
| 16:00 | 04:00 next day |
| 17:00 | 05:00 next day |
| 18:00 | 06:00 next day |
| 19:00 | 07:00 next day |
| 20:00 | 08:00 next day |
| 21:00 | 09:00 next day |
| 22:00 | 10:00 next day |
| 23:00 | 11:00 next day |
Other common differences from Cacoal
FAQ
- How many hours apart are Cacoal and Hong Kong 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. Cacoal uses America/Porto_Velho and Hong Kong uses Asia/Hong_Kong; 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 Cacoal; the right column is the local time in Hong Kong 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.