← All articles

True Solar Time vs. Clock Time: Why Your Birth Chart Could Be an Hour Off

A customer runs a chart for a birth in Corrèze, France — March 12, 1995, 12:03 pm. The form comes back with a correction: true solar time, 10:59 am. Sixty-three minutes earlier.

That looks like a bug. It's France.

The clock is a treaty, not a measurement

Noon, as a physical event, is the moment the sun crosses your local meridian. For most of human history, that was what clocks tracked — every town kept its own noon.

Railroads ended that. You cannot run a timetable across a country where every station disagrees about what time it is, so the world was carved into time zones: bands roughly 15 degrees of longitude wide, each pinned to a reference meridian. Inside a band, everyone agrees to share one clock — which means almost everyone inside the band lives slightly off their own sun.

Then politics moved the bands. France sits almost exactly on the Greenwich meridian; its sun agrees with London's. But since 1940 France has run on UTC+1 — Berlin's meridian, 15 degrees east. Spain, further west still, does the same. Western China is the extreme case: the whole country runs on Beijing time, so in Kashgar — 44 degrees of longitude from Beijing's reference meridian — the clock runs nearly three hours ahead of the sun.

None of this is hidden. It's just forgotten. The gap between your clock and your sun has two components:

1. Longitude offset. Four minutes for every degree between you and your zone's reference meridian. Fixed by geography and politics.
2. The equation of time. The Earth's orbit is elliptical and its axis is tilted, so the sun itself runs up to ~16 minutes fast or slow across the year. Fixed by astronomy.

Add them, and "12:03 on the clock in Corrèze" becomes "10:59 by the sun." No bug. Just a treaty you were born under.

How big does the gap get?

Real numbers, computed by our engine and cross-checked against independent astronomical solar-noon calculations:

A quarter of the planet's population lives under a clock that is more than an hour away from its sun for part of the year.

Daylight saving: the hour that gets recorded and forgotten

There's a third distortion, and it's the one that quietly corrupts birth data: daylight saving time. The time on a birth certificate is whatever the wall clock said — and if the birth happened in summer under DST, that recorded time is one hour ahead of the standard time for that zone, with nothing on the certificate saying so.

Two details most people miss:

• DST is historical, not current. Whether your birth time includes a DST hour depends on the law in force at that place on that date — not on whether the place uses DST today.
• China ran daylight saving from 1986 to 1991. Anyone born in a Chinese summer in those six years has a recorded birth time that is one hour ahead of Beijing standard time. Most of them have never been told.

Any serious chart engine has to resolve this from the full historical timezone database — place plus date, not place alone.

So which time does a chart want?

Here is where we give you the honest answer instead of the confident one.

The classical argument says: charts describe a relationship between a moment and the sky, so they should run on solar time — the sun's actual position — not on a political compromise. It's a coherent argument, and some schools insist on it.

Our position is empirical. We track how charts verify against the recorded lives of people with documented birth times, and in our tracked results, uncorrected civil clock time reads more accurately than solar-corrected time for most people. We don't fully know why. The working hypothesis: timing structure follows the time system you actually live by — the one that schedules your work, your meals, your society — not your geographic longitude. We are aware this is a hypothesis and we say so.

So DaoTiming's default is the clock time you were recorded under, taken as written. The solar correction exists as an option — off by default, there if you have a specific reason to use it — and when you turn it on, every layer of the correction, the historical DST hour included, is resolved and shown to you.

What the engine shows you before you pay

Because an invisible one-hour shift is exactly the kind of thing that should never be invisible, our chart intake runs a Time Check the moment you enter a birth place with the solar correction on:

• the resolved historical timezone for that place and date,
• whether daylight saving was in effect at that moment — and the standard time if it was,
• the computed true solar time, with the total shift in minutes against the time you entered.

The exact time your chart is computed from is printed on the screen before anything is submitted. We validated the computation against independent astronomical solar-noon data across the extreme cases — western Spain, Beijing-time Kashgar, Iceland, half-hour and quarter-hour zones, southern-hemisphere DST, even UTC+14 islands on the far side of the date line. If a time is going to be corrected, you see the correction.

Your clock is a treaty. Your chart deserves to know which treaty you were born under.

DaoTiming computes structure from time. If you want to see your own chart — computed, not curated — start with the Blueprint.

Wu, D. (July 7, 2026). True Solar Time vs. Clock Time: Why Your Birth Chart Could Be an Hour Off. DaoTiming. https://daotiming.com/articles/true-solar-time-vs-clock-time