Case 10 of 26
Historical time zones
Singapore: no daylight-saving adjustment
A stable UTC+08:00 zone separates longitude correction from DST.
Boundary question
Does the receipt avoid inventing DST where none applies?
Yes. The DST component is zero; longitude and Equation of Time still move noon to 10:55.
Synthetic input
Recorded facts
- Date
- 1990-06-15
- Recorded time
- 12:00
- Location
- Singapore
- Time zone
- Asia/Singapore
- Longitude
- 103.8198°
- Gender input
- Male
Pinned expected facts
Verified output
Year
庚午
Month
壬午
Day
辛亥
Hour
癸巳
- Day Master
- 辛
- True solar time
- 1990-06-15 10:55
- Total correction
- -64.75 minutes
- Historical offset
- UTC+08:00 · DST 0 min
- Luck direction
- 顺排
- Reference Jie
- 小暑 · 1990-07-07 17:00:28
- Luck start
- 1997-11-15 21:21:15
Reading the boundary
What this case means for your own chart
This case uses the same date and time as the Beijing and Chicago cases but places the birth in Singapore, which has never used daylight saving. The DST component is zero, and yet the noon clock reading still corrects to 10:55 true solar time.
That is the useful lesson. A reader who has learned that timezone correction means daylight saving may conclude that a Singapore record needs no correction at all. It needs sixty-five minutes of correction, entirely from longitude and the Equation of Time.
Singapore sits well east of the meridian its clocks were set to, so the sun runs ahead of the clock by a substantial margin. The same is true of anywhere far from its standard meridian, including large parts of western China, Spain, and Argentina. The clock and the sun are not the same instrument.
The size of that gap is easy to underestimate because it is invisible in daily life. Nobody notices that noon on the clock is not noon in the sky; the convention simply shifts when people eat lunch. It only becomes visible when a calculation depends on the sun's actual position, which is precisely what the hour pillar does.
The practical version of this is simple. If both your birth place and your birth time are recorded, the correction can be computed from them. If either one is missing, it cannot be computed at all, and no amount of care with the other will recover it. That asymmetry is why this site asks for a location alongside a time rather than treating the time as sufficient on its own.
Check your own record
- Do not skip the correction just because your birth place has no daylight-saving history. Longitude still applies.
- Compare your birth city's longitude against the standard meridian of its timezone to estimate the direction and rough size of the correction.
- If your birth city sits far from its timezone's standard meridian, expect the correction to be large enough to move an hour pillar.
Which convention is in play
- Calculation fact
- The pinned engine records a zero DST component for this input and still corrects noon to 10:55 through longitude and the Equation of Time.
- Convention
- The decision to correct to true solar time at all is a convention choice. Some practitioners work from standard time and treat the correction as optional; this engine states that it applies it.
- Our explanation
- Grouping this case with the DST cases is our choice, made because readers conflate the timezone correction with the daylight-saving correction.
Related reading
Conventions and limits
What this case does — and does not — prove
It verifies
Deterministic reproduction of this input under the named engine version and conventions. A pinned-field mismatch stops the production build.
It does not claim
Universal agreement across Bazi schools, interpretation of a real person, or certainty where the historical record is incomplete.
tyme4ts 1.5.2 · sect 2 day boundary · BaziCalculator.ai NOAA/IANA true-solar adapter
calculation-benchmarks-v1 · reviewed 2026-09-05