Time difference between Santiago Ixcuintla and Chicago

Chicago is 2 hours ahead of Santiago Ixcuintla.

America/Mazatlan America/Chicago already the next day

Local time in both cities

23:17
Sunday, 20 September 2026
America/Mazatlan · UTC-07:00
Chicago · United States
01:17
Monday, 21 September 2026
America/Chicago · UTC-05:00

Chicago is 2 hours ahead of Santiago Ixcuintla.

already the next day

Time zones

Santiago IxcuintlaAmerica/Mazatlan · UTC-07:00
ChicagoAmerica/Chicago · UTC-05:00

Santiago Ixcuintla does not observe daylight saving and stays on UTC-07: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-20 local time in Santiago Ixcuintla. The two places start and end daylight saving on different dates, so another day can give a different result.

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

FAQ

How many hours apart are Santiago Ixcuintla 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. Santiago Ixcuintla uses America/Mazatlan 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 Santiago Ixcuintla; 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