Delhi
India
--:--
Local date loading
Reference hours 09:00–18:00
TIME IN
Kathmandu
Nepal · Asia/Kathmandu
--:--:--
Your current date appears here.
Using device time
View accuracy details
The clock starts with your device time. A server check can improve the estimate when its synchronization health is known.
THE SAME SHARED MOMENT
Compare with other cities
A LITTLE LOCAL CONTEXT
Kathmandu’s quarter hour is part of the time
Kathmandu is at UTC+05:45 in both dated examples. Delhi is fifteen minutes behind, so rounding the difference to zero or a full hour would give the wrong local appointment. At the example 12:00 UTC instant, Kathmandu reads 17:45 rather than 17:30.
Singapore is two hours and fifteen minutes ahead of Kathmandu at both sample instants. London is five hours and forty-five minutes behind in January and four hours and forty-five minutes behind in July. Preserve those minutes and the date when copying a conversion for another participant.
Dated examples, not the current time
Both rows use 12:00 UTC on the stated date. The local date and time below follow the pinned 2026a rules.
| UTC date | Local date | Local time | UTC offset |
|---|---|---|---|
| 2026-01-15 | 2026-01-15 | 17:45 | UTC+05:45 |
| 2026-07-15 | 2026-07-15 | 17:45 | UTC+05:45 |
Two samples are not a complete transition calendar or a guarantee of future rules. Convert your actual date and time; understand skipped and repeated times.
The live display begins with device time and requests a synchronized estimate when the server's health is known. Its status explains which source is in use. JavaScript is required for the moving clock; place and zone information remain available without it.
How the clock estimates time · Browse reviewed city clocks
City location data: GeoNames record 1283240, used under CC BY 4.0; curated and normalized by Clock.live. Zone rules: IANA 2026a via js-joda. Data sources and versions.
Planning content and examples reviewed . These are data-derived planning examples, not independently surveyed local schedules.