Time difference between Santa Cruz de la Sierra and Denver

Denver is 2 hours behind Santa Cruz de la Sierra.

America/La_Paz America/Denver same day

Local time in both cities

17:02
Monday, 21 September 2026
America/La_Paz · UTC-04:00
Denver · United States
15:02
Monday, 21 September 2026
America/Denver · UTC-06:00

Denver is 2 hours behind Santa Cruz de la Sierra.

same day

Time zones

Santa Cruz de la SierraAmerica/La_Paz · UTC-04:00
DenverAmerica/Denver · UTC-06:00

Santa Cruz de la Sierra does not observe daylight saving and stays on UTC-04: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-21 local time in Santa Cruz de la Sierra. The two places start and end daylight saving on different dates, so another day can give a different result.

Santa Cruz de la Sierra (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 Santa Cruz de la Sierra 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. Santa Cruz de la Sierra uses America/La_Paz 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 Santa Cruz de la Sierra; 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