Colombia Time Zone Basics
Colombia runs on Colombia Time (COT), which is UTC-5 year-round. No daylight saving time. No exceptions. The whole country sticks to the same offset regardless of region or season. That's simpler than most Latin American countries because places like Chile and Argentina flip between offsets while Colombia just sits at minus five and doesn't bother. The main confusion people run into is assuming Colombia shifts like its neighbors. It doesn't. When the US moves to Eastern Daylight Time (EDT, UTC-4), Colombia stays at UTC-5. That means during the US summer months, there's only a one-hour difference between Bogotá and New York instead of the usual two. I've missed at least three meetings because I assumed the gap stayed at two hours when it actually shrank to one. Bogotá, Medellín, Cali, Cartagena — they're all the same time. There's no regional variation the way you get in Brazil or the US. Colombia covers roughly 30 degrees of longitude, which would normally justify two time zones, but the government decided decades ago that keeping everyone on one clock was less annoying. It mostly works, except when you're scheduling something with someone in Leticia in the far south who technically should be on a different solar time but isn't allowed to be.
If you need to convert Colombia time to your local zone, just remember UTC-5 and that it never changes. Subtract five hours from UTC to get Colombia time, or add five hours to Colombia time to get UTC. That's it. The only real edge case is the US daylight saving overlap I mentioned. When I was coordinating a project between a team in Bogotá and clients in São Paulo, I learned the hard way that Brazil has multiple time zones and also observes DST, so the offset between Colombia and Brazil shifted depending on the time of year. I ended up maintaining a shared spreadsheet that listed the current offset for both sides so nobody would accidentally schedule a call at 3 AM Bogota time thinking it was noon. It cut our scheduling mistakes from about four per month down to maybe one per quarter. The real problem with Colombia time isn't the conversion. It's the assumption that everything in South America behaves the same way. They don't. Chile, Peru, Ecuador, and Bolivia each have their own quirks. Peru is also UTC-5 with no DST, so it matches Colombia exactly. Ecuador is also UTC-5, though they call it Ecuador Time. Chile flips between UTC-3 and UTC-4. Venezuela used to be UTC-4:30 before Chávez changed it to UTC-4 in 2007. If you're building software that handles multiple Latin American cities, hardcoding "South America equals one offset" will bite you.
For developers, the IANA timezone identifier for Colombia is America/Bogota. That's what you put in your database, your server config, and your code. Don't use America/Guayaquil or America/Lima even though they happen to share the same offset right now. Colombia's timezone database entry has stayed consistent since the DST abolition in 1993, so you won't hit sudden historical shifts. But using the wrong identifier means your code breaks if those other countries ever decide to change their rules and your app assumes they move in sync. If you're doing anything time-sensitive with Colombian partners, I'd recommend setting your calendar to show both your local time and Bogotá time simultaneously. I keep a secondary clock widget running on my phone labeled "Bogotá" and check it before confirming any meeting slot. It took me about two weeks to build the habit but it's saved me from more scheduling disasters than I care to count. One more thing worth knowing: Colombian business hours typically run 9 AM to 6 PM local time, with a lunch break that can push things later. If you're calling from the US Eastern time zone during summer, that's a 1 PM to 12 AM window for you, which means the overlap is tight. Morning calls in your time are afternoon calls for them. Afternoon calls in your time are evening calls for them and they're probably done by then. This is the same pattern most companies face across the Americas and there's no workaround except finding the narrow morning slot and protecting it.
Get the Full Details
