Explore · time zones
Kabul to MST converter
Afghanistan Time (Kabul) → Mountain Time (Denver)
Quick answer
The difference changes with daylight saving time. Denver is 11 hours 30 minutes behind Kabul from Jan 1, 2026 to Mar 8, 2026 09:00 UTC (Denver on MST · UTC−7); 10 hours 30 minutes behind Kabul from Mar 8, 2026 09:00 UTC to Nov 1, 2026 08:00 UTC (Denver on MDT · UTC−6); 11 hours 30 minutes behind Kabul from Nov 1, 2026 08:00 UTC to Dec 31, 2026 (Denver on MST · UTC−7).
- Jan 1, 2026 to Mar 8, 2026 09:00 UTCKabul (UTC+4:30) → Denver (MST, UTC−7)Denver is 11 hours 30 minutes behind Kabul
- Mar 8, 2026 09:00 UTC to Nov 1, 2026 08:00 UTCKabul (UTC+4:30) → Denver (MDT, UTC−6)Denver is 10 hours 30 minutes behind Kabul
- Nov 1, 2026 08:00 UTC to Dec 31, 2026Kabul (UTC+4:30) → Denver (MST, UTC−7)Denver is 11 hours 30 minutes behind Kabul
9:00 AM UTC+4:30 in Kabul is 9:30 PM MST (UTC−7) in Denver, the previous day. Denver is 11 h 30 min behind Kabul.
| Format | Result | Copy |
|---|---|---|
| DenverMST · UTC−7 · Tuesday, January 13, 2026 · the previous day | 9: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768365000 | |
| RFC 2822UTC | Wed, |
Conversions use Kabul (Asia/Kabul) and Denver (America/Denver). Other cities reached through search aliases may have different historical rules.
Current time in Kabul and Denver
Hour by hour: Kabul (UTC+4:30) → Denver (MST, UTC−7)
There is no time when both Kabul and Denver are inside 9:00–17:00.
| Kabul | Denver | Day |
|---|---|---|
| 12:00 AM | 12:30 PM | previous day |
| 1:00 AM | 1:30 PM | previous day |
| 2:00 AM | 2:30 PM | previous day |
| 3:00 AM | 3:30 PM | previous day |
| 4:00 AM | 4:30 PM | previous day |
| 5:00 AM | 5:30 PM | previous day |
| 6:00 AM | 6:30 PM | previous day |
| 7:00 AM | 7:30 PM | previous day |
| 8:00 AM | 8:30 PM | previous day |
| 9:00 AM | 9:30 PM | previous day |
| 10:00 AM | 10:30 PM | previous day |
| 11:00 AM | 11:30 PM | previous day |
| 12:00 PM | 12:30 AM | same day |
| 1:00 PM | 1:30 AM | same day |
| 2:00 PM | 2:30 AM | same day |
| 3:00 PM | 3:30 AM | same day |
| 4:00 PM | 4:30 AM | same day |
| 5:00 PM | 5:30 AM | same day |
| 6:00 PM | 6:30 AM | same day |
| 7:00 PM | 7:30 AM | same day |
| 8:00 PM | 8:30 AM | same day |
| 9:00 PM | 9:30 AM | same day |
| 10:00 PM | 10:30 AM | same day |
| 11:00 PM | 11:30 AM | same day |
Hour by hour: Kabul (UTC+4:30) → Denver (MDT, UTC−6)
There is no time when both Kabul and Denver are inside 9:00–17:00.
| Kabul | Denver | Day |
|---|---|---|
| 12:00 AM | 1:30 PM | previous day |
| 1:00 AM | 2:30 PM | previous day |
| 2:00 AM | 3:30 PM | previous day |
| 3:00 AM | 4:30 PM | previous day |
| 4:00 AM | 5:30 PM | previous day |
| 5:00 AM | 6:30 PM | previous day |
| 6:00 AM | 7:30 PM | previous day |
| 7:00 AM | 8:30 PM | previous day |
| 8:00 AM | 9:30 PM | previous day |
| 9:00 AM | 10:30 PM | previous day |
| 10:00 AM | 11:30 PM | previous day |
| 11:00 AM | 12:30 AM | same day |
| 12:00 PM | 1:30 AM | same day |
| 1:00 PM | 2:30 AM | same day |
| 2:00 PM | 3:30 AM | same day |
| 3:00 PM | 4:30 AM | same day |
| 4:00 PM | 5:30 AM | same day |
| 5:00 PM | 6:30 AM | same day |
| 6:00 PM | 7:30 AM | same day |
| 7:00 PM | 8:30 AM | same day |
| 8:00 PM | 9:30 AM | same day |
| 9:00 PM | 10:30 AM | same day |
| 10:00 PM | 11:30 AM | same day |
| 11:00 PM | 12:30 PM | same day |
Worked examples
| When | Kabul | Denver | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 6:30 PM UTC+4:30, January 14, 2026 | 7:00 AM MST (UTC−7), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 6:30 PM UTC+4:30, July 15, 2026 | 8:00 AM MDT (UTC−6), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 4:30 AM UTC+4:30, January 1, 2027 | 5:00 PM MST (UTC−7), 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.
Kabul — Afghanistan Time
- IANA identifier
- Asia/Kabul
- UTC offset
- UTC+4:30
- Daylight saving
- Not observed
- On this clock today
- Kabul, Afghanistan
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Asia/Kabul; a listed place's past or future rules may differ.
UTC+4:30 all year.
MST — Mountain Time
- IANA identifier
- America/Denver
- Standard time
- MST · UTC−7
- Daylight time
- MDT · UTC−6
- On this clock today
- Denver, Salt Lake City
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Denver; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 8, 2026, 3:00 AM local (2026-03-08 09:00 UTC): clocks go forward to UTC−6 (MDT)
- Nov 1, 2026, 1:00 AM local (2026-11-01 08:00 UTC): clocks go back to UTC−7 (MST)
- Mar 14, 2027, 3:00 AM local (2027-03-14 09:00 UTC): clocks go forward to UTC−6 (MDT)
- Nov 7, 2027, 1:00 AM local (2027-11-07 08:00 UTC): clocks go back to UTC−7 (MST)
Most of Arizona stays on MST all year without daylight saving; see the Arizona page. Alberta (Calgary, Edmonton) stays on UTC−6 all year from November 2026 and is not on this clock; see the Mexico City page.
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.