International birth data guide
BaZi birth time, time zones, and daylight saving explained
BaZi birth time should begin with the local date and clock time recorded where the birth happened. If you were born in New York, Toronto, London, Sydney, or another city outside Korea, do not first convert the time to Seoul, Beijing, or UTC. The calculator needs the birthplace so it can interpret that local record under the correct historical rules.
This matters because a city can change its UTC offset across the year and across history. Daylight saving can also create a repeated hour in autumn or skip an hour in spring. A careful calculator resolves those facts before it decides the hour pillar, solar-term boundary, rising sign, or houses.
At a glance
- Enter the local time written on the birth record, not a time you converted yourself.
- Select the actual birth city because time-zone history and longitude both matter.
- A repeated daylight-saving hour may require one more piece of evidence.
- Near an hour or solar-term boundary, small input changes deserve explicit review.
Start with the clock time at the birthplace
Suppose a birth certificate says 8:20 p.m. in Vancouver. Enter 20:20 and Vancouver. Do not add the difference from Korea, and do not use the time shown on a relative’s phone in another country. The city and date let the system map the recorded local time to the correct instant.
The same rule applies when a family later moved. Use the place where the birth occurred, not the city where the person grew up or lives now. If the record lists only a hospital or county, choose the closest available city in the same time-zone area and keep that approximation in mind.
Why a fixed UTC offset is not enough
A label such as “Eastern Time” does not always mean UTC−5. New York and Toronto commonly use UTC−5 in standard time and UTC−4 during daylight saving, while the exact transition rules have changed historically. London, Sydney, and other cities have their own histories. A current offset copied from a search result may therefore be wrong for the year and date of birth.
Hongsimdang uses an IANA city time zone with the birth date and local clock time. This preserves historical offset and daylight-saving context instead of applying today’s offset to every year. It also keeps half-hour offsets, such as Adelaide, rather than rounding them to a whole hour.
What happens during daylight-saving changes
When clocks move forward, some local times never occur. When clocks move back, one block of local time occurs twice. For example, “1:30 a.m.” on an autumn transition day can refer to two different instants with different UTC offsets. A calculator should not silently choose one.
If Hongsimdang finds a repeated time, it asks you to select the matching occurrence. Check whether the record includes a UTC offset, standard/daylight abbreviation, or another timestamp. If no evidence survives, mark the uncertainty rather than choosing the version that produces the preferred interpretation.
- Spring gap: verify the written time because the selected local time did not exist.
- Autumn overlap: confirm whether the first or second occurrence was recorded.
- No DST region: the historical city zone still matters and should be selected.
- Approximate record: keep the hour-based conclusion conditional.
Clock time and local solar time are different steps
Civil time follows a time zone shared across a wide region. The Sun does not cross the local meridian at exactly the same clock minute in every city in that zone. Some Four Pillars methods therefore adjust the hour-pillar calculation by longitude after the correct civil time and historical offset have been established.
This is one reason two calculators can disagree near a two-hour branch boundary. They may use different city coordinates, time-zone data, solar-time conventions, or late-night day-boundary rules. Compare the inputs and published convention before treating either chart as unquestionably correct.
When the exact minute deserves extra attention
Most recorded times are comfortably inside one hour branch and one calendar boundary. Extra care is useful near midnight, near the edge of a two-hour branch, on a daylight-saving transition, or close to a solar-term change. A small clerical or remembered-time error can matter more in those cases than it does in the middle of a stable interval.
Run the recorded time first. If the time is approximate, compare the plausible range and note which parts stay the same. Stable conclusions are more useful than a dramatic claim that appears only under one uncertain minute.
Questions people ask
Frequently asked questions
Should I convert my overseas birth time to Korean or Chinese time?
No. Enter the local date and clock time at the birthplace, then select the birth city. The calculator applies the location and historical time-zone context.
Does daylight saving time change a BaZi chart?
It can change the instant represented by a local clock time and may affect an hour or solar-term boundary. Historical rules should be applied for the birth city and date rather than guessed from the current offset.
Why do two BaZi calculators show different hour pillars?
They may use different time zones, daylight-saving data, longitude adjustments, true- or mean-solar-time conventions, or day-boundary rules. Compare those settings before comparing interpretations.
What if my recorded time is only approximate?
Use the recorded estimate, disclose that it is approximate, and compare nearby plausible hours. Do not present hour-based details as exact if the source time is uncertain.
Localize the birth record before interpreting the chart
International birth data is not a reason to guess or convert the time by hand. A city, local record time, and historical rule set provide a traceable starting point for the calculation.
Once the input is sound, keep interpretation proportional to its certainty. The chart can organize questions, but it should not hide uncertainty behind a precise-looking timestamp.