Why every city kept its own clock before IST
Bombay ran on Bombay Time, set by the observatory at the Colaba lighthouse. The eastern capital used Calcutta Time, based on the sun over Bengal. Madras had Madras Time. Each city sat a few minutes off its neighbour.
For a person walking to a local market, the gap meant nothing. For the expanding railway network, it was a disaster.
A train leaving Bombay at 10:00 Bombay Time arrived in the eastern metropolis at a time that meant something different there. Passengers missed connections. Freight sat on sidings. Stationmasters kept conversion charts on their desks. The system limped along only because station clocks in each city were reset to match the local standard. The railway itself had no single reference.
What the railway actually needed
The Indian Railway Conference Association began pushing for a single time standard in the early 1900s. Their argument was simple: a network that spanned a subcontinent could not function with a dozen local times. Timetables, signalling, and crew scheduling all required one clock.
The colonial administration agreed in principle but faced two problems.
First, which city's time would become the standard? Bombay and the eastern capital were the two biggest commercial centres. Bombay Time was UTC+4:51. Calcutta Time was UTC+5:53:20. The difference of roughly one hour and two minutes meant neither city would accept the other's time without a fight.
Second, the sun. India spans nearly 30 degrees of longitude. A single time zone means sunrise and sunset times vary hugely between east and west. Even today, the sun rises in the northeast about an hour before it rises in Gujarat. In 1905, few people in power cared about the northeast, but the principle still had to be justified.
Why the IST meridian sits at 82.5° east
The solution was a compromise longitude: 82.5° east.
This meridian passes through Mirzapur, a town near Allahabad (now Prayagraj) in Uttar Pradesh. It sits almost exactly halfway between the westernmost and easternmost points of British India. At 82.5°E, the local mean time is UTC+5:30, splitting the difference between the eastern capital (roughly UTC+5:53) and Bombay (roughly UTC+4:51).
The choice was not about astronomy. It was about the railway timetable.
A meridian at 82.5°E meant that no major city had to shift by more than about 23 minutes from its existing local time. Bombay moved forward by 39 minutes. The eastern hub moved backward by about 23 minutes. Madras, already on a local time close to UTC+5:30, barely changed. The disruption to daily life was kept to a minimum.
1 January 1906: the railway takes over
India Standard Time came into effect on 1 January 1906. The order applied to the entire railway network first. Station clocks were reset. Timetables were reprinted. Every train in the country now ran on the same minute.
Cities and towns gradually followed. Bombay adopted IST for official purposes in 1906 but many businesses kept Bombay Time for years. The city on the Hooghly held out longest: its stock exchange, its port, and many private firms continued using the old local time informally until the 1940s. The last holdouts in the northeast did not fully switch until after independence.
The railway, however, never looked back. Once the network was on IST, the cost of maintaining local times became too high. Passengers expected one timetable. Freight moved faster. Crews could be scheduled across divisions without conversion errors.
Why the railway still anchors IST today
Indian Railways remains the single largest practical anchor for India Standard Time. Every station, every train schedule, every ticket, every announcement uses IST. If India ever adopted a second time zone, as has been proposed for the northeast, the railway would have to be the first institution to change. That is why proposals for a second time zone have repeatedly stalled. The cost of retraining staff, reprinting timetables, and reprogramming signalling systems is enormous.
The railway also enforces IST in places where local habits might otherwise drift. Tea gardens in Assam operate on "Tea Garden Time", an informal offset of roughly UTC+5 or UTC+6 that gives workers more daylight hours. But the trains that carry the tea out of Assam run on IST. The station clock is the official clock.
Does the IST offset ever change with the seasons?
The offset itself does not change. India Standard Time stays fixed at UTC+5:30 year-round. No daylight saving.
What shifts is how IST relates to zones that do observe DST. On 15 January 2026, relative to IST, New York is 10.5 hours behind, London 5.5 hours behind, and Sydney 5.5 hours ahead. By 15 July 2026, when much of the northern hemisphere has moved to summer time, New York becomes 9.5 hours behind, London 4.5 hours behind, and Sydney 4.5 hours ahead.
The practical takeaway: the half-hour offset that makes IST confusing to convert (why 5.5? why not 5 or 6?) is the same compromise that solved a railway problem in 1906. It is not arbitrary. It is the shadow of a colonial compromise between two rival commercial capitals, preserved by a railway network that cannot afford to change.
The next time you miss a meeting because you rounded IST to UTC+5 or UTC+6, remember: the railway chose 5.5 because it was the only number that worked for everyone. It still is.