Explore · time zones
Buenos Aires to CST converter
Argentina Time (Buenos Aires) → Central Time (Chicago)
Quick answer
The difference changes with daylight saving time. Chicago is 3 hours behind Buenos Aires from Jan 1, 2026 to Mar 8, 2026 08:00 UTC (Chicago on CST · UTC−6); 2 hours behind Buenos Aires from Mar 8, 2026 08:00 UTC to Nov 1, 2026 07:00 UTC (Chicago on CDT · UTC−5); 3 hours behind Buenos Aires from Nov 1, 2026 07:00 UTC to Dec 31, 2026 (Chicago on CST · UTC−6).
- Jan 1, 2026 to Mar 8, 2026 08:00 UTCBuenos Aires (UTC−3) → Chicago (CST, UTC−6)Chicago is 3 hours behind Buenos Aires
- Mar 8, 2026 08:00 UTC to Nov 1, 2026 07:00 UTCBuenos Aires (UTC−3) → Chicago (CDT, UTC−5)Chicago is 2 hours behind Buenos Aires
- Nov 1, 2026 07:00 UTC to Dec 31, 2026Buenos Aires (UTC−3) → Chicago (CST, UTC−6)Chicago is 3 hours behind Buenos Aires
9:00 AM UTC−3 in Buenos Aires is 6:00 AM CST (UTC−6) in Chicago, the same day. Chicago is 3 h behind Buenos Aires.
| Format | Result | Copy |
|---|---|---|
| ChicagoCST · UTC−6 · Wednesday, January 14, 2026 · the same day | 6: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768392000 | |
| RFC 2822UTC | Wed, |
Conversions use Buenos Aires (America/Argentina/Buenos_Aires) and Chicago (America/Chicago). Other cities reached through search aliases may have different historical rules.
Current time in Buenos Aires and Chicago
Hour by hour: Buenos Aires (UTC−3) → Chicago (CST, UTC−6)
Both sides are inside 9:00–17:00 from 12:00 PM to 5:00 PM UTC−3 in Buenos Aires (5 hours).
| Buenos Aires | Chicago | Day |
|---|---|---|
| 12:00 AM | 9:00 PM | previous day |
| 1:00 AM | 10:00 PM | previous day |
| 2:00 AM | 11:00 PM | previous day |
| 3:00 AM | 12:00 AM | same day |
| 4:00 AM | 1:00 AM | same day |
| 5:00 AM | 2:00 AM | same day |
| 6:00 AM | 3:00 AM | same day |
| 7:00 AM | 4:00 AM | same day |
| 8:00 AM | 5:00 AM | same day |
| 9:00 AM | 6:00 AM | same day |
| 10:00 AM | 7:00 AM | same day |
| 11:00 AM | 8:00 AM | same day |
| 12:00 PM | 9:00 AM | same day |
| 1:00 PM | 10:00 AM | same day |
| 2:00 PM | 11:00 AM | same day |
| 3:00 PM | 12:00 PM | same day |
| 4:00 PM | 1:00 PM | same day |
| 5:00 PM | 2:00 PM | same day |
| 6:00 PM | 3:00 PM | same day |
| 7:00 PM | 4:00 PM | same day |
| 8:00 PM | 5:00 PM | same day |
| 9:00 PM | 6:00 PM | same day |
| 10:00 PM | 7:00 PM | same day |
| 11:00 PM | 8:00 PM | same day |
Hour by hour: Buenos Aires (UTC−3) → Chicago (CDT, UTC−5)
Both sides are inside 9:00–17:00 from 11:00 AM to 5:00 PM UTC−3 in Buenos Aires (6 hours).
| Buenos Aires | Chicago | Day |
|---|---|---|
| 12:00 AM | 10:00 PM | previous day |
| 1:00 AM | 11:00 PM | previous day |
| 2:00 AM | 12:00 AM | same day |
| 3:00 AM | 1:00 AM | same day |
| 4:00 AM | 2:00 AM | same day |
| 5:00 AM | 3:00 AM | same day |
| 6:00 AM | 4:00 AM | same day |
| 7:00 AM | 5:00 AM | same day |
| 8:00 AM | 6:00 AM | same day |
| 9:00 AM | 7:00 AM | same day |
| 10:00 AM | 8:00 AM | same day |
| 11:00 AM | 9:00 AM | same day |
| 12:00 PM | 10:00 AM | same day |
| 1:00 PM | 11:00 AM | same day |
| 2:00 PM | 12:00 PM | same day |
| 3:00 PM | 1:00 PM | same day |
| 4:00 PM | 2:00 PM | same day |
| 5:00 PM | 3:00 PM | same day |
| 6:00 PM | 4:00 PM | same day |
| 7:00 PM | 5:00 PM | same day |
| 8:00 PM | 6:00 PM | same day |
| 9:00 PM | 7:00 PM | same day |
| 10:00 PM | 8:00 PM | same day |
| 11:00 PM | 9:00 PM | same day |
Worked examples
| When | Buenos Aires | Chicago | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 11:00 AM UTC−3, January 14, 2026 | 8:00 AM CST (UTC−6), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 11:00 AM UTC−3, July 15, 2026 | 9:00 AM CDT (UTC−5), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 9:00 PM UTC−3, December 31, 2026 | 6:00 PM CST (UTC−6), December 31, 2026 | 2027-01-01T00:00:00.000Z | 1798761600 |
The ISO 8601 and Unix columns are the same instant written without a zone — how APIs and databases should store it. Need this for a whole column? Convert a CSV file.
Buenos Aires — Argentina Time
- IANA identifier
- America/Argentina/Buenos_Aires
- UTC offset
- UTC−3
- Daylight saving
- Not observed
- On this clock today
- Buenos Aires, Argentina
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Argentina/Buenos_Aires; a listed place's past or future rules may differ.
CST — Central Time
- IANA identifier
- America/Chicago
- Standard time
- CST · UTC−6
- Daylight time
- CDT · UTC−5
- On this clock today
- Chicago, Dallas, Houston, Minneapolis
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Chicago; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 8, 2026, 3:00 AM local (2026-03-08 08:00 UTC): clocks go forward to UTC−5 (CDT)
- Nov 1, 2026, 1:00 AM local (2026-11-01 07:00 UTC): clocks go back to UTC−6 (CST)
- Mar 14, 2027, 3:00 AM local (2027-03-14 08:00 UTC): clocks go forward to UTC−5 (CDT)
- Nov 7, 2027, 1:00 AM local (2027-11-07 07:00 UTC): clocks go back to UTC−6 (CST)
CST here is North American Central Standard Time (UTC−6), with CDT (UTC−5) in summer. China Standard Time (UTC+8) is on the Shanghai page. Manitoba (Winnipeg) stays on UTC−5 all year from 2026 and is not on this clock.
Related conversions
File workspace
Converting a whole column of timestamps?
The free converter handles one value at a time across 82 formats and 92 zones. The file workspace converts an entire CSV column between any two formats and zones, previews the first rows, and leaves unreadable cells exactly as they were.
Offsets and change dates on this page are computed from IANA time zone database 2026f for 2026–2027; the live tool uses the same data.