Time difference between Puerto Eldorado and Denver

Denver is 3 hours behind Puerto Eldorado.

America/Argentina/Cordoba America/Denver same day

Local time in both cities

Puerto Eldorado · Argentina
20:32
Sunday, 20 September 2026
America/Argentina/Cordoba · UTC-03:00
Denver · United States
17:32
Sunday, 20 September 2026
America/Denver · UTC-06:00

Denver is 3 hours behind Puerto Eldorado.

same day

Time zones

Puerto EldoradoAmerica/Argentina/Cordoba · UTC-03:00
DenverAmerica/Denver · UTC-06:00

Puerto Eldorado does not observe daylight saving and stays on UTC-03:00 all year.

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-20 local time in Puerto Eldorado. The two places start and end daylight saving on different dates, so another day can give a different result.

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

FAQ

How many hours apart are Puerto Eldorado 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. Puerto Eldorado uses America/Argentina/Cordoba 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 Puerto Eldorado; 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