Why India Has Only One Time Zone

India is almost 3,000 kilometres wide. The sun reaches its eastern border close to two hours before it reaches the western one. Every clock in the country nonetheless reads the same thing, and that single clock sits on an awkward half hour, UTC+5:30. Both facts have better explanations than they first appear to.

The geography that ought to need three zones

India's westernmost point is in Gujarat, near 68°E. Its easternmost is in Arunachal Pradesh, near 97°E. That is roughly 29 degrees of longitude. Since the Earth turns one degree every four minutes, the gap between sunrise at the two ends is about one hour and fifty-seven minutes.

For comparison, the continental United States covers about 58 degrees and uses four time zones. On the same ratio India would reasonably use two, and a generous reading would give it three. It uses one.

The effect is not subtle at the eastern end. In June the sun can be up in parts of Arunachal Pradesh before 4:30 in the morning by the clock on the wall, and in December it can be gone before 4:30 in the afternoon. Offices, schools and government hours are set nationally, so the far northeast spends much of its workday in darkness at one end and wastes several hours of daylight at the other.

Where the half hour comes from

Indian Standard Time is not an arbitrary compromise. It is the local solar time of the 82.5°E meridian, which runs through Mirzapur in Uttar Pradesh, close to the middle of the country. Multiply 82.5 degrees by four minutes per degree and you get 330 minutes, which is exactly five and a half hours. The half hour is a consequence of where the chosen meridian happened to fall, not of anyone wanting a fractional offset.

India adopted it on 1 January 1906, under British administration. What is easy to forget is how long the country resisted actually using it. Calcutta kept its own local time, roughly UTC+5:53, until 1948. Bombay held out even longer, running about UTC+4:51 until 1955. For half a century after standard time was declared, India's two largest commercial cities were deliberately on different clocks from the standard and from each other.

Today those cities are identical to the minute. You can see that on the live pages for Kolkata, Mumbai and Delhi, which all read the same figure no matter when you look.

Tea garden time, India's unofficial second zone

There is a quiet exception. The tea estates of Assam have run on their own clock for well over a century, usually one hour ahead of Indian Standard Time. It is known as bagan time or chaibagan time, literally garden time.

British planters introduced it for a practical reason that has not gone away: picking tea is daylight work, and in Assam the daylight arrives absurdly early relative to the national clock. Shifting the estate day forward by an hour lets workers start near sunrise and finish before the light goes. The estates kept it after independence and many still use it.

So India does already operate a second time zone. It simply has no legal status, applies to one industry, and is invisible to every clock, timetable and booking system in the country.

The proposal to split the clock

In 2018, researchers at the CSIR National Physical Laboratory in New Delhi, the institution that actually maintains India's official time, published a case for two zones. Their proposal was IST-I at UTC+5:30 for most of the country and IST-II at UTC+6:30 for the northeastern states, with the dividing line drawn through the narrow corridor of land that connects the northeast to the rest of India.

The argument was mostly about electricity. If the northeast's working day moved forward an hour, evening lighting demand would shift to before sunset rather than after it. Their estimate of the saving was in the region of 20 million kilowatt hours a year.

The proposal was not the first. Assam's state government has pushed for a separate northeastern clock more than once, and variations on the idea have circulated since at least the 1980s.

Why it keeps not happening

The official objections are operational. India runs one of the largest railway networks on Earth, and railway safety depends on an unambiguous shared clock: two zones means every timetable, signal log and crew roster near the boundary acquires a question about which time is meant. Aviation, broadcasting and nationally scheduled examinations raise similar concerns. The Department of Science and Technology has repeatedly judged the cost of that confusion to outweigh the electricity saving.

The unofficial objection is political, and it is the one that probably matters more. The northeast has a long and complicated relationship with the centre, including decades of separatist movements. Giving the region its own clock is administratively minor and symbolically loaded, and successive governments have preferred not to touch it.

That is the real answer to why India has one time zone. It is not an oversight or a failure to notice the geography. It is a deliberate, repeatedly reaffirmed decision that a single clock is worth the daylight.

What this means when you are scheduling

The practical consequence for anyone working with India is the half hour. A great many scheduling mistakes come from people mentally treating offsets as whole numbers, so "India is five and a half hours ahead" quietly becomes "five" or "six" somewhere between the calendar invite and the meeting.

It also breaks a shortcut that usually works. You cannot convert to Indian time by changing only the hour and leaving the minutes alone, which is exactly the sort of error that produces a 30-minute near miss rather than an obvious one.

Every figure on this site is computed from the real offset rather than rounded to the nearest hour, so the half hour is always there. If you regularly work across it, the Delhi and London comparison shows the live difference and the hours when both working days actually overlap, and the India time zone page lists every Indian city on the site against its current offset.