Was the Mirzapur meridian picked because it is India’s geographic centre?

The neat geography lesson says the 82.5°E meridian runs roughly through the middle of the country, so it was a natural choice. It sounds logical. It is also incomplete.

The 82.5°E line does not cut India in half. The country’s westernmost point sits around 68°E, and its easternmost around 97°E. The midpoint is closer to 82.5°E, but that is a coincidence, not the reason.

Why was the 82.5°E meridian at Mirzapur selected for IST?

Before 1906, India did not have one time. It had several.

  • Bombay Time was UTC+4:51 (set by the Bombay Observatory).
  • Calcutta Time was UTC+5:53:20 (set by the Madras Observatory and later used by Calcutta).
  • Madras Time was UTC+5:21, used by the Madras Observatory and widely followed by railways.

The railways ran on Madras Time as a default, but it was not standardised. A train leaving Bombay at 08:00 local time arrived in Calcutta at a different local time, and the timetable had to convert manually. Passengers missed connections. Freight schedules were a mess.

In 1905, the colonial administration pushed for a single national time. The question was: which meridian?

How the Mirzapur meridian split the difference between Bombay and Calcutta

Calcutta Time (UTC+5:53:20) and Bombay Time (UTC+4:51) were almost an hour apart. Picking either one would have forced the other city to shift its daily rhythm by nearly an hour.

The solution was the 82.5°E meridian, which passes through Mirzapur (near modern-day Prayagraj in Uttar Pradesh). At UTC+5:30, it splits the difference:

  • Calcutta is 23 minutes and 20 seconds ahead of the new standard.
  • Bombay is 39 minutes behind.

It was a political and practical compromise, not a geographic one. The meridian was chosen because it landed roughly halfway between India’s two most important colonial cities at the time.

Why Mirzapur and not another town on the 82.5°E meridian?

Mirzapur itself was not special. The 82.5°E line happens to run through it. The city was a convenient reference point for the survey of India, which had already mapped the country using that meridian. But the decision was about the line of longitude, not the town.

If the 82.5°E line had passed through a different village, that village would be the answer today. Mirzapur is the place on the map, but the reason is the compromise.

When did IST based on the Mirzapur meridian take effect?

On 1 January 1906, Indian Standard Time (IST) was adopted at UTC+5:30. The railways switched immediately. Other cities followed slowly. Calcutta Time persisted informally in parts of the northeast until the mid-20th century.

When India became independent in 1947, the new government kept IST as the single national time zone. There were debates about introducing multiple zones, the northeast argued for a separate time to make better use of daylight, but the "one-nation-one-time" policy won. It remains the official position today.

Why does the Mirzapur meridian give India a 30-minute offset?

The 82.5°E meridian puts India at UTC+5:30. That is unusual. Most time zones are whole hours from UTC. India is one of a handful of countries with a 30-minute offset, alongside Nepal (UTC+5:45), Iran (UTC+3:30), and parts of Australia (ACST at UTC+9:30).

The 30-minute offset is a direct result of the compromise. If the meridian had been at 75°E, the offset would be UTC+5. If it had been at 90°E, it would be UTC+6. The 82.5°E line splits the difference, and the 30-minute offset is the mathematical consequence.

Does the Mirzapur-based IST still cause problems today?

Yes, for three reasons:

  1. The northeast sunrise problem. Because India uses a single time zone based on a meridian in the centre, the sun rises and sets later in the northeast than it would under a local time. Some tea gardens in Assam operate on "Tea Garden Time" (informally UTC+5 or UTC+6) to start work earlier. This is not a legal time zone, but it shows the friction.

  2. The 30-minute confusion. People who convert IST to other time zones often round to UTC+5 or UTC+6, missing the 30-minute difference. A meeting scheduled at 09:00 IST becomes 04:30 BST in London, not 04:00 or 05:00. The 30-minute offset causes regular scheduling errors.

  3. The IST abbreviation clash. IST is also used for Irish Standard Time (UTC+1, summer only in Ireland) and Israel Standard Time (UTC+2, winter in Israel). If you see "IST" in a meeting invitation, you need to check which country is meant. The IST abbreviation meanings page explains the three.

How to avoid IST scheduling mistakes around the 30-minute offset

If you are scheduling calls or flights involving India, do not round the 30-minute offset. Use a converter that handles it correctly. The IST converter shows live conversions for any time zone.

If you are curious about the northeast sunrise problem and the debate around a second time zone, the article on why India has only one time zone covers the arguments on both sides.