Time difference between Denver and Porto Seguro
Porto Seguro is 3 hours ahead of Denver.
Local time in both cities
Denver · United States
23:31
Porto Seguro · Brazil
02:31
Porto Seguro is 3 hours ahead of Denver.
already the next day
Time zones
| Denver | America/Denver · UTC-06:00 |
|---|---|
| Porto Seguro | America/Bahia · UTC-03:00 |
Denver is currently on daylight saving time (UTC-06:00). Next change: 2026-11-01 01:00.
Porto Seguro does not observe daylight saving and stays on UTC-03:00 all year.
Hour-by-hour conversion
Calculated for 2026-09-20 local time in Denver. The two places start and end daylight saving on different dates, so another day can give a different result.
| Denver (source) | Porto Seguro (target) |
|---|---|
| 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 | 00:00 next day |
| 22:00 | 01:00 next day |
| 23:00 | 02:00 next day |
Other common differences from Denver
FAQ
- How many hours apart are Denver and Porto Seguro 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. Denver uses America/Denver and Porto Seguro uses America/Bahia; 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 Denver; the right column is the local time in Porto Seguro 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.