Time difference between Nadi and Chicago

Chicago is 17 hours behind Nadi.

Pacific/Fiji America/Chicago still the previous day

Local time in both cities

Nadi · Fiji
14:47
Monday, 21 September 2026
Pacific/Fiji · UTC+12:00
Chicago · United States
21:47
Sunday, 20 September 2026
America/Chicago · UTC-05:00

Chicago is 17 hours behind Nadi.

still the previous day

Time zones

NadiPacific/Fiji · UTC+12:00
ChicagoAmerica/Chicago · UTC-05:00

Nadi does not observe daylight saving and stays on UTC+12:00 all year.

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

Hour-by-hour conversion

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

Nadi (source) Chicago (target)
00:00 07:00 prev day
01:00 08:00 prev day
02:00 09:00 prev day
03:00 10:00 prev day
04:00 11:00 prev day
05:00 12:00 prev day
06:00 13:00 prev day
07:00 14:00 prev day
08:00 15:00 prev day
09:00 16:00 prev day
10:00 17:00 prev day
11:00 18:00 prev day
12:00 19:00 prev day
13:00 20:00 prev day
14:00 21:00 prev day
15:00 22:00 prev day
16:00 23:00 prev day
17:00 00:00
18:00 01:00
19:00 02:00
20:00 03:00
21:00 04:00
22:00 05:00
23:00 06:00

FAQ

How many hours apart are Nadi and Chicago 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. Nadi uses Pacific/Fiji and Chicago uses America/Chicago; 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 Nadi; the right column is the local time in Chicago 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