TL;DR: India runs on a single time zone, India Standard Time (IST), which is UTC+5:30, all year. India does not observe daylight saving, so the offset never changes. The half-hour offset is the detail that catches people out: IST is not a whole number of hours from UTC, which makes mental conversion awkward and breaks assumptions in some scheduling tools.
One country, one clock
India spans a wide longitude range, roughly from Gujarat in the west to Arunachal Pradesh in the east, which geographically would justify two time zones. It uses one instead, and has done so consistently since 1947.
The reason is administrative rather than astronomical. A single national time simplifies transport, business hours, and government coordination. The cost is that sunrise in the far east arrives very early and sunset in the far west comes late, but the country accepts that for the convenience of a uniform clock.
The 5:30 offset, and why it matters
India is five and a half hours ahead of UTC. That half hour is the source of most conversion errors.
Converting from India to a whole-hour zone means the result lands on the half hour. If it is 10:00 in Delhi, it is 04:30 in London during winter, not 04:00. People routinely round, and the rounding produces a thirty-minute miss.
It also breaks naive arithmetic across two half-hour zones. Converting between India and, for example, Nepal (UTC+5:45) involves a fifteen-minute difference, which no whole-hour mental model can handle.
No daylight saving, which is the good news
India does not change its clocks. There is no summer time, no spring forward, and no autumn back. That removes an entire category of scheduling error that plagues Europe and North America.
The consequence is that the gap between India and any region that does observe daylight saving will change twice a year, in that region’s local terms. A call at 3 p.m. Delhi time is a different hour in London in January than in July, purely because London moved.
So the practical advice is asymmetric: India is the stable side, and the other side is the variable. If you are scheduling from India, ask what the other party’s offset is at that date, not what it usually is.
Conversion reference
These gaps are correct when the other region is on standard time:
- London (GMT): India is 5.5 hours ahead
- New York (EST): India is 10.5 hours ahead
- Los Angeles (PST): India is 13.5 hours ahead
- Dubai: India is 1.5 hours ahead
- Singapore and Beijing: India is 2.5 hours behind
- Sydney (AEST): India is 4.5 hours behind
During northern summer, the London, New York, and Los Angeles gaps shrink by an hour because those regions move and India does not.
India versus Sri Lanka and the neighbourhood
Sri Lanka also uses UTC+5:30, so the two countries share a clock. Nepal uses UTC+5:45, which is a fifteen-minute difference from India, an unusual arrangement that exists for national reasons rather than astronomical ones.
Bangladesh and Pakistan are on whole-hour offsets, at UTC+6 and UTC+5 respectively, so the gap to India is a clean half hour or full hour depending on direction. The region is more varied than people assume.
Business hours, practically
This is where conversion stops being trivia and becomes useful. Indian office hours are commonly around 9:30 a.m. to 6:30 p.m. IST, which maps to an awkward window for the Americas.
A 10 a.m. Delhi call is 4:30 a.m. in London during winter and 11:30 p.m. the previous night in New York. That is not a workable overlap, which is why India-Europe calls typically cluster in the Indian late afternoon and India-US calls sit in the Indian evening.
The practical fix is to schedule from the constraining side. Find the overlap window first, then convert to the other zone, rather than picking a comfortable hour for one party and hoping.
The tooling problem
Not every calendar or scheduling application handles half-hour offsets well. Some older systems store a whole-hour offset and produce a thirty-minute error, and some display times in a way that hides the half hour.
If you notice a recurring thirty-minute discrepancy with an Indian colleague, the offset handling is the first thing to check, before assuming someone misread the invitation.
For a current reading rather than a calculation, a live clock with world time zones shows the actual local time and sidesteps the arithmetic, which is worth doing whenever the half hour is involved.
Why the half hour exists at all
India’s offset is not an accident or an approximation. It is a deliberate civil choice that places the country’s clocks between the two obvious whole-hour options.
Geographically, the 82.5°E meridian runs through the middle of the country, which corresponds to UTC+5:30 almost exactly. So the half hour is, in a sense, the most honest offset India could have chosen for a single-zone country: it splits the difference between the western and eastern edges.
That also explains why the sun rises unusually early in the far east and sets unusually late in the far west. The clock is calibrated to the country’s centre, and the edges pay for it.
There have been proposals to introduce a second time zone for the northeast, where sunrise can arrive before 5 a.m. in summer. None has been adopted, largely because the administrative cost of splitting the country’s clock is considered higher than the inconvenience of early sunrises.
The short answer
India is UTC+5:30 all year, with no daylight saving. The half-hour offset is the important detail, the lack of seasonal change is the convenience, and the changing gaps with Europe and North America are the thing to double-check.