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