Ashtakavarga Reductions: Trikona, Ekadhipatya and a Complete Pinda Worksheet

What changes when an Ashtakavarga table is reduced?

Trikona Shodhana subtracts the smallest value within each of four sign trines. Ekadhipatya Shodhana then applies occupancy rules to the five pairs of signs sharing a planetary lord. Rashi Pinda and Graha Pinda are weighted sums of that reduced row; their sum is Shodhya Pinda. Each planetary Bhinna table is processed separately.

Astrogyana's current profile, parasara-ashtakavarga-2026.2, retains the original Bhinna, Sarva and Prastara tables alongside these reductions. The worked Sun example below gives 41 + 20 = 61. It is a reproducible calculation within a traditional astrological method, not a measured probability of an event or a scientific validation of prediction.

Start with the Ashtakavarga introduction if Bhinna and Sarva are unfamiliar. This guide concentrates on the transformation of numbers, including the awkward cases where a zero or an equal pair stops a reduction.

Keep the original tables and the reduced rows distinct

Prastara records the individual contributions underlying a planet's table. Eight references contribute: the seven classical planets and the Ascendant. Adding the eight contributions for a particular sign produces one Bhinna value, between zero and eight. Adding the seven planetary Bhinna values for that sign produces its unreduced Sarva value.

The Ascendant is a reference inside each planetary table; it is not an eighth planetary Bhinna table added to the seven-planet Sarva total. This distinction explains why “eight contributors” and “seven tables” can both be correct. A reduced row answers a later calculation question and should carry its own heading.

The seven totals add to 337. That is a checksum for this unreduced scheme across all twelve signs, not a target that each reduced table must preserve. A report whose reduced rows add to less than 337 has not thereby lost data, provided the original rows remain available.

A synthetic chart with completely specified sign inputs

For a transparent example, place the seven planets successively in Aries through Libra and the Ascendant in Scorpio. These are artificial sign inputs for a worksheet, not positions claimed to occur together on a real date. Degrees, retrograde status and house cusps are not additional inputs to this example's reduction stage.

The application's contribution tables produce the Sun row 6, 3, 4, 4, 3, 3, 4, 3, 4, 5, 5, 4, in Aries-to-Pisces order. Its sum is 48. Write the sign names above the numbers before doing anything else: a twelve-number list rotated to the Ascendant without changing its labels will silently move every multiplier.

First stage: subtract the minimum of each trine

The four groups are Aries–Leo–Sagittarius, Taurus–Virgo–Capricorn, Gemini–Libra–Aquarius and Cancer–Scorpio–Pisces. For each group, find the minimum in the original row and subtract it from all three members. Each sign belongs to exactly one group, so no sign is reduced twice during this stage.

For the first group, 6, 3, 4 becomes 3, 0, 1. For the final group, 4, 3, 4 becomes 1, 0, 1. A trine already containing zero changes by zero. Three equal values all become zero. These cases follow from the same subtraction rule; no separate exception is needed to reproduce them.

After this stage at least one value in every trine is zero. This is a useful intermediate check, but it does not tell you which of the remaining values will survive Ekadhipatya. The next stage asks a different question about ownership and occupancy.

Which occupants count in the second stage?

For this implementation, occupancy means the presence of one or more of Sun, Moon, Mars, Mercury, Jupiter, Venus or Saturn in a sign. Rahu, Ketu and the Ascendant do not make a sign occupied for this rule. In our synthetic chart Scorpio contains the Ascendant but is still empty for Ekadhipatya.

Occupancy is a yes-or-no property here. Two planets in one sign do not make it twice occupied. Later, Graha Pinda will count the two planets separately with their own weights. Reusing one of these counting methods for the other stage is a common way to get a plausible but incorrect total.

Use the same sign placements that generated the original row. Moving a planet to a Bhava Chalit house for this step would mix two coordinate descriptions. The Rashi and Bhava Chalit comparison explains why a house assignment does not rewrite a planet's zodiac sign.

Ekadhipatya rules, including zeros and equal pairs

Test the zero condition first: when either value is zero, leave the pair alone. If both signs contain classical planets, also leave it alone. With one occupied sign, preserve its value; clear a smaller empty value, or lower a larger empty value to match it. An equal occupied/empty pair stays unchanged in this profile.

If both signs are empty and nonzero, unequal values become the smaller value on both sides; equal values both become zero. The table deliberately uses isolated examples, so the different outcomes can be checked without changing the synthetic chart.

Rao's chapter supplies the reduction framework used by the application. Its listed one-occupied comparisons specify smaller and larger values; the equality case is made explicit here as the application's unchanged branch. Compare method settings before treating another program's different equality result as an arithmetic error.

Apply the five shared-lord pairs

Mars owns Aries and Scorpio, Venus Taurus and Libra, Mercury Gemini and Virgo, Jupiter Sagittarius and Pisces, and Saturn Capricorn and Aquarius. Cancer and Leo each have a single classical lord's sign and are not paired with one another. They still participated fully in the earlier Trikona stage.

In this example the first three pairs contain a zero and remain as they are. Sagittarius and Pisces are both empty with values 1 and 1, so both become zero. Capricorn and Aquarius are both empty with 2 and 1, so both finish at 1. Cancer's 1 remains untouched by this second stage.

The entire twelve-sign worksheet

Read across each row to see exactly when its number changes. The last two columns prepare Rashi Pinda using the sign multipliers. These are the method's conventional weights, not masses, luminosities, measured physical strengths or percentages.

The raw row totals 48, the Trikona row totals 9, and the final reduced row totals 6. The weighted products sum to 21 + 4 + 5 + 11 = 41. Do not multiply the raw 6 in Aries by seven at this point: the final reduced value there is 3.

Seeing all columns together also prevents a version mismatch. If a screenshot gives the final pinda but omits the earlier rows, you cannot tell whether its author applied the same reduction order or merely used different original Bhinna inputs.

Graha Pinda uses each planet's occupied sign

Now read the reduced Sun row at the natal sign of every classical planet, multiply by that planet's weight, and add the seven products. Even though the row belongs to the Sun, the sum includes all seven classical planets. The name of the Bhinna row does not restrict this sum to its namesake.

Sun contributes 3 × 5 = 15 and Mercury contributes 1 × 5 = 5. The other five planets occupy signs with zero in the reduced row, so their contributions are zero. Graha Pinda is therefore 20, and Shodhya Pinda = 41 + 20 = 61.

For a separate arithmetic illustration, suppose two planets with weights 5 and 8 occupy a sign whose reduced value is 2. Their combined contribution is 2 × 5 + 2 × 8 = 26. Counting the sign only once would lose one contribution. This illustration does not change the chart used in the tables.

Why the order and the choice of row matter

Reduction does not commute with addition. Consider two illustrative trines 5, 1, 3 and 1, 5, 3. Reducing them separately gives 4, 0, 2 and 0, 4, 2; adding produces 4, 4, 4. Adding first gives 6, 6, 6, which reduces to 0, 0, 0. Both arithmetic sequences are internally tidy, but they answer different questions.

Consequently, a reduction applied directly to the summed Sarva row is not a substitute for reducing each planetary Bhinna row. Likewise, the shared-lord tests must inspect the post-Trikona values. Applying them to the initial row can change which zero branch is taken and propagate a different pinda.

How to investigate a disagreement between reports

1. Align the columns to Aries through Pisces and identify the planet whose row is being reduced.
2. Check the original Bhinna values and their fixed planetary total.
3. Compare the four trine minima before checking any pinda.
4. Mark occupancy from the seven classical planets only.
5. Inspect zeros, equal pairs and the order of the two reductions.
6. Check all twelve sign multipliers and all seven planet multipliers.
7. Verify that Rashi plus Graha equals the displayed Shodhya Pinda.

If raw rows differ, look upstream at the contribution tables and sign inputs. If raw rows match but reduced rows differ, focus on reduction conventions. If reduced rows match but pindas differ, the likely disagreement is in weights, occupancy lookups or summation. This sequence locates a discrepancy far more efficiently than comparing the final number alone.

What a pinda does and does not establish

Pinda is a constructed quantity in a traditional astrological calculation. The arithmetic can be checked independently of belief in the predictions sometimes associated with it. A zero in one reduced sign is not a verdict that an entire part of life is absent, and 61 is not a 61 percent success rate.

It is also not Bhava Bala or Shadbala expressed in a new unit. Those methods use different ingredients. For their distinction, read the complete Bhava Bala worksheet. Accurate labeling is especially useful when a report places all these tables near one another.

Open Kundli to explore the application's calculation tables, and consult the calculation methodology in Hindi for method context. Keep the original rows with any exported calculation so that another reader can reproduce the result instead of relying on a single unexplained score.

Frequently asked questions