Explore · time zones
Jakarta to AKST converter
Western Indonesia Time (Jakarta) → Alaska Time (Anchorage)
Quick answer
The difference changes with daylight saving time. Anchorage is 16 hours behind Jakarta from Jan 1, 2026 to Mar 8, 2026 11:00 UTC (Anchorage on AKST · UTC−9); 15 hours behind Jakarta from Mar 8, 2026 11:00 UTC to Nov 1, 2026 10:00 UTC (Anchorage on AKDT · UTC−8); 16 hours behind Jakarta from Nov 1, 2026 10:00 UTC to Dec 31, 2026 (Anchorage on AKST · UTC−9).
- Jan 1, 2026 to Mar 8, 2026 11:00 UTCJakarta (WIB, UTC+7) → Anchorage (AKST, UTC−9)Anchorage is 16 hours behind Jakarta
- Mar 8, 2026 11:00 UTC to Nov 1, 2026 10:00 UTCJakarta (WIB, UTC+7) → Anchorage (AKDT, UTC−8)Anchorage is 15 hours behind Jakarta
- Nov 1, 2026 10:00 UTC to Dec 31, 2026Jakarta (WIB, UTC+7) → Anchorage (AKST, UTC−9)Anchorage is 16 hours behind Jakarta
9:00 AM WIB (UTC+7) in Jakarta is 5:00 PM AKST (UTC−9) in Anchorage, the previous day. Anchorage is 16 h behind Jakarta.
| Format | Result | Copy |
|---|---|---|
| AnchorageAKST · UTC−9 · Tuesday, January 13, 2026 · the previous day | 5: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768356000 | |
| RFC 2822UTC | Wed, |
Conversions use Jakarta (Asia/Jakarta) and Anchorage (America/Anchorage). Other cities reached through search aliases may have different historical rules.
Current time in Jakarta and Anchorage
Hour by hour: Jakarta (WIB, UTC+7) → Anchorage (AKST, UTC−9)
There is no time when both Jakarta and Anchorage are inside 9:00–17:00.
| Jakarta | Anchorage | Day |
|---|---|---|
| 12:00 AM | 8:00 AM | previous day |
| 1:00 AM | 9:00 AM | previous day |
| 2:00 AM | 10:00 AM | previous day |
| 3:00 AM | 11:00 AM | previous day |
| 4:00 AM | 12:00 PM | previous day |
| 5:00 AM | 1:00 PM | previous day |
| 6:00 AM | 2:00 PM | previous day |
| 7:00 AM | 3:00 PM | previous day |
| 8:00 AM | 4:00 PM | previous day |
| 9:00 AM | 5:00 PM | previous day |
| 10:00 AM | 6:00 PM | previous day |
| 11:00 AM | 7:00 PM | previous day |
| 12:00 PM | 8:00 PM | previous day |
| 1:00 PM | 9:00 PM | previous day |
| 2:00 PM | 10:00 PM | previous day |
| 3:00 PM | 11:00 PM | previous day |
| 4:00 PM | 12:00 AM | same day |
| 5:00 PM | 1:00 AM | same day |
| 6:00 PM | 2:00 AM | same day |
| 7:00 PM | 3:00 AM | same day |
| 8:00 PM | 4:00 AM | same day |
| 9:00 PM | 5:00 AM | same day |
| 10:00 PM | 6:00 AM | same day |
| 11:00 PM | 7:00 AM | same day |
Hour by hour: Jakarta (WIB, UTC+7) → Anchorage (AKDT, UTC−8)
There is no time when both Jakarta and Anchorage are inside 9:00–17:00.
| Jakarta | Anchorage | Day |
|---|---|---|
| 12:00 AM | 9:00 AM | previous day |
| 1:00 AM | 10:00 AM | previous day |
| 2:00 AM | 11:00 AM | previous day |
| 3:00 AM | 12:00 PM | previous day |
| 4:00 AM | 1:00 PM | previous day |
| 5:00 AM | 2:00 PM | previous day |
| 6:00 AM | 3:00 PM | previous day |
| 7:00 AM | 4:00 PM | previous day |
| 8:00 AM | 5:00 PM | previous day |
| 9:00 AM | 6:00 PM | previous day |
| 10:00 AM | 7:00 PM | previous day |
| 11:00 AM | 8:00 PM | previous day |
| 12:00 PM | 9:00 PM | previous day |
| 1:00 PM | 10:00 PM | previous day |
| 2:00 PM | 11:00 PM | previous day |
| 3:00 PM | 12:00 AM | same day |
| 4:00 PM | 1:00 AM | same day |
| 5:00 PM | 2:00 AM | same day |
| 6:00 PM | 3:00 AM | same day |
| 7:00 PM | 4:00 AM | same day |
| 8:00 PM | 5:00 AM | same day |
| 9:00 PM | 6:00 AM | same day |
| 10:00 PM | 7:00 AM | same day |
| 11:00 PM | 8:00 AM | same day |
Worked examples
| When | Jakarta | Anchorage | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 9:00 PM WIB (UTC+7), January 14, 2026 | 5:00 AM AKST (UTC−9), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 9:00 PM WIB (UTC+7), July 15, 2026 | 6:00 AM AKDT (UTC−8), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 7:00 AM WIB (UTC+7), January 1, 2027 | 3:00 PM AKST (UTC−9), 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.
Jakarta — Western Indonesia Time
- IANA identifier
- Asia/Jakarta
- UTC offset
- WIB · UTC+7
- Daylight saving
- Not observed
- On this clock today
- Jakarta, Surabaya, Bandung, Medan
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Asia/Jakarta; a listed place's past or future rules may differ.
Indonesia spans three zones: WIB (UTC+7, Jakarta), WITA (UTC+8, Makassar/Bali) and WIT (UTC+9, Jayapura).
AKST — Alaska Time
- IANA identifier
- America/Anchorage
- Standard time
- AKST · UTC−9
- Daylight time
- AKDT · UTC−8
- On this clock today
- Anchorage, Juneau, Fairbanks
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Anchorage; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 8, 2026, 3:00 AM local (2026-03-08 11:00 UTC): clocks go forward to UTC−8 (AKDT)
- Nov 1, 2026, 1:00 AM local (2026-11-01 10:00 UTC): clocks go back to UTC−9 (AKST)
- Mar 14, 2027, 3:00 AM local (2027-03-14 11:00 UTC): clocks go forward to UTC−8 (AKDT)
- Nov 7, 2027, 1:00 AM local (2027-11-07 10:00 UTC): clocks go back to UTC−9 (AKST)
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.