Explore · time zones
Kathmandu to Halifax converter
Nepal Time (Kathmandu) → Atlantic Time (Halifax)
Quick answer
The difference changes with daylight saving time. Halifax is 9 hours 45 minutes behind Kathmandu from Jan 1, 2026 to Mar 8, 2026 06:00 UTC (Halifax on AST · UTC−4); 8 hours 45 minutes behind Kathmandu from Mar 8, 2026 06:00 UTC to Nov 1, 2026 05:00 UTC (Halifax on ADT · UTC−3); 9 hours 45 minutes behind Kathmandu from Nov 1, 2026 05:00 UTC to Dec 31, 2026 (Halifax on AST · UTC−4).
- Jan 1, 2026 to Mar 8, 2026 06:00 UTCKathmandu (UTC+5:45) → Halifax (AST, UTC−4)Halifax is 9 hours 45 minutes behind Kathmandu
- Mar 8, 2026 06:00 UTC to Nov 1, 2026 05:00 UTCKathmandu (UTC+5:45) → Halifax (ADT, UTC−3)Halifax is 8 hours 45 minutes behind Kathmandu
- Nov 1, 2026 05:00 UTC to Dec 31, 2026Kathmandu (UTC+5:45) → Halifax (AST, UTC−4)Halifax is 9 hours 45 minutes behind Kathmandu
9:00 AM UTC+5:45 in Kathmandu is 11:15 PM AST (UTC−4) in Halifax, the previous day. Halifax is 9 h 45 min behind Kathmandu.
| Format | Result | Copy |
|---|---|---|
| HalifaxAST · UTC−4 · Tuesday, January 13, 2026 · the previous day | 11: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768360500 | |
| RFC 2822UTC | Wed, |
Conversions use Kathmandu (Asia/Kathmandu) and Halifax (America/Halifax). Other cities reached through search aliases may have different historical rules.
Current time in Kathmandu and Halifax
Hour by hour: Kathmandu (UTC+5:45) → Halifax (AST, UTC−4)
There is no time when both Kathmandu and Halifax are inside 9:00–17:00.
| Kathmandu | Halifax | Day |
|---|---|---|
| 12:00 AM | 2:15 PM | previous day |
| 1:00 AM | 3:15 PM | previous day |
| 2:00 AM | 4:15 PM | previous day |
| 3:00 AM | 5:15 PM | previous day |
| 4:00 AM | 6:15 PM | previous day |
| 5:00 AM | 7:15 PM | previous day |
| 6:00 AM | 8:15 PM | previous day |
| 7:00 AM | 9:15 PM | previous day |
| 8:00 AM | 10:15 PM | previous day |
| 9:00 AM | 11:15 PM | previous day |
| 10:00 AM | 12:15 AM | same day |
| 11:00 AM | 1:15 AM | same day |
| 12:00 PM | 2:15 AM | same day |
| 1:00 PM | 3:15 AM | same day |
| 2:00 PM | 4:15 AM | same day |
| 3:00 PM | 5:15 AM | same day |
| 4:00 PM | 6:15 AM | same day |
| 5:00 PM | 7:15 AM | same day |
| 6:00 PM | 8:15 AM | same day |
| 7:00 PM | 9:15 AM | same day |
| 8:00 PM | 10:15 AM | same day |
| 9:00 PM | 11:15 AM | same day |
| 10:00 PM | 12:15 PM | same day |
| 11:00 PM | 1:15 PM | same day |
Hour by hour: Kathmandu (UTC+5:45) → Halifax (ADT, UTC−3)
There is no time when both Kathmandu and Halifax are inside 9:00–17:00.
| Kathmandu | Halifax | Day |
|---|---|---|
| 12:00 AM | 3:15 PM | previous day |
| 1:00 AM | 4:15 PM | previous day |
| 2:00 AM | 5:15 PM | previous day |
| 3:00 AM | 6:15 PM | previous day |
| 4:00 AM | 7:15 PM | previous day |
| 5:00 AM | 8:15 PM | previous day |
| 6:00 AM | 9:15 PM | previous day |
| 7:00 AM | 10:15 PM | previous day |
| 8:00 AM | 11:15 PM | previous day |
| 9:00 AM | 12:15 AM | same day |
| 10:00 AM | 1:15 AM | same day |
| 11:00 AM | 2:15 AM | same day |
| 12:00 PM | 3:15 AM | same day |
| 1:00 PM | 4:15 AM | same day |
| 2:00 PM | 5:15 AM | same day |
| 3:00 PM | 6:15 AM | same day |
| 4:00 PM | 7:15 AM | same day |
| 5:00 PM | 8:15 AM | same day |
| 6:00 PM | 9:15 AM | same day |
| 7:00 PM | 10:15 AM | same day |
| 8:00 PM | 11:15 AM | same day |
| 9:00 PM | 12:15 PM | same day |
| 10:00 PM | 1:15 PM | same day |
| 11:00 PM | 2:15 PM | same day |
Worked examples
| When | Kathmandu | Halifax | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 7:45 PM UTC+5:45, January 14, 2026 | 10:00 AM AST (UTC−4), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 7:45 PM UTC+5:45, July 15, 2026 | 11:00 AM ADT (UTC−3), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 5:45 AM UTC+5:45, January 1, 2027 | 8:00 PM AST (UTC−4), 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.
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.
Halifax — Atlantic Time
- IANA identifier
- America/Halifax
- Standard time
- AST · UTC−4
- Daylight time
- ADT · UTC−3
- On this clock today
- Halifax, Nova Scotia, New Brunswick, Bermuda
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Halifax; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 8, 2026, 3:00 AM local (2026-03-08 06:00 UTC): clocks go forward to UTC−3 (ADT)
- Nov 1, 2026, 1:00 AM local (2026-11-01 05:00 UTC): clocks go back to UTC−4 (AST)
- Mar 14, 2027, 3:00 AM local (2027-03-14 06:00 UTC): clocks go forward to UTC−3 (ADT)
- Nov 7, 2027, 1:00 AM local (2027-11-07 05:00 UTC): clocks go back to UTC−4 (AST)
AST here is Atlantic Standard Time (UTC−4). Arabia Standard Time (UTC+3) is on the Riyadh 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.