Kathmandu
Nepal
--:--
Local date loading
Reference hours 09:00–18:00
TIME IN
Delhi
India · Asia/Kolkata
--:--:--
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
Delhi’s zone name and minutes both matter
The catalog maps Delhi to Asia/Kolkata. The zone name identifies a rule set; it does not mean the selected city has changed to Kolkata. Both dated examples show UTC+05:30, so the thirty-minute part must remain in any conversion.
Mumbai matches Delhi in the examples, while Kathmandu is fifteen minutes ahead. London is five hours and thirty minutes behind Delhi in January and four hours and thirty minutes behind in July. When sharing a plan, include the full local time and date rather than rounding these relationships.
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:30 | UTC+05:30 |
| 2026-07-15 | 2026-07-15 | 17:30 | UTC+05:30 |
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 1273294, 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.