The 1885 Survey That Fixed India’s Train Map to a Single Clock

If you catch a train from Mumbai to Delhi today, you glance at your watch and expect the departure board to match. That simple trust in a single clock did not exist before 1885. For the first three decades of Indian railways, every station ran on its own local time—determined by the sun at that longitude. A train from Bombay to Calcutta could lose or gain minutes at each stop, and passengers and crew alike had to juggle a half-dozen different times along the route. The system worked, after a fashion, until a collision near Bhusawal killed at least eight people and forced the colonial administration to impose one clock on the entire network.

The Madras Observatory’s Lonely Clock

Before 1885, time in India was a local affair. Each town set its clocks by the sun: noon was when the sun stood highest in that particular sky. The Madras Observatory, founded in 1792, kept its own time—5 hours 21 minutes ahead of Greenwich Mean Time. Bombay followed a different meridian, placing it 4 hours 51 minutes ahead of GMT. Calcutta, farther east, was 5 hours 53 minutes ahead. Delhi, though not yet a major rail hub, split the difference at roughly 5 hours 20 minutes.

For the traveller, this meant that a journey from Bombay to Calcutta—a distance of roughly 1,700 km—involved a cumulative time shift of more than an hour. A train departing Bombay at 8:00 am local time would, by the time it reached Calcutta, have to reconcile its schedule with a station clock that was 62 minutes ahead. Station masters carried conversion charts, and timetables were printed with footnotes explaining which local time applied at each stop.

The railways themselves were not bothered at first. Each line operated within its own territory: the Great Indian Peninsula Railway (GIPR) served western and central India, the East Indian Railway (EIR) covered the east, and the Madras Railway handled the south. Inter-line traffic was limited, and each company saw local time as sufficient. But as the network grew and trains began crossing company boundaries, the patchwork became a hazard.

Telegraph offices, which needed precise timing for message routing, were the first to push for standardisation. The Madras Observatory’s time was already used by many telegraph clerks because it was the most consistently recorded across the presidency. Yet the railway companies resisted, arguing that changing all their station clocks would be expensive and confusing to passengers used to local sunrise.

One Crash That Forced a National Time

The turning point came on the morning of 14 February 1885, near the town of Bhusawal in present-day Maharashtra. Two trains on the Great Indian Peninsula Railway—a goods train and a passenger train—were running on the same single-track section. The station masters at either end had each consulted their own clocks, which were not synchronised. The result was a head-on collision that, by most contemporary accounts, killed eight people and injured dozens more.

The exact death toll remains uncertain. Official reports from the GIPR put the number at eight, but local newspapers at the time claimed twelve or more. What is clear is that the accident triggered an immediate inquiry by the railway board in Bombay. The board’s report, submitted in March 1885, concluded that the primary cause was a discrepancy in station clocks: the two stations involved were using different local times, and the train crews had no reliable way to reconcile them.

Sir William Gull, the railway commissioner for the Government of India, took up the cause. He had been arguing for a single railway time since 1883, when British railways had themselves adopted a standard time (Railway Time, later Greenwich Mean Time) after years of local confusion. Gull saw the Bhusawal crash as proof that India needed the same reform. In a memorandum to the Viceroy’s council, he proposed that all railway stations in India adopt a single time standard, based on the Madras Observatory’s meridian, effective from 1 January 1886.

The proposal was not universally welcomed. The Bombay Chamber of Commerce objected that Madras time was “inconveniently far” from Bombay’s solar time, and that the change would disrupt port schedules. The Calcutta Chamber worried that a single time would hurt eastern businesses, which were used to an earlier sunrise. But Gull and the railway board pressed ahead, arguing that safety trumped convenience. In July 1885, the Viceroy approved the plan, contingent on a survey to calibrate every station clock to the new standard.

How They Chose the Meridian for All India

The choice of Madras time as the national standard was not obvious. Three observatories—Madras, Bombay, and Calcutta—each had a claim. Madras time (5 hours 21 minutes ahead of GMT) was already used by the telegraph network, which gave it a head start. Bombay time was only 4 minutes behind Madras—a difference so small that many clock faces could not even show it. Calcutta time, by contrast, was 32 minutes ahead of Madras, a gap large enough that western India would have to start its day nearly half an hour earlier by the clock.

The railway board considered a compromise: use Calcutta time for eastern lines and Madras time for the rest. But that would have preserved the very confusion that caused the Bhusawal crash. Gull argued that a single standard, even if imperfect, was better than a dual system. He also noted that Madras time was close to the mean solar time of the 82.5° East meridian, which roughly bisected the subcontinent. That meridian would later be adopted as Indian Standard Time in 1905, but in 1885 it was simply a convenient average.

The decision was announced in August 1885: from 1 January 1886, all railway stations in British India would use Madras time. The term “Indian Standard Time” was not yet used; it was simply called “Railway Time” or “Madras Time.” The change applied only to railways and telegraphs; ordinary civil time remained local. But for the passenger, the railway clock became the most visible clock in town, and over time, local civil time quietly faded.

One quirk remained: the city of Calcutta, whose merchants had lobbied hard against the change, was allowed to keep its own time for official municipal documents. That practice survives in a minor way even today—some old Kolkata records still cite “Calcutta time” as a historical footnote. But for the trains, Madras time was the law.

The 1885 Survey That Measured Every Track

Setting a single time on paper was one thing; making every station clock show the same second was another. The railway board turned to the Great Trigonometrical Survey of India, the same organisation that had mapped the subcontinent’s geography over the preceding century. The survey’s officers were skilled in astronomical observation and chronometer calibration, and they were already familiar with telegraph-based time signalling.

The plan was to send survey parties to every major railway junction—roughly 200 stations across the network—and set their clocks to Madras time using telegraph signals. At a pre-arranged moment, the Madras Observatory would send a time signal along the telegraph wires. The surveyor at each station would hear the signal and adjust the station clock accordingly. The process had to be repeated several times to account for signal delays, which varied with distance and wire quality.

The survey began in September 1885 and took 18 months to complete. The total cost was about ₹1.2 lakhs (roughly ₹4 crore in today’s value, adjusting for inflation). Each surveyor carried a chronometer that had been calibrated at Madras, and they travelled by train, cart, and sometimes on foot to reach remote stations. The work was tedious but essential: a single station clock that was off by even a minute could cause a scheduling error.

One surveyor, writing in his diary, noted that the biggest challenge was not the calibration itself but convincing station masters to trust the new time. Many had been using local sundials for years and saw the telegraph signal as an abstract concept. The surveyors had to demonstrate that the signal was accurate by showing that the sun’s position matched the clock at the moment of local noon. Only then did the station masters accept the change.

What the New Clock Meant for Passengers

For the average passenger, the introduction of Railway Time was both a blessing and a confusion. Suddenly, the 5:15 pm train to Delhi left at 5:15 pm at every station along the route. Timetables, which had previously been printed with multiple time columns, could now be simplified. The 1886 edition of Bradshaw’s Indian Railway Guide, the standard timetable for the subcontinent, adopted Madras time throughout, making it possible to plan a journey across company boundaries without arithmetic.

But the change also meant that the clock no longer matched the sun. In Bombay, for example, the sun reached its zenith at about 12:04 pm by the new Railway Time, not at 12:00. In Calcutta, the sun was at its highest at 11:28 am. Farmers and rural passengers, who relied on the sun for their daily routines, found the railway clock confusing. Many stations kept a sundial in the waiting room as a reference, and some station masters would announce both times until passengers got used to the new system.

The confusion lasted for decades. In the 1890s, a traveller from Madras to Calcutta complained in a letter to a newspaper that he had missed his connection because he had relied on a village sundial that was 20 minutes behind the station clock. The railway company, in its defence, pointed out that the station clock was the official time and that passengers should adjust their watches accordingly. But for people who had never owned a watch—and most Indians at the time did not—the sundial remained the only clock they trusted.

For the railway staff, the new standard simplified operations considerably. Station masters no longer needed to calculate local-to-local times when scheduling trains. The telegraph operators, who had already been using Madras time, found their work easier because the railway clocks now matched their own. And the train crews, who had been the most vocal advocates for standardisation, could finally rely on a single time from departure to arrival.

The Quirks That Survived the Standardisation

Even after the 1885 survey, pockets of local time persisted. The city of Calcutta, as mentioned, kept its own official time for municipal documents until well into the 20th century. Some government offices in the city continued to use “Calcutta time” for internal records, and it was not until 1905, when Indian Standard Time (IST) was formally adopted, that the last vestiges of local time disappeared from official use.

More stubborn were the tea gardens of Assam. The gardens, which were often far from railway lines, operated on “Tea Garden Time”—a full hour ahead of IST. The logic was practical: tea plucking starts at dawn, and by setting the clock an hour ahead, the workers could finish their shifts earlier in the heat of the day. Tea Garden Time persisted in some estates until the 1950s, and even today, older workers in Assam sometimes refer to it.

The railways themselves were not entirely uniform. As late as 1950, some stations in the northeast—particularly on the Assam Bengal Railway—ran on “Railway Time” that was 30 minutes ahead of IST. This was a legacy of the old Calcutta time, which had been used on that line before 1885. The discrepancy was small enough that it caused no accidents, but it confused passengers who travelled from one line to another.

Today, the Indian Railways uses a 24-hour clock exclusively, and all schedules are based on IST (UTC+5:30). The 1885 survey’s meridian—82.5° East—still defines IST, and the system has never adopted daylight saving time. The collision that prompted the reform is now a footnote in railway museums, but its legacy is visible every time a passenger checks a platform clock.

Why a 140-Year-Old Clock Still Rules Your Journey

The 1885 survey was not the end of time standardisation in India—it was the beginning. In 1905, the government formally adopted Indian Standard Time, based on the 82.5° East meridian, which was very close to the Madras time used by the railways. The change was largely administrative, since most clocks already followed Railway Time. But it extended the standard beyond the railways to all government and commercial activities.

One of the most enduring quirks of this system is that India has a single time zone for its entire landmass, despite spanning nearly 30 degrees of longitude. This means that the sun rises and sets nearly two hours earlier in the east than in the west. There have been periodic calls for a second time zone for the northeastern states, but the government has resisted, citing the complexity of changing railway schedules and the 1885 precedent.

The 1885 survey itself is largely forgotten. The surveyors’ names are not recorded in any monument, and the Bhusawal crash is mentioned only in a handful of railway history books. But the infrastructure they created—the synchronised clocks, the standardised timetables, the single time that governs every train—remains in place. Next time you check a platform clock, you are looking at the legacy of that 18-month effort to make every station in India tick together.

The reform was not perfect. It privileged the railways over local customs, and it imposed a single rhythm on a diverse subcontinent. But it also made long-distance travel predictable, and it saved lives. The collision that forced the change was a tragedy, but the response was a rare example of colonial bureaucracy solving a problem efficiently. For better or worse, the 1885 survey fixed India’s train map to a single clock, and that clock is still ticking.