Time difference between San Miguel del Padrón and Denver

Denver is 2 hours behind San Miguel del Padrón.

America/Havana America/Denver same day

Local time in both cities

11:49
Monday, 21 September 2026
America/Havana · UTC-04:00
Denver · United States
09:49
Monday, 21 September 2026
America/Denver · UTC-06:00

Denver is 2 hours behind San Miguel del Padrón.

same day

Time zones

San Miguel del PadrónAmerica/Havana · UTC-04:00
DenverAmerica/Denver · UTC-06:00

San Miguel del Padrón is currently on daylight saving time (UTC-04:00). Next change: 2026-11-01 00:00.

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

Hour-by-hour conversion

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

San Miguel del Padrón (source) Denver (target)
00:00 22:00 prev day
01:00 23:00 prev day
02:00 00:00
03:00 01:00
04:00 02:00
05:00 03:00
06:00 04:00
07:00 05:00
08:00 06:00
09:00 07:00
10:00 08:00
11:00 09:00
12:00 10:00
13:00 11:00
14:00 12:00
15:00 13:00
16:00 14:00
17:00 15:00
18:00 16:00
19:00 17:00
20:00 18:00
21:00 19:00
22:00 20:00
23:00 21:00

FAQ

How many hours apart are San Miguel del Padrón and Denver 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 Miguel del Padrón uses America/Havana and Denver uses America/Denver; 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 Miguel del Padrón; the right column is the local time in Denver 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