BaZi Calculation · DST · Solar Time

How to Calculate BaZi in a Daylight Saving Time Zone

Preserve the recorded civil time, identify the historical timezone rule, remove any daylight-saving offset, and apply solar-time correction only when your chosen BaZi method requires it.

Follow the Calculation Workflow Open the Day Master Calculator

Record first. Convert once. Preserve every assumption.

Start with method

DST is one correction—not the whole calculation

A birth certificate records civil time. A charting method may use that civil time, standard time, local mean solar time, or local apparent solar time.

Different BaZi lineages and software make different time conventions. Precision begins by stating the convention instead of silently mixing methods. DST affects the clock offset; longitude affects local mean solar time; the equation of time affects apparent solar time.

DST is historicalRules vary by place, date, war, legislation, and political change.

Offsets are not always one hourSome jurisdictions used half-hour, two-hour, double-summer, or irregular changes.

Longitude has a directionLocations east of a zone meridian are ahead in local mean solar time; west are behind.

Near boundaries, compareA few minutes matter only when they cross a Day or Hour Pillar rule used by the method.

Separate the clocks

Four time standards that must not be confused

01 · RECORDED CIVIL TIME

What the document says

The local wall-clock time, including whatever legal timezone and DST rule applied at birth.

02 · LOCAL STANDARD TIME

DST removed

Civil time after subtracting the daylight-saving component while retaining the legal standard UTC offset.

03 · LOCAL MEAN SOLAR TIME

Longitude corrected

Standard time shifted by approximately four minutes for each longitude degree from the zone’s standard meridian.

04 · LOCAL APPARENT SOLAR TIME

Sun-dial time

Local mean solar time adjusted by the equation of time, which varies through the year.

05 · UTC INSTANT

Universal reference

The unambiguous moment obtained from local civil time and its verified historical UTC offset.

06 · BAZI CONVENTION

The rule you choose

The charting school’s decision about civil, standard, mean-solar, or apparent-solar time and the day boundary.

Local mean solar time = local standard time + 4 minutes × (birth longitude − standard-meridian longitude)

Use signed longitudes consistently: east positive, west negative. A positive result adds minutes; a negative result subtracts them. For apparent solar time, then add the equation-of-time value produced by a reliable astronomical calculation for that date and place.

Auditable workflow

Calculate without losing the original data

Keep a small calculation record so another practitioner—or future you—can reproduce the chart.

STEP 01

Preserve the source record

Write the birth date, recorded time, exact locality, source type, time precision, and any uncertainty. Never overwrite this value with a corrected one.

STEP 02

Identify the historical timezone

Use an IANA timezone identifier such as Europe/London or America/New_York—not a fixed abbreviation such as EST, which can be ambiguous.

STEP 03

Verify the legal offset at birth

Check whether DST or another civil-time adjustment was active on that exact date. Historical government records or a maintained timezone database are preferred.

STEP 04

Convert to standard time if required

Subtract only the DST component. Example: UTC−4 daylight time becomes UTC−5 standard time by subtracting one hour.

STEP 05

Apply the chosen solar correction

If the lineage uses local mean solar time, correct for longitude. If it uses apparent solar time, also apply the date-specific equation of time.

STEP 06

Declare the day-boundary rule

Record whether the charting method changes the BaZi day at 23:00, 00:00, or another rule. Do not switch conventions after seeing the result.

STEP 07

Generate and compare the chart

Calculate from one clearly labelled input convention. If a correction crosses a boundary, retain both variants for structured comparison.

STEP 08

Save the audit trail

Store source time, timezone ID, UTC offset, DST adjustment, coordinates, longitude correction, equation-of-time value, method, and final input.

Worked illustration

New York: why the correction direction matters

This example demonstrates local mean solar time only. Exact historical offset and any equation-of-time value must be verified for the actual birth date.

Illustrative inputs

Recorded civil time: 06:30
DST component: +1 hour
Local standard time: 05:30
Standard meridian for UTC−5: 75°W (−75°)
New York longitude: approximately 74°W (−74°)

Longitude calculation

(−74) − (−75) = +1 degree

+1 × 4 minutes = +4 minutes

Local mean solar time is therefore approximately 05:34, not 05:26. New York lies east of the −75° standard meridian, so its mean Sun time is ahead of that meridian.

If the method requires local apparent solar time, the date-specific equation of time must then be added. Do not invent a fixed value.

Why this matters: a time correction changes the Hour Branch only when the final time crosses the applicable two-hour boundary. It can change the Day Pillar only when the chosen day-boundary rule is crossed. It does not automatically change the Spouse Palace, which is the Day Branch.

When precision changes the chart

Prioritise genuine boundary cases

Boundary	What may change	What to retain	Best response
Hour Branch boundary	Hour Branch and therefore Hour Stem.	Both corrected times and both Hour Pillars.	Compare variants without forcing biography to fit either chart.
BaZi day boundary	Day Pillar, Day Master, Hour Stem derivation, and downstream relationships.	School rule, corrected time, and both candidate days.	Escalate carefully; this is materially more consequential than an Hour-only change.
Solar-term boundary	Month Pillar or Year Pillar depending on the term and method.	Exact solar-term instant, UTC conversion, locality, and software source.	Use astronomical term timing rather than a calendar-date shortcut.
Ambiguous civil clock	The same local clock time may occur twice when DST ends.	Offset, fold occurrence, hospital record, and any corroborating documentation.	Calculate both instants if the occurrence cannot be established.
Nonexistent civil clock	Some local times never occurred when clocks advanced.	Original record and historical transition details.	Investigate transcription, recording convention, or institutional practice.

Avoid these failures

Common calculation errors

Always subtracting one hour

DST was not universal, and historical shifts were not always exactly one hour.

Using today’s timezone rules

A city’s current offset does not prove what applied in the year of birth.

Reversing longitude correction

East of the standard meridian means local mean solar time is ahead; west means behind.

Calling mean solar time “true solar time”

Apparent solar time also requires the equation of time; longitude correction alone is incomplete.

Double-correcting software input

Do not manually subtract DST if the calculator already converts location, date, timezone, and DST internally.

Changing schools mid-calculation

Civil-time, solar-time, and day-boundary conventions cannot be mixed opportunistically.

Claiming the whole chart is wrong

An Hour boundary usually changes the Hour Pillar—not automatically the Day Master, Day Branch, Month, or Year.

Rectifying by vague resemblance

Biographical “fit” is vulnerable to confirmation bias. Preserve uncertainty instead of manufacturing precision.

Luck Pillar start age: methods vary by direction rule and by how the interval to a solar term is converted. Birth time can affect the fractional interval, but DST correction does not automatically produce a different whole starting age. Document the calculation convention.

Fix the timestamp before interpreting the chart.

Preserve the civil record, verify the historical offset, declare the time convention, and compare variants only where a real boundary is crossed.

Return to the BaZi Hub