Time difference between San José de las Lajas and Chicago

Chicago is 1 hours behind San José de las Lajas.

America/Havana America/Chicago same day

Local time in both cities

06:44
Monday, 21 September 2026
America/Havana · UTC-04:00
Chicago · United States
05:44
Monday, 21 September 2026
America/Chicago · UTC-05:00

Chicago is 1 hours behind San José de las Lajas.

same day

Time zones

San José de las LajasAmerica/Havana · UTC-04:00
ChicagoAmerica/Chicago · UTC-05:00

San José de las Lajas is currently on daylight saving time (UTC-04:00). Next change: 2026-11-01 00:00.

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 José de las Lajas. The two places start and end daylight saving on different dates, so another day can give a different result.

San José de las Lajas (source) Chicago (target)
00:00 23:00 prev day
01:00 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

FAQ

How many hours apart are San José de las Lajas 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 José de las Lajas uses America/Havana 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 José de las Lajas; 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