Explore · time zones
Kathmandu to CET converter
Nepal Time (Kathmandu) → Central European Time (Paris)
Quick answer
The difference changes with daylight saving time. Paris is 4 hours 45 minutes behind Kathmandu from Jan 1, 2026 to Mar 29, 2026 01:00 UTC (Paris on CET · UTC+1); 3 hours 45 minutes behind Kathmandu from Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTC (Paris on CEST · UTC+2); 4 hours 45 minutes behind Kathmandu from Oct 25, 2026 01:00 UTC to Dec 31, 2026 (Paris on CET · UTC+1).
- Jan 1, 2026 to Mar 29, 2026 01:00 UTCKathmandu (UTC+5:45) → Paris (CET, UTC+1)Paris is 4 hours 45 minutes behind Kathmandu
- Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTCKathmandu (UTC+5:45) → Paris (CEST, UTC+2)Paris is 3 hours 45 minutes behind Kathmandu
- Oct 25, 2026 01:00 UTC to Dec 31, 2026Kathmandu (UTC+5:45) → Paris (CET, UTC+1)Paris is 4 hours 45 minutes behind Kathmandu
9:00 AM UTC+5:45 in Kathmandu is 4:15 AM CET (UTC+1) in Paris, the same day. Paris is 4 h 45 min behind Kathmandu.
| Format | Result | Copy |
|---|---|---|
| ParisCET · UTC+1 · Wednesday, January 14, 2026 · the same day | 4: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768360500 | |
| RFC 2822UTC | Wed, |
Conversions use Kathmandu (Asia/Kathmandu) and Paris (Europe/Paris). Other cities reached through search aliases may have different historical rules.
Current time in Kathmandu and Paris
Hour by hour: Kathmandu (UTC+5:45) → Paris (CET, UTC+1)
Both sides are inside 9:00–17:00 from 1:45 PM to 5:00 PM UTC+5:45 in Kathmandu (3 hours 15 minutes).
| Kathmandu | Paris | Day |
|---|---|---|
| 12:00 AM | 7:15 PM | previous day |
| 1:00 AM | 8:15 PM | previous day |
| 2:00 AM | 9:15 PM | previous day |
| 3:00 AM | 10:15 PM | previous day |
| 4:00 AM | 11:15 PM | previous day |
| 5:00 AM | 12:15 AM | same day |
| 6:00 AM | 1:15 AM | same day |
| 7:00 AM | 2:15 AM | same day |
| 8:00 AM | 3:15 AM | same day |
| 9:00 AM | 4:15 AM | same day |
| 10:00 AM | 5:15 AM | same day |
| 11:00 AM | 6:15 AM | same day |
| 12:00 PM | 7:15 AM | same day |
| 1:00 PM | 8:15 AM | same day |
| 2:00 PM | 9:15 AM | same day |
| 3:00 PM | 10:15 AM | same day |
| 4:00 PM | 11:15 AM | same day |
| 5:00 PM | 12:15 PM | same day |
| 6:00 PM | 1:15 PM | same day |
| 7:00 PM | 2:15 PM | same day |
| 8:00 PM | 3:15 PM | same day |
| 9:00 PM | 4:15 PM | same day |
| 10:00 PM | 5:15 PM | same day |
| 11:00 PM | 6:15 PM | same day |
Hour by hour: Kathmandu (UTC+5:45) → Paris (CEST, UTC+2)
Both sides are inside 9:00–17:00 from 12:45 PM to 5:00 PM UTC+5:45 in Kathmandu (4 hours 15 minutes).
| Kathmandu | Paris | Day |
|---|---|---|
| 12:00 AM | 8:15 PM | previous day |
| 1:00 AM | 9:15 PM | previous day |
| 2:00 AM | 10:15 PM | previous day |
| 3:00 AM | 11:15 PM | previous day |
| 4:00 AM | 12:15 AM | same day |
| 5:00 AM | 1:15 AM | same day |
| 6:00 AM | 2:15 AM | same day |
| 7:00 AM | 3:15 AM | same day |
| 8:00 AM | 4:15 AM | same day |
| 9:00 AM | 5:15 AM | same day |
| 10:00 AM | 6:15 AM | same day |
| 11:00 AM | 7:15 AM | same day |
| 12:00 PM | 8:15 AM | same day |
| 1:00 PM | 9:15 AM | same day |
| 2:00 PM | 10:15 AM | same day |
| 3:00 PM | 11:15 AM | same day |
| 4:00 PM | 12:15 PM | same day |
| 5:00 PM | 1:15 PM | same day |
| 6:00 PM | 2:15 PM | same day |
| 7:00 PM | 3:15 PM | same day |
| 8:00 PM | 4:15 PM | same day |
| 9:00 PM | 5:15 PM | same day |
| 10:00 PM | 6:15 PM | same day |
| 11:00 PM | 7:15 PM | same day |
Worked examples
| When | Kathmandu | Paris | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 7:45 PM UTC+5:45, January 14, 2026 | 3:00 PM CET (UTC+1), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 7:45 PM UTC+5:45, July 15, 2026 | 4:00 PM CEST (UTC+2), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 5:45 AM UTC+5:45, January 1, 2027 | 1:00 AM CET (UTC+1), 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.
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.
CET — Central European Time
- IANA identifier
- Europe/Paris
- Standard time
- CET · UTC+1
- Daylight time
- CEST · UTC+2
- On this clock today
- Paris, Berlin, Rome, Madrid, Amsterdam, Brussels, Vienna, Stockholm, Warsaw, Zurich
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Europe/Paris; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 29, 2026, 3:00 AM local (2026-03-29 01:00 UTC): clocks go forward to UTC+2 (CEST)
- Oct 25, 2026, 2:00 AM local (2026-10-25 01:00 UTC): clocks go back to UTC+1 (CET)
- Mar 28, 2027, 3:00 AM local (2027-03-28 01:00 UTC): clocks go forward to UTC+2 (CEST)
- Oct 31, 2027, 2:00 AM local (2027-10-31 01:00 UTC): clocks go back to UTC+1 (CET)
CET is UTC+1; CEST (UTC+2) applies from the last Sunday of March to the last Sunday of October across the EU.
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.