Coordinated Universal Time
UTC means UTC throughout the year.
Convert Central Time to Coordinated Universal Time. Compare dates, seasonal differences and meeting hours.
CT is 5h or 6h behind UTC in 2026, depending on the date.
9 AM CT = 3 PM UTC
Selected date: November 10, 2026. Fixed abbreviations retain their stated UTC offsets.
November 10, 2026 · Date changes are marked.
| CT | UTC |
|---|---|
| 12:00 AM | 6:00 AM |
| 1:00 AM | 7:00 AM |
| 2:00 AM | 8:00 AM |
| 3:00 AM | 9:00 AM |
| 4:00 AM | 10:00 AM |
| 5:00 AM | 11:00 AM |
| 6:00 AM | 12:00 PM |
| 7:00 AM | 1:00 PM |
| 8:00 AM | 2:00 PM |
| 9:00 AM | 3:00 PM |
| 10:00 AM | 4:00 PM |
| 11:00 AM | 5:00 PM |
| CT | UTC |
|---|---|
| 12:00 PM | 6:00 PM |
| 1:00 PM | 7:00 PM |
| 2:00 PM | 8:00 PM |
| 3:00 PM | 9:00 PM |
| 4:00 PM | 10:00 PM |
| 5:00 PM | 11:00 PM |
| 6:00 PM | 12:00 AM +1 day |
| 7:00 PM | 1:00 AM +1 day |
| 8:00 PM | 2:00 AM +1 day |
| 9:00 PM | 3:00 AM +1 day |
| 10:00 PM | 4:00 AM +1 day |
| 11:00 PM | 5:00 AM +1 day |
These examples start on 2026-11-10 in UTC.
UTC means UTC throughout the year.
CT follows America/Chicago. On your selected date it uses UTC−06:00 (CST). Its offset can change when the regional clock rules change.
Fixed alternatives: CST (UTC−06:00) · CDT (UTC−05:00). These labels keep their stated UTC offset throughout the year.
Keeping 09:00 on the CT clock produces 2 different destination clock/date answers in 2026. The ranges below use CT calendar dates, including transition days.
| Dates in CT · 2026 | UTC answer | Source → destination offsets | Explore |
|---|---|---|---|
| Jan 1 – Mar 766 dates | 15:00Same date | UTC−06:00 → UTC | |
| Mar 8 – Oct 31238 dates | 14:00Same date | UTC−05:00 → UTC | |
| Nov 1 – Dec 3161 dates | 15:00Same date | UTC−06:00 → UTC |
Every calendar date is included, not just workdays. Date ranges include both endpoints. Based on IANA 2026e; future rules may change.
Your complete source day: 2026-11-10. Each range shows which destination date to use.
Range starts are included; ends are excluded. 24:00 means midnight at the end of that date. Repeated hours appear separately with their UTC offsets. The strip is proportional to elapsed time.
How UTC compares with CT throughout 2026.
CT changes its UTC offset in 2026. UTC is a fixed offset.
| From (UTC, inclusive) | Until (UTC, exclusive) | UTC vs CT |
|---|---|---|
| 1 Jan 2026, 00:00 UTC | 8 Mar 2026, 08:00 UTC | 6h ahead |
| 8 Mar 2026, 08:00 UTC | 1 Nov 2026, 07:00 UTC | 5h ahead |
| 1 Nov 2026, 07:00 UTC | 1 Jan 2027, 00:00 UTC | 6h ahead |
The most frequent difference has UTC 5h ahead relative to CT. Exceptions:
| From (UTC, inclusive) | Until (UTC, exclusive) | Compared with CT |
|---|---|---|
| 1 Jan 2026, 00:00 UTC | 8 Mar 2026, 08:00 UTC | 6h ahead |
| 1 Nov 2026, 07:00 UTC | 1 Jan 2027, 00:00 UTC | 6h ahead |
Every date calculated with your working windows. 261 selected CT workdays; public holidays are not applied.
Start a 60-minute meeting in CT 09:00–10:00.
These starts fit both working windows on every selected CT workday in 2026, using a 15-minute start grid. The end of each range is the last valid start.
CT: 09:00–17:00, Mon, Tue, Wed, Thu, Fri. UTC: 09:00–17:00, Mon, Tue, Wed, Thu, Fri.
Overnight shifts belong to their start weekday. Host workday means the source calendar date. Repeated local times use the first occurrence.
CT is 5h or 6h behind UTC in 2026, depending on the date. CT changes its UTC offset in 2026. UTC is a fixed offset.
The published rules produce 3 periods with 2 different offsets in 2026. See the annual chart for the exact boundaries of each period.
09:00 in CT on 2026-11-10 is 15:00 in UTC on 2026-11-10. This selected time stays on the same date in both places. Other times can cross midnight.
Your selected working windows share 2h on 2026-11-10. The planner above checks the whole meeting duration and shows suitable start times. Edit the windows to match your team.