Explore · time zones
CST to Kathmandu converter
Central Time (Chicago) → Nepal Time (Kathmandu)
Quick answer
The difference changes with daylight saving time. Kathmandu is 11 hours 45 minutes ahead of Chicago from Jan 1, 2026 to Mar 8, 2026 08:00 UTC (Chicago on CST · UTC−6); 10 hours 45 minutes ahead of Chicago from Mar 8, 2026 08:00 UTC to Nov 1, 2026 07:00 UTC (Chicago on CDT · UTC−5); 11 hours 45 minutes ahead of Chicago 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 UTCChicago (CST, UTC−6) → Kathmandu (UTC+5:45)Kathmandu is 11 hours 45 minutes ahead of Chicago
- Mar 8, 2026 08:00 UTC to Nov 1, 2026 07:00 UTCChicago (CDT, UTC−5) → Kathmandu (UTC+5:45)Kathmandu is 10 hours 45 minutes ahead of Chicago
- Nov 1, 2026 07:00 UTC to Dec 31, 2026Chicago (CST, UTC−6) → Kathmandu (UTC+5:45)Kathmandu is 11 hours 45 minutes ahead of Chicago
9:00 AM CST (UTC−6) in Chicago is 8:45 PM UTC+5:45 in Kathmandu, the same day. Kathmandu is 11 h 45 min ahead of Chicago.
| Format | Result | Copy |
|---|---|---|
| KathmanduWednesday, January 14, 2026 · the same day | 8: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768402800 | |
| RFC 2822UTC | Wed, |
Conversions use Chicago (America/Chicago) and Kathmandu (Asia/Kathmandu). Other cities reached through search aliases may have different historical rules.
Current time in Chicago and Kathmandu
Hour by hour: Chicago (CST, UTC−6) → Kathmandu (UTC+5:45)
There is no time when both Chicago and Kathmandu are inside 9:00–17:00.
| Chicago | Kathmandu | Day |
|---|---|---|
| 12:00 AM | 11:45 AM | same day |
| 1:00 AM | 12:45 PM | same day |
| 2:00 AM | 1:45 PM | same day |
| 3:00 AM | 2:45 PM | same day |
| 4:00 AM | 3:45 PM | same day |
| 5:00 AM | 4:45 PM | same day |
| 6:00 AM | 5:45 PM | same day |
| 7:00 AM | 6:45 PM | same day |
| 8:00 AM | 7:45 PM | same day |
| 9:00 AM | 8:45 PM | same day |
| 10:00 AM | 9:45 PM | same day |
| 11:00 AM | 10:45 PM | same day |
| 12:00 PM | 11:45 PM | same day |
| 1:00 PM | 12:45 AM | next day |
| 2:00 PM | 1:45 AM | next day |
| 3:00 PM | 2:45 AM | next day |
| 4:00 PM | 3:45 AM | next day |
| 5:00 PM | 4:45 AM | next day |
| 6:00 PM | 5:45 AM | next day |
| 7:00 PM | 6:45 AM | next day |
| 8:00 PM | 7:45 AM | next day |
| 9:00 PM | 8:45 AM | next day |
| 10:00 PM | 9:45 AM | next day |
| 11:00 PM | 10:45 AM | next day |
Hour by hour: Chicago (CDT, UTC−5) → Kathmandu (UTC+5:45)
There is no time when both Chicago and Kathmandu are inside 9:00–17:00.
| Chicago | Kathmandu | Day |
|---|---|---|
| 12:00 AM | 10:45 AM | same day |
| 1:00 AM | 11:45 AM | same day |
| 2:00 AM | 12:45 PM | same day |
| 3:00 AM | 1:45 PM | same day |
| 4:00 AM | 2:45 PM | same day |
| 5:00 AM | 3:45 PM | same day |
| 6:00 AM | 4:45 PM | same day |
| 7:00 AM | 5:45 PM | same day |
| 8:00 AM | 6:45 PM | same day |
| 9:00 AM | 7:45 PM | same day |
| 10:00 AM | 8:45 PM | same day |
| 11:00 AM | 9:45 PM | same day |
| 12:00 PM | 10:45 PM | same day |
| 1:00 PM | 11:45 PM | same day |
| 2:00 PM | 12:45 AM | next day |
| 3:00 PM | 1:45 AM | next day |
| 4:00 PM | 2:45 AM | next day |
| 5:00 PM | 3:45 AM | next day |
| 6:00 PM | 4:45 AM | next day |
| 7:00 PM | 5:45 AM | next day |
| 8:00 PM | 6:45 AM | next day |
| 9:00 PM | 7:45 AM | next day |
| 10:00 PM | 8:45 AM | next day |
| 11:00 PM | 9:45 AM | next day |
Worked examples
| When | Chicago | Kathmandu | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 8:00 AM CST (UTC−6), January 14, 2026 | 7:45 PM UTC+5:45, January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 9:00 AM CDT (UTC−5), July 15, 2026 | 7:45 PM UTC+5:45, July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 6:00 PM CST (UTC−6), December 31, 2026 | 5:45 AM UTC+5:45, January 1, 2027 | 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.
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.
Kathmandu — Nepal Time
- IANA identifier
- Asia/Kathmandu
- UTC offset
- UTC+5:45
- Daylight saving
- Not observed
- On this clock today
- Kathmandu, Nepal
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Asia/Kathmandu; a listed place's past or future rules may differ.
One of the few UTC+5:45 offsets in the world.
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.