The Hour Daylight Saving Time Stole: How We Restored True Birth Times Across 123 Countries and Regions

Why a birth chart needs the real time

Traditional Chinese astrology determines the hour pillar from the sun's position: when the sun crosses your local meridian, that is the midpoint of the Horse hour. This is called true solar time. But the time on your birth certificate is separated from the sun by three layers of human convention:

Layer one: time zones. Everyone in a zone shares one clock. Beijing and Ürümqi both use Beijing time, yet when clocks in Ürümqi strike noon, the sun is still far to the southeast — more than two hours away.

Layer two: daylight saving time. Many countries set clocks forward in summer. Birth records show the shifted time, not solar time. The United States, all of Europe, Australia and much of South America still observe it; many more countries did historically and then abolished it.

Layer three: historical time regime changes. This is the most hidden layer. The standard time of the same city could be entirely different in 1970 versus 1990 — countries change zones, move standard meridians, and run temporary experiments. None of this is written on any birth certificate.

If a calculator uses the raw clock time, all three distortions stack into your hour pillar. Our true solar time engine restores time in strict order: roll back daylight saving first, then correct for the difference between the birthplace longitude and the legal standard meridian of that place at that moment in history, and finally apply the astronomical equation of time.

From six years in China to 123 countries worldwide

This project began with our earlier work on China's 1986-1991 daylight saving time. During those six years, the birth times of roughly 36 million newborns were recorded one hour fast — and most of them never knew. Solving it established a principle we have never changed: the original record never changes; corrections happen only at calculation time. The birth time you enter is always stored and displayed exactly as you entered it.

But China was only the beginning. As our international audience grew, we found the same problem everywhere — and far messier: the US spans six time zones with state-level DST quirks; every European country has different historical DST dates; the post-Soviet states changed regimes repeatedly around the dissolution; southern-hemisphere DST straddles New Year.

We prioritized by real user distribution and shipped six waves of expansion: first the United States; then Indonesia, Australia and Canada; then the major European countries; then a second batch including Ukraine, Israel, Iran and Egypt; and finally a third batch of 51 countries and regions across Latin America, Central Asia, the Middle East and Africa. As of today, all 123 country and region codes are live, 97 of them computed dynamically from the birthplace time zone, covering more than 99.9% of users with recorded birthplaces.

Standing on the shoulders of the IANA time zone database

Reconstructing every time change in every region since 1950 by hand would be impossible. Fortunately, the world keeps a shared answer: the IANA time zone database (the tz database) — maintained by volunteers for decades and used by every operating system and every piece of Internet infrastructure. When your phone silently shows the right time after you land in another country, that is the tz database at work.

But using an authoritative database is not the same as being accurate. The database tells you what the clock offset was at a given place and time. A birth chart needs the answer to a subtler question: how much of that offset was daylight saving that should be rolled back, and how much was legal standard time that should be kept? For most of history the answer is obvious — but the edges are full of traps. We verified the original tz database archives line by line and encoded the correct legal standard for 38 historical windows across 16 zone groups.

Time history is wilder than you think

Every story below corresponds to a real rule in our system.

Morocco: every Ramadan, the clocks go backward. Since 2018 Morocco stays on summer time all year — except during Ramadan, when the whole country sets clocks back one hour. It is the only country on Earth that pauses fast time for a month every year. Because Ramadan follows the Islamic calendar, the window shifts about 11 days earlier each year. Births inside and outside Ramadan need entirely different corrections.

Salta, Argentina, October 20, 1991: two hours in one night — but only one was daylight saving. That night, clocks in Salta Province jumped from UTC-4 straight to UTC-2. Intuition says two hours of DST; even our own automated validation initially thought so. Line-by-line verification of the tz database archives revealed the truth: the government did two things at the same instant — raised standard time from UTC-4 to UTC-3 and started one hour of daylight saving. The size of the clock jump is not the size of the daylight saving. Subtracting two hours would push the chart wrong in the other direction. This case is now written into our internal validation standards: every subtraction amount must be confirmed against the original archives.

Britain and Ireland, 1968-1971: three winters without falling back. Both countries ran a three-year experiment of permanent UTC+1, and the law defined it as standard time — not daylight saving. Births in those winters need no adjustment at all. Treating it as DST and subtracting an hour is one of the most common mistakes in international chart calculators.

The Soviet Union, 1991: the last summer time of an era. On March 31, 1991, the dissolving USSR performed a textbook-grade maneuver: it lowered standard time by one hour and entered daylight saving simultaneously — wall clocks never moved, but the legal meaning of every hour that summer changed. From Almaty to Minsk, from Tbilisi to Tashkent, we restored the legal standard for each of ten republics that summer.

Georgia, midsummer 2004: the standard changed silently. On June 27, Georgia moved its standard time from UTC+4 to UTC+3 while wall clocks never moved — daylight saving quietly took over that hour until the end of October. Births that summer need a one-hour correction, yet generic detection rules miss it, because the lower offset only appears after the birth, never before.

Syria and Jordan, autumn 2022: the day summer time became permanent. Both countries announced they would stop falling back. The summer of 2022 became their last real daylight saving season — children born after need no correction, while those born that summer still do.

The Dominican Republic, 1970s: half-hour daylight saving. Yes — clocks went forward 30 minutes, not 60. The world also has Nepal at UTC+5:45, the Chatham Islands at a 45-minute offset, and Venezuela on UTC-4:30 from 2007 to 2016. Our engine works in minutes and assumes nothing about whole hours.

Kazakhstan, 2024: one country, one time zone. Spanning nearly 3,000 kilometers, Kazakhstan unified to UTC+5 on March 1, 2024. Births before and after differ by 15 degrees of standard meridian — a full hour of the hour-pillar baseline.

Aysén, Chile, 2025: the world's youngest time zone. When Chile's southern Aysén region stopped switching to winter time, the IANA database created a brand-new zone for it. We supported it within months of its creation — including its entire history from before it became a separate zone.

Nearly fifty thousand checks: how we confirm accuracy

For an astrology product, accuracy is existential. Our definition of the word is testable:

Layer one: independently derived tests. Every supported country has test cases whose expected values are derived independently from timezone history archives — not copied from the system output. The two must agree. These now number in the hundreds, including non-whole-hour cases like the Dominican 30 minutes and Nepal's 45.

Layer two: month-by-month validation, 1950-2026. For every supported DST zone, we cross-checked every single month from 1950 through 2026 against the authoritative data — nearly fifty thousand sample points, in both directions: never missing a real daylight saving period, and never mistaking legal standard time for daylight saving. This layer caught three of our own mistakes, including one that no ordinary test would ever find: Costa Rica observed four short DST periods in 1979, 1980, 1991 and 1992, each lasting only a few months — all of which fell exactly between the usual spot-check dates.

Layer three: independent reviewers attacking each other's conclusions. Before launch, the rules survived rounds of challenges from multiple independent review perspectives, including AI review systems. The process produced seven challenges: five were real problems, each fixed — the Salta two-hour story came from exactly this process; two were false alarms, refuted with archival evidence. We wrote the whole exchange into our internal engineering records, because it proves a point: no single validation method is infallible; accuracy comes from independent perspectives cross-checking one another.

Two principles we will not compromise

One: the original record never changes. All corrections happen at calculation time. You enter 2:00 PM, the system forever displays 2:00 PM, and the restoration happens behind the scenes only when casting the chart. Your birth time is yours; we just work out where the sun was.

Two: respect de facto standards. Some permanent summer times lasted so long that they became the lived standard of a generation — Argentina ran one hour fast continuously from 1946 to 1963, seventeen years in which an entire generation was born, went to school and lived. For such periods we adopt the same philosophy the IANA database applies to Britain's 1968-71 experiment: treat it as de facto standard time and make no subtraction. Time systems exist to serve people; so does chart calculation.

Who should take a second look at their hour pillar

If you or someone you care about fits any of these, the recorded birth time was likely shaped by a time regime:

• Born in the United States, Canada, or any European country between March and November (daylight saving season);
• Born in mainland China between April and September, 1986-1991;
• Born in a former Soviet republic (Russia, Ukraine, Kazakhstan, Georgia and others) in the summers of 1981-1991;
• Born in Morocco after 2019 (outside Ramadan);
• Born in Argentina, Chile, Brazil or Uruguay between October and March (southern-hemisphere DST);
• Born in Britain or Ireland, 1968-1971 — good news: your time needs no adjustment, but it is worth confirming your calculator is not "helpfully" subtracting an hour anyway.

Pick your birth city when casting a chart on FateMaster.AI, and leave the rest to us: time zones, daylight saving, and historical time regimes are handled automatically and precisely. Your hour pillar deserves to stand on the true position of the sun.