Dina and Hora Bala: Sunrise Weekdays, Unequal Hours and Worked Ledgers

How are Dina and Hora Bala calculated?

In Astrogyana's parashari-motion-shadbala-2026.2 profile, the lord of the sunrise-based weekday receives 45 Virupas of Dina Bala. The lord of the current planetary hour receives 60 Virupas of Hora Bala. Daylight and night are each divided into twelve equal parts, so a planetary hour need not last sixty minutes.

If one planet holds both roles, it receives 105 Virupas from these two components. Otherwise the 45 and 60 belong to different planets. These are two contributions within Kala Bala, not the complete Shadbala score and not a probability of success. This guide explains the named calculation convention; interpretations of planetary strength belong to the Jyotish tradition.

The examples below are constructed time schedules. They do not report the actual sunrise of a named city, and the chosen date merely supplies a verifiable weekday. Keep that distinction when reproducing the arithmetic with a calculator.

Start with the sunrise that anchors the day

For a birth instant t, identify a sunrise R, the following sunset S and the next sunrise R₂. The required inequalities are R ≤ t < R₂ and R < S < R₂. The traditional day in this calculation runs from the first sunrise up to, but excluding, the next. Its lord comes from the local weekday of R.

A birth at 02:00 on a civil Tuesday can therefore belong to Monday's sunrise day. The weekday on a calendar and the Dina Bala day answer different questions. Neither should silently replace the other. At Tuesday's actual sunrise, the new sunrise day begins and Mars becomes its day lord.

Astrogyana's Kundli builder converts the solar-event timestamps into the birth location's time zone before this selection. This matters because the same sunrise instant may fall on a different UTC date. A UTC weekday extracted without the location's calendar context can select the wrong planet.

The planetary-hour sequence

The repeating order is Saturn → Jupiter → Mars → Sun → Venus → Mercury → Moon → Saturn. Begin at the weekday lord for the first daylight hora. Continue through all twelve daylight slots and then all twelve nighttime slots. Sunset changes the slot length; it does not restart the planetary sequence.

For Monday, start at Moon. Its first seven horas are Moon, Saturn, Jupiter, Mars, Sun, Venus and Mercury; the eighth returns to Moon. These are ordinal slots. Number 7 means the seventh interval after sunrise, not seven o'clock on the civil clock.

Twenty-four advances in the seven-planet cycle have the same remainder as three advances. Consequently the first slot of the following sunrise day moves from Monday's Moon to Tuesday's Mars. This offers a useful consistency check across every weekday, without requiring an astronomical prediction.

Calculate the interval before assigning the planet

During daylight, set A=R and B=S. During night, set A=S and B=R₂. Using elapsed seconds on one time scale, calculate f=(t−A)/(B−A). The zero-based position within that half is floor(12f), from 0 through 11. Add 12 during night to obtain the overall zero-based index j.

If w is the weekday lord's position in the sequence beginning with Saturn at zero, the current lord is the entry at (w+j) mod 7. For display, the hora number is j+1. Separate these two index systems: the planet list wraps after seven entries, while the day's hora numbering continues to twenty-four.

Each interval includes its starting instant and excludes its ending instant. An exact boundary belongs to the interval beginning there. At sunset use the first night slot. At the next sunrise discard the old cycle and start the new one. Do not classify an instant using a rounded display time if its underlying timestamp has greater precision.

A complete Monday with 65-minute dayside horas

Assume Monday, 26 October 2026 has sunrise at 05:30, sunset at 18:30, and the following sunrise at 05:30 on Tuesday, all at a fixed +05:30 offset. The next day's sunset is also supplied as 18:30 when testing the following cycle. These are synthetic inputs, not an ephemeris.

Daylight is thirteen hours: 780/12=65 minutes per hora. Night is eleven hours: 660/12=55 minutes per hora. The full table retains all twenty-four slots so that the sequence through midnight can be checked rather than inferred from an abbreviated list.

The slot starting at noon belongs to Mercury. The first nighttime slot belongs to Venus. The midnight slot belongs to Sun even though the day lord remains Moon. These three checkpoints catch common mistakes involving fixed clock hours, a restarted sunset sequence, or a premature weekday rollover.

Check the exact transitions

The following probes use the same fixed offset and constructed solar events. A one-second change at a boundary can change Hora Bala, while Dina Bala remains attached to the anchoring sunrise. The last row belongs to Tuesday's new cycle, for which its sunset and Wednesday's sunrise must be available.

Do not label midnight as a special planetary-hour boundary in every chart. It happens to coincide with one in this deliberately simple fixture. With different sunset and next-sunrise times, midnight may fall inside a hora. Conversely, a hora boundary need not coincide with any whole civil hour.

Build the strength ledger before adding other components

At Monday 12:10, the time lies in the seventh hora, from 12:00 to 13:05. Moon receives the day contribution and Mercury the hour contribution. Record all seven planets, including zeros, so that absent components are not mistaken for missing data.

The two-column total across planets is 105 Virupas, or 1.75 Rupas. This is a conservation check on these allocations, not a target score for an individual planet. At Monday 05:30 both roles belong to Moon, giving it 45+60=105, while the other planets receive zero from these two components.

The day contribution stays at 45 throughout its sunrise cycle; it does not accumulate every hora. Likewise 60 is assigned for the active hora, not multiplied by the number of elapsed horas. The remaining Kala Bala components and the other five Shadbala groups must be calculated separately before interpreting a complete report.

Why another calculator may show a different hour lord

The Maitreya documentation describes alternative conventions: twenty-four equal divisions of the whole sunrise-to-sunrise span, or fixed hours beginning at 06:00. Astrogyana's named profile uses twelve parts of daylight and twelve of night. An identical timestamp can occupy different intervals under those methods.

For the fixed-06:00 comparison, the first slot has been explicitly anchored to Monday's lord. It is a hypothetical comparison, not a statement about another product's defaults. Agreement on one timestamp does not establish agreement between methods: two schedules may coincide temporarily and diverge later.

When comparing reports, save the chosen convention, solar events, offset and exact instant. Compare the interval first, then the planetary sequence, then the assigned strength. A final numerical disagreement is easier to diagnose when each intermediate choice is visible.

Time zones, midnight and changing clock offsets

Monday 05:30 at +05:30 is Monday 00:00 UTC. A Monday 05:00 sunrise at the same offset would instead be Sunday 23:30 UTC. That second example demonstrates why converting the sunrise to UTC and then reading its weekday loses the local calendar information needed for Dina Bala.

For the main fixture, Monday 12:10 at +05:30 equals 06:40 UTC. Passing either representation of the same birth instant must locate the same hora when the solar events retain their correct local context. Changing the displayed time zone alone must not turn one instant into a new birth time.

If the local offset changes between sunset and sunrise, subtract absolute timestamps rather than clock labels. A displayed interval crossing a clock change can contain a different number of elapsed seconds than its wall-clock appearance suggests. The hypothetical schedule above has no offset change; do not extend its 55-minute night slots to a date that does.

Missing events and uncertain birth times

The existing implementation requires a valid sunset between two consecutive local-date sunrises. It filters supplied day records that lack a sunrise or sunset, so the next date's record must also be complete for its sunrise to serve as the endpoint. Missing or invalid inputs produce unavailable Shadbala, not seven zero-strength planets.

Where a location has no required rise or set event, this profile does not substitute a fictional 06:00/18:00 day. Preserve the unavailable result and inspect the event data. A different polar-region convention would need to be named separately rather than silently introduced.

A recorded birth range of 06:33–06:37 in the Monday fixture crosses the first boundary. Moon remains the day lord, while the hour lord may be Moon or Saturn. Describe both possible ledgers. An average of the two allocations would be a new model, not the original discrete rule.

A reproducible reading workflow

1. Resolve the location, date and birth-time offset.
2. Record the anchoring sunrise, following sunset and next sunrise in local calendar context.
3. Check that the instant belongs to the selected cycle.
4. Choose daylight or night and calculate its elapsed fraction.
5. Determine the zero-based slot, then advance through the planetary sequence.
6. Assign 45 and 60 in separate columns, allowing both to belong to one planet.
7. Check the 105-Virupa allocation total before adding other strengths.

The introductory Hora table guide explains reading the schedule itself. This companion guide uses that schedule to audit the two Shadbala allocations and their subtotal.

Continue with Tribhaga Bala to compare three-part time divisions, and Natonnata Bala for a different calculation based on local mean solar time. They share a broad temporal theme but must not reuse each other's interval formulas.

The Rupas and Virupas guide explains reporting units. The Yuddha Bala ledger shows how other temporal contributions can enter a later adjustment. Keep the calculation layer distinct from claims about a person's future.

Frequently asked questions