Time difference between Ban Lam Luk Ka and Denver

Denver is 13 hours behind Ban Lam Luk Ka.

Asia/Bangkok America/Denver still the previous day

Local time in both cities

Ban Lam Luk Ka · Thailand
01:57
Tuesday, 22 September 2026
Asia/Bangkok · UTC+07:00
Denver · United States
12:57
Monday, 21 September 2026
America/Denver · UTC-06:00

Denver is 13 hours behind Ban Lam Luk Ka.

still the previous day

Time zones

Ban Lam Luk KaAsia/Bangkok · UTC+07:00
DenverAmerica/Denver · UTC-06:00

Ban Lam Luk Ka 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-22 local time in Ban Lam Luk Ka. The two places start and end daylight saving on different dates, so another day can give a different result.

Ban Lam Luk Ka (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

FAQ

How many hours apart are Ban Lam Luk Ka 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. Ban Lam Luk Ka uses Asia/Bangkok 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 Ban Lam Luk Ka; 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.

Both cities