The War Time Charts: Indian Births 1942–45

For three years, India's clocks did not tell Indian Standard Time — and the horoscopes of a whole generation carry the hour that history moved.

1. A generation's charts, one hour out of place

The people born under India's War Time are in their early-to-mid eighties now. Their jātakams are among the most emotionally weighted documents a family owns: consulted for their marriages half a century ago, revisited for shashtiabdapoorthi and sadabhishekam celebrations, cited when grandchildren's charts are compared with theirs. And a very large fraction of those charts — any that were computed, then or since, on the assumption that a wartime clock reading was an IST reading — are internally shifted by one hour.

This is not a defect of the old astrologers, and it is emphatically not a defect of the elders' stars. It is a bookkeeping fact about clocks, of the same family as the diaspora daylight-saving errors we catalogue in a companion article — except this one happened inside India, where nobody expects timezone history at all. That is exactly why it deserves its own treatment.

2. What happened to India's clocks

Indian Standard Time — UTC+5:30, the meridian of 82.5°E near Mirzapur — was established in 1906. Before it, the presidencies kept their own local times, two of which will matter later in this article. From 1906 the subcontinent ran steadily on IST — until the war reached Asia.

As a wartime economy measure (the same logic as Britain's and America's summer clocks: shift waking hours into daylight, save fuel and lighting), the Government of India advanced the civil clock by one hour, to UTC+6:30. The IANA time zone database — the historical record used by the world's computers — carries the two spells:

Table 1 — India's civil clock through the war years, per the IANA tz database (Asia/Kolkata). The second spell — over three full years — is the big cohort.

Every birth certificate, temple record and family notebook from those windows records the advanced clock. The 8:15 AM written beside a 1943 birth means 7:15 AM IST. Unless someone, somewhere in the chain — the original astrologer, a later recomputation, or the software — subtracted that hour, the chart stands computed for the wrong sky.

3. The demonstration: one hour, visible in the lagna

Rather than argue abstractly, we computed it. Take the identical civil description — 15 June, 6:00 AM, Delhi — in a war year and a peace year, on the juno.date engine (which resolves historical time through the IANA database):

Table 2 — Same date on the calendar, same clock reading, same city, Sun within a quarter-degree of the same place — and a different rising sign. The one-hour war clock is the entire difference. (Values computed on the juno.date engine, June 2026 build; reproduce them yourself on juno.date/jataka.)

An engine that assumed IST-forever would output Mithuna for both years. For the 1943 birth that answer is an hour wrong — and the person who owns that chart has prayed, matched and planned around a Mithuna-lagna document for eighty years while the sky at their birth rose in Rishaba. Multiply by every lagna-boundary case in three years of births across undivided India, and the scale of the quiet error becomes clear.

4. How much damage is one hour? (The short version)

We derive these figures fully in the birth-time sensitivity article; here is the wartime summary:

Table 3 — The uncorrected war hour, itemised.

5. The genuinely tricky part: which charts were already corrected?

Here the story becomes more delicate than the diaspora case, and honesty requires saying so. The astrologers of the 1940s were not naive about time — quite the opposite: the learned ones worked from ishta-ghatika (time after local sunrise) and were fully accustomed to converting between civil clocks and local solar time. Some certainly knew about War Time and subtracted the hour before casting. Others — particularly in the years and decades after the war, recomputing from a written "8:15 AM" with the war forgotten — did not. A wartime family chart therefore sits in one of three states, and you usually cannot tell which by looking:

Table 4 — The three states of a wartime horoscope. State C is why blind recomputation isn't enough either.

This three-way ambiguity is unique to historical-DST cohorts and it means the correct protocol is a comparison, not a replacement: compute both candidate charts — the recorded time resolved through the war-time rules, and the recorded time as plain IST — and check which one matches the facts the family knows. The old papers often record verifiable anchors: the nakshatra the elder has always been called by, the dasa sequence an astrologer once recited, whether the birth was "just before sunrise". One of the two candidate charts will agree with those anchors; that one is the truth of the certificate.

6. The other survivors: Calcutta time and Bombay time

War Time is the largest historical-clock cohort, but two older Indian time regimes also outlived their official welcome, and both show up in old horoscopes:

Calcutta time — UTC+5:53:20. The old Bengal standard, 23 minutes 20 seconds ahead of IST, remained in official use in Calcutta until 1948. A 1946 Calcutta birth certificate may be Calcutta time, not IST — a 23-minute shift that moves the lagna about 6°, flipping roughly one chart in five near boundaries, and shifting navamsa lagnas almost always.

Bombay time — UTC+4:51. Abolished officially decades earlier, it persisted unofficially in parts of the city into the 1950s — office clocks and railway clocks famously disagreeing by 39 minutes. For mid-century Bombay births, the honest question is which clock the hospital or home followed; where family lore says "railway time" or "office time", that lore is data.

Both cases yield to the same comparison protocol as War Time: compute the candidates, test against remembered anchors, let the nakshatra adjudicate.

7. Why almost no software handles this

Because for post-1947 India, ignoring timezone history costs nothing — and India-focused tools are built and tested on post-1947 births. The war windows sit outside living QA. A tool reveals its architecture instantly on the Table 2 test: enter the same date-time-city pair for 1943 and 1946 and compare lagnas. Identical output = IST-forever assumption; a one-hour-shifted 1943 output = database-driven resolution. (This is the same one-minute fingerprint we apply to daylight-saving handling in our ePanchang and ProKerala reviews — the wartime probe is simply its Indian-history edition.)

juno.date resolves every birth through the IANA database, and we have verified our engine's handling at all four War-Time boundaries (probes on either side of 1 Oct 1941, 15 May 1942, 1 Sep 1942 and 15 Oct 1945 show the one-hour shift engaging and releasing exactly on schedule). Two caveats stated plainly. First, the IANA zone data by design tracks the standard zone — it does not model Calcutta Time's administrative persistence to 1948, so a 1935–48 Bengal certificate written in Calcutta Time needs the additional +23:20 correction; we are building a dedicated period-adjustment layer for exactly such regional survivals, and until it ships, Section 5's comparison protocol covers the case. Second, for State-C papers (already-adjusted written times) no database can know what a human helpfully rewrote — which is why the comparison protocol, not blind trust in any engine including ours, is the professional answer.

8. A note on what this means, in our house voice

If this article has just told you that a beloved elder's lagna may be Rishaba rather than Mithuna, hold the news the way the tradition itself would: the sky over that 1943 dawn was never uncertain — only the paperwork was. Nothing in a life already lived is invalidated by a corrected chart; if anything, families who run the comparison often find the corrected lagna fits the person better, which is its own quiet delight. And there is something fitting, even affectionate, in the fact that checking a grandmother's horoscope now requires knowing what Churchill's war did to Indian clocks. Charts remember history. That is part of why we keep them.

9. Reading the old records themselves

Everything above assumed the family record states a clock time. Many wartime-era records do something more interesting: they state time the traditional way, and this can quietly rescue a chart from the whole problem. Three notations appear in old notebooks and horoscope margins, and each has a different relationship to the war clock. (1) Clock time ("8:15 AM", "காலை 8.15") — fully exposed to War Time; everything in this article applies. (2) Ghati-vighati after sunrise (nazhigai in the Tamil country: "sunrise + 6¼ nazhigai") — this notation is anchored to the sky, not the clock: sunrise is an astronomical event, so a birth recorded as ghatis-after-sunrise is immune to every civil-clock intervention in history. If your elder's record is in nazhigai, convert it against the computed sunrise for that date and place (1 nazhigai = 24 minutes) and the War Time question never arises — the old astrologers' habit turns out to be the most robust timestamp format ever used in India. (3) Mixed records ("about an hour after sunrise, the clock showed 7:45") — a gift: the two statements cross-check each other, and whether they agree tells you at once whether the clock in that house was war-adjusted. When helping a family reconstruct a wartime chart, always ask to see the original wording, not someone's later transcription into clock time — transcription is precisely where the hour goes missing.

10. The reverse test: what an IST-forever engine outputs

To make the failure concrete from the other side: an engine that ignores clock history, given our Table 2 birth (15 June 1943, 6:00 AM, Delhi), converts 6:00 AM at today's IST offset and computes the sky of 00:30 UT — but the birth actually occurred at 23:30 UT the previous evening. Every output downstream inherits the hour: its lagna comes out Mithuna instead of Rishaba; its navamsa lagna lands in the wrong varga with near certainty; its ishta-ghatika (time since sunrise, which many printed formats display) is wrong by 2½ nazhigai; and its Vimshottari balance is displaced by whatever fraction of the Moon's nakshatra an hour represented that day — here about 4%, or five months of a Venus mahadasa. None of these errors announces itself: the wrong chart is internally consistent, prints beautifully, and will agree with every other IST-forever engine, which is exactly how wrong answers achieve consensus. The only witnesses against it are the database — and any surviving detail the family remembers that is anchored to the sky rather than the clock: the birth star above all, "just before dawn", "the lamp was lit for sunset". Old memories of the sky outrank old readings of a clock that history had quietly moved.

11. Quick answers

How common are wartime-cohort charts in matching work today?

Directly, rarely — the cohort's own marriages are long past. Indirectly, constantly: elders' charts enter modern work as reference points — comparing a grandchild's chart "against thatha's", dasa-based life retrospectives at milestone birthdays, and the memorial recomputations families request. In all three uses the uncorrected hour quietly distorts the comparison, which is why we flag the 1941–45 windows automatically when such dates are entered, and why this article exists to be linked from that flag.

My father was born in March 1942 — which spell was that?

Per the database, the first spell ran to mid-May 1942, so a March 1942 birth is inside it: the clock was War Time, one hour ahead. Births from mid-May to end-August 1942 are the brief IST island between the spells.

Could the war hour explain a long-standing "the chart never quite fit" feeling?

Occasionally, yes — and it is one of the more satisfying resolutions in this work. A wartime-cohort chart whose lagna-based readings always felt slightly askew, while nakshatra-based ones rang true, matches the error signature exactly: the hour shifts the lagna often and the star rarely. Families who recompute and find the corrected lagna "was them all along" have not discovered new fate — they have removed an hour of bureaucratic noise from an old signal. We would caution equally against the reverse enthusiasm: a chart that always fit fine is weak evidence the record was clock-clean, given how much of a reading rests on the robust star. The comparison protocol, not the feeling, decides.

Did War Time apply to all of India?

It was promulgated for British India as a whole (princely-state practice could vary locally — one more reason the comparison protocol beats blind rules for individual cases). The IANA record models the subcontinent's standard practice.

Does this affect Pakistan/Bangladesh-side family charts too?

The wartime advance predates Partition, so yes — pre-1947 births across the subcontinent share the cohort, whatever the city's later zone became.

The family astrologer insists the old chart is fine. How do we discuss it without offence?

Lead with the star, not the software. Ask the astrologer to confirm the elder's janma nakshatra from the old chart against the family's living memory (the star everyone has always fasted by). If they match, ask — genuinely, as a student — whether the original computation used clock time or nazhigai-after-sunrise: a sunrise-anchored original is immune (Section 9) and the old chart stands vindicated, which is a happy outcome worth announcing. Only if the original was clock-based does the War Time question arise, and framing it as "the government moved the clocks in 1943 — did the old computation know?" makes it a question about colonial bureaucracy, not about anyone's competence. In our experience the astrologers most worth having are delighted by the question.

What about 1962/1965/1971?

Contrary to occasional rumour, the IANA record shows no clock advance for the later wars — IST has run unbroken since 16 October 1945. The 1940s cohort is the one that needs checking.