Most calculators got your birth time wrong before they got your chart wrong.
The day-pillar debate gets a lot of attention, and I understand why — 23:00 to 24:00 is genuinely ambiguous, and the camps have been arguing about it for decades. But there's a quieter error that changes the chart more often, and it happens before anyone argues about anything.
The hour pillar is decided by a wall clock, and wall clocks don't agree with the sun.
Two corrections apply, and most tools do only the first one:
- Longitude. Local solar time runs ahead of or behind your timezone's standard meridian. It's usually under an hour, but an hour is a whole branch.
- Which country's rules were in force that year. This is the one that gets skipped.
Case that keeps producing wrong charts: 1990-06-15, 12:00, Kuala Lumpur. True solar time puts it at 10:46. Now Beijing, same instant — 10:45, and Beijing was on DST in June 1990, so the recorded clock time has to be pulled back an hour before any of this applies. Same UTC+8, same date, different hour pillar.
Worse case: tz == 8 tells you nothing. It covers Beijing, Taipei, Kuala Lumpur, Singapore, Manila, Perth, and parts of Indonesia and Australia. In 1990 one of those had summer time and most didn't. Infer the rule from the offset and you get the wrong answer with high confidence, which is the worst kind.
I'll say what I don't know. I don't think the longitude correction is universally applied correctly either, and the day-boundary argument is still genuinely open — I'm not going to pretend otherwise. But if your hour pillar shifted when you "corrected for true solar time," check which timezone rule got applied before you accept the correction. A correction applied with the wrong rule is worse than none.
This is maintained as geography data rather than a timezone list — 19 countries, 190 provinces, 663 cities — because the answer is "which city, which date," not "which offset."
Curious whether anyone else here has hit the same city-year and gotten a different hour pillar.