Time difference between Chicago and Mueang Nonthaburi

Mueang Nonthaburi is 12 hours ahead of Chicago.

America/Chicago Asia/Bangkok same day

Local time in both cities

Chicago · United States
07:18
Monday, 21 September 2026
America/Chicago · UTC-05:00
Mueang Nonthaburi · Thailand
19:18
Monday, 21 September 2026
Asia/Bangkok · UTC+07:00

Mueang Nonthaburi is 12 hours ahead of Chicago.

same day

Time zones

ChicagoAmerica/Chicago · UTC-05:00
Mueang NonthaburiAsia/Bangkok · UTC+07:00

Chicago is currently on daylight saving time (UTC-05:00). Next change: 2026-11-01 01:00.

Mueang Nonthaburi does not observe daylight saving and stays on UTC+07:00 all year.

Hour-by-hour conversion

Calculated for 2026-09-21 local time in Chicago. The two places start and end daylight saving on different dates, so another day can give a different result.

Chicago (source) Mueang Nonthaburi (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

FAQ

How many hours apart are Chicago and Mueang Nonthaburi 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. Chicago uses America/Chicago and Mueang Nonthaburi uses Asia/Bangkok; 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 Chicago; the right column is the local time in Mueang Nonthaburi 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