Tukuk-OS🕒 Chicago to Adelaide time
| Chicago on 2026-11-06 | 12:00 (GMT−6) |
| Adelaide at that instant | 04:30 the next day (GMT+10:30) |
| Difference on this date | 16 h 30 min (2026-11-01 to 2026-12-31) |
| 2026-01-01 to 2026-03-07 | 16 h 30 min |
| 2026-03-08 to 2026-04-04 | 15 h 30 min |
| 2026-04-05 to 2026-10-03 | 14 h 30 min |
| 2026-10-04 to 2026-10-31 | 15 h 30 min |
| 2026-11-01 to 2026-12-31 | 16 h 30 min |
| Next clock change, Chicago | Sunday 14 March 2027 at 08:00 UTC |
| Next clock change, Adelaide | Saturday 3 April 2027 at 16:30 UTC |
| 09:00 in Chicago is | 01:30 in Adelaide |
| 12:00 in Chicago is | 04:30 in Adelaide |
| 18:00 in Chicago is | 10:30 in Adelaide |
| Shared 09:00–17:00 working window | none — there is no hour that is inside 09:00–17:00 in both |
ℹ️ What this tool does & how it works
On 2026-11-06 the two clocks are apart by 16 h 30 min, with Adelaide ahead. Chicago runs on GMT−6 and Adelaide on GMT+10:30. Across 2026 the difference runs: 2026-01-01 → 2026-03-07: 16 h 30 min; 2026-03-08 → 2026-04-04: 15 h 30 min; 2026-04-05 → 2026-10-03: 14 h 30 min; 2026-10-04 → 2026-10-31: 15 h 30 min; 2026-11-01 → 2026-12-31: 16 h 30 min. Pick any date and time below and the page reworks the whole table from your own device.
Why the gap between Chicago and Adelaide changes during 2026
Two places drift apart and come back again whenever one of them changes its clocks and the other does not — which is the situation between a place that observes daylight saving and one that does not, or between two that pick different Sundays for it. In 2026 the difference between Chicago and Adelaide runs: 2026-01-01 → 2026-03-07: 16 h 30 min; 2026-03-08 → 2026-04-04: 15 h 30 min; 2026-04-05 → 2026-10-03: 14 h 30 min; 2026-10-04 → 2026-10-31: 15 h 30 min; 2026-11-01 → 2026-12-31: 16 h 30 min. A meeting arranged in the middle of one of those runs is safe; one arranged across a boundary is the classic four-hours-late call, so the table names the boundaries instead of leaving you to remember them.
The clock changes, and who decides them
Chicago uses the zone America/Chicago, and its next change after 2026-11-06 is Sunday 14 March 2027 at 08:00 UTC. Adelaide uses the zone Australia/Adelaide, and its next change after 2026-11-06 is Saturday 3 April 2027 at 16:30 UTC. Neither figure is a physical fact: an offset is legislation, and the same fifteen degrees of longitude can sit under three zones because a border runs through it. That is why this page reads its offsets out of the time-zone database built into your own browser instead of hardcoding a table of abbreviations — it is the database your operating system already keeps current, and it is what puts Chicago and Adelaide in the right relation even when a government moves a date at short notice. A device whose database predates the last change gets the old answer, which is the one caveat worth knowing.
What it is actually like to work across the two
There is no hour that falls inside 09:00–17:00 on both sides — none — there is no hour that is inside 09:00–17:00 in both — so any call is somebody’s out-of-hours and the honest thing is to rotate it. The two clock rules here are not unique to these two places: 3 other cities in our dataset keep the same clock as one of them, including New Orleans, Houston, Nashville, so looking any of those up against the city on the other side of the pair gives this page’s answers. The arithmetic is the three lines the page runs in front of you: read each zone’s offset for the date you picked, subtract, and let the modulo handle the dateline.