Dubai
United Arab Emirates
--:--
Local date loading
Reference hours 09:00–18:00
TIME IN
Mumbai
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
Plan from Mumbai without rounding the result
Mumbai is at UTC+05:30 in January and July in the examples. Dubai is one hour and thirty minutes behind, while Singapore is two hours and thirty minutes ahead. Keeping minutes visible is essential even when every meeting starts on a whole local hour.
Delhi shares Mumbai’s Asia/Kolkata rule set in this catalog. The same-zone relationship can simplify a two-city plan, but adding a third city still calls for a dated comparison. Use the board for a shared moment and the converter when the appointment belongs to a different day.
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 1275339, 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.