Time difference between San Juan Sacatepéquez and Chicago

Chicago is 1 hours ahead of San Juan Sacatepéquez.

America/Guatemala America/Chicago same day

Local time in both cities

11:10
Monday, 21 September 2026
America/Guatemala · UTC-06:00
Chicago · United States
12:10
Monday, 21 September 2026
America/Chicago · UTC-05:00

Chicago is 1 hours ahead of San Juan Sacatepéquez.

same day

Time zones

San Juan SacatepéquezAmerica/Guatemala · UTC-06:00
ChicagoAmerica/Chicago · UTC-05:00

San Juan Sacatepéquez does not observe daylight saving and stays on UTC-06: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 San Juan Sacatepéquez. The two places start and end daylight saving on different dates, so another day can give a different result.

San Juan Sacatepéquez (source) Chicago (target)
00:00 01:00
01:00 02:00
02:00 03:00
03:00 04:00
04:00 05:00
05:00 06:00
06:00 07:00
07:00 08:00
08:00 09:00
09:00 10:00
10:00 11:00
11:00 12:00
12:00 13:00
13:00 14:00
14:00 15:00
15:00 16:00
16:00 17:00
17:00 18:00
18:00 19:00
19:00 20:00
20:00 21:00
21:00 22:00
22:00 23:00
23:00 00:00 next day

FAQ

How many hours apart are San Juan Sacatepéquez 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. San Juan Sacatepéquez uses America/Guatemala 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 San Juan Sacatepéquez; 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