True Solar Time: Why Your Birth Certificate Doesn't Say When You Were Born

Your birth certificate records a clock time. The clock was set by a government.

Those are two different facts, and a BaZi chart needs the second one translated into something the sun would recognise — because the hour pillar is a position in the solar day, not a position on a legal clock.

The gap between them has two causes. Most calculators correct for one and ignore the other, and the one they ignore is larger.

The first cause: longitude

Standard time zones are drawn to give large regions one convenient clock. Korea sets its clock to the 135th meridian, which runs through the Sea of Japan — east of the entire country.

So every Korean city runs ahead of its own sun, and by a different amount:

Nine minutes separate Busan from Incheon. Both are Korea, both are on the same clock, and their suns are nine minutes apart.

This is why a calculator that asks for a country rather than a city has already given up. One national figure is right somewhere in the middle and progressively wrong toward both edges — and since the hour branch is a two-hour window, a birth in the first half hour of one lands in the previous window once the correction is applied. For Seoul that is one birth in four.

The second cause: the law moved

Here is the part almost nothing handles.

The correction above assumes Korea's clock is set to 135°E. Today it is. It has not always been.

Korea moved its standard meridian twice. And on top of that, daylight saving ran in three separate stretches — the late 1940s and early 1950s, the second half of the 1950s, and 1987 to 1988.

So "Seoul is thirty-two minutes behind" is a statement about the present, not about Korea.

For a birth between 1954 and 1961, the standard meridian was 127°30′E — which Seoul sits almost exactly on. The longitude correction for those years is about two minutes, not thirty-two. A calculator that applies its modern figure to a 1958 birth is not failing to correct. It is introducing a half-hour error while believing it is removing one.

And if that birth also fell in summer, daylight saving adds an hour on top.

Two births, worked

These are real outputs from this site's engine, before and after it learned about historical offsets.

15 June 1958, 10:00, Seoul. Meridian at 127°30′E, and summer time in force.

modern offset only   −30 min   →  hour pillar 丁巳
correct for 1958     −62 min   →  hour pillar 丙辰

15 July 1988, 10:00, Seoul. Meridian back at 135°E, and summer time in force again.

modern offset only   −30 min   →  hour pillar 癸巳
correct for 1988     −92 min   →  hour pillar 壬辰

Different stem, different branch. Which means different hidden stems, different Ten Gods, a different twelfth of the chart — and everything the hour palace is read for.

Across a large sample of Korean births, correcting for the historical offsets moves the hour pillar for about one birth in seven. In the 1987–88 window it is closer to three in ten.

And a smaller number move further than that: roughly 3% cross into an adjacent calendar day once corrected, which changes the day pillar — the day master itself, the character the whole chart is read from.

What this site does, and what it doesn't

Being specific here matters more than being impressive.

It corrects by city, from stored coordinates, for 194 cities. Not by country.

It handles Korea's history in full — all four meridian periods and the daylight saving windows, with exact transition dates rather than approximate months.

It handles US daylight saving from the rule sets that actually applied: 1918, then the changes in 1967, 1976, 1987 and 2007, with Arizona and Hawaii correctly opting out.

It does not handle 1945 to 1966 in the United States. During those years daylight saving was local option — neighbouring towns could and did differ — and there is no national rule to apply. The engine marks those births as unhandled rather than inventing one.

And for most other countries it applies the modern offset to all dates. Japan had daylight saving under the occupation. China unified to UTC+8 in 1949. Hong Kong ran daylight saving across most of four decades. Europe only harmonised in 1996. The engine does not yet know any of that, and it says so rather than presenting a number as though it did.

That last paragraph is the one worth taking seriously if you are reading this to evaluate a calculator. A site that handles none of this looks exactly like a site that handles all of it — both print a number. The difference is whether the number is right, and you cannot tell from looking.

What to check

Four questions, in descending order of how much they reveal.

Does it ask for a city, or a country? A country-level correction is a decision that longitude doesn't matter much, made silently.

Does the correction change when you change the birth year? Enter the same city and time for 1958 and for 1998. If the correction is identical, the calculator is applying a modern offset to history.

Does it say what it doesn't know? A calculator confident about every birth anywhere is either extraordinary or not checking.

Does it tell you when you're near a boundary? A birth close to a two-hour edge is one where any refinement moves the pillar. That is worth knowing before you read anything into the hour.