Reading the KundliAugust 10, 2026 11m read 175 views 0

What Is Ashtakavarga, and How Is It Used?

By Kaalveda Research Team

What Is Ashtakavarga, and How Is It Used?
Ashtakavarga is the closest thing Jyotisha has to a quantitative model. This guide explains bindus, Bhinnashtakavarga, the 337-point Sarvashtakavarga total, the kaksha refinement, and where the numbers stop being evidence.

In one paragraph

Ashtakavarga is the system that turns a birth chart into numbers. Rather than describing a graha as "strong" or "afflicted" in prose, Ashtakavarga awards every one of the twelve signs a score of benefic points — bindus — so that signs can be compared arithmetically. Each of the seven classical grahas from the Sun to Saturn receives its own scorecard, the Bhinnashtakavarga or BAV, built by eight contributors: the seven grahas plus the Lagna, which is where ashta in the name comes from. Sum all seven BAVs and you get the Sarvashtakavarga or SAV, a row of twelve totals whose grand total is always 337 — the standard check that a calculation is correct. Its most valuable application is transit judgement: a graha moving through a sign where it holds many bindus tends to deliver, and through a sign where it holds few tends not to. Ashtakavarga is the nearest thing the tradition has to a quantitative model, which is precisely why it needs handling with care.

The twelve houses an Ashtakavarga scores

What Ashtakavarga actually is

The name breaks into ashta, eight, and varga, a group or class. The "eight" are the eight contributors — Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn and the ascendant — not eight charts and not an eightfold division of the zodiac. This matters because varga is also the word for divisional charts such as the navamsa, covered separately in what divisional charts or vargas are. The two are unrelated. Ashtakavarga is a scoring layer laid on top of the natal chart, not a chart derived from it.

The mechanism is simple in principle. For a given graha, you ask each of the eight contributors a yes-or-no question about every sign: counting from where that contributor sits, does this sign fall in a position the classical tables mark as benefic for the graha in question? A yes is recorded as a bindu, a dot; a no leaves the cell empty. Every sign therefore ends up with a score between 0 and 8 in that graha's BAV.

The technique is old within the tradition rather than a modern add-on, treated in the Brihat Parashara Hora Shastra, in Varahamihira's Brihat Jataka and later at length in the Phaladeepika. It is not, however, Vedic: like most of applied horoscopy it belongs to the classical and medieval Jyotisha corpus, and the tables have been transmitted with small but real variations.

Ashtakavarga does not tell you what will happen. It tells you how much structural support a sign carries. Support is not outcome, and a number is not a prediction.

How the bindus are assigned

The clearest way to see the machinery is to take one graha. The Sun's Bhinnashtakavarga is built from the classical contribution list below. Read each row as "counting the contributor's own sign as house 1, the Sun receives a bindu in these houses".

Contributor Houses in which it gives the Sun a bindu Bindus
Sun 1, 2, 4, 7, 8, 9, 10, 11 8
Moon 3, 6, 10, 11 4
Mars 1, 2, 4, 7, 8, 9, 10, 11 8
Mercury 3, 5, 6, 9, 10, 11, 12 7
Jupiter 5, 6, 9, 11 4
Venus 6, 7, 12 3
Saturn 1, 2, 4, 7, 8, 9, 10, 11 8
Lagna 3, 4, 6, 10, 11, 12 6
Total 48

Every BAV has a fixed total, because the contribution lists are fixed. The Sun's always comes to 48, in every chart. What varies is only how those 48 points are distributed across the twelve signs — one chart concentrates them, another spreads them evenly. Each of the other six grahas has its own table and its own fixed total.

Sarvashtakavarga and the 337 check

Stack the seven BAVs and add them sign by sign, and you have the Sarvashtakavarga. Because each BAV total is fixed, the SAV total is fixed too.

Graha Total bindus in its BAV
Sun 48
Moon 49
Mars 39
Mercury 54
Jupiter 56
Venus 52
Saturn 39
Sarvashtakavarga total 337

If the twelve SAV numbers in front of you do not add to 337, the calculation is wrong. That is the most useful arithmetic fact in the whole system, and it is worth applying every time, to your own working and to any chart handed over by software or a practitioner. 337 divided by 12 gives an average of roughly 28 bindus per sign, the baseline against which every individual score should be read.

Note what this implies. Ashtakavarga is a zero-sum accounting of a fixed pool. A chart cannot have twelve strong signs. If several score in the mid-thirties, others must score in the low twenties, by necessity rather than by misfortune. A low score somewhere is structurally guaranteed in every chart ever cast.

How to read a Sarvashtakavarga

The conventional reading is comparative. Signs, rashis, carrying high totals are well supported; those carrying low totals are thinly supported. Practitioners generally work with bands along these lines.

SAV score for a sign Conventional reading
32 and above Notably strong
30 to 31 Strong
28 to 29 Slightly above average
25 to 27 Average
22 to 24 Below average
Below 22 Weak

These bands are conventions of practice, not laws of the system. Different teachers set the cut-offs a point or two apart, and no classical text hands down a table of thresholds in this form. Treat them as a rough vocabulary for describing distribution, not as diagnostic criteria.

The bands become meaningful only once mapped onto the houses. Since the SAV scores signs and houses are counted from the Lagna, a strong sign matters most when it happens to be a house you care about. A high SAV on the sign occupying the tenth bhava is read as support for professional standing; on the seventh, for partnership; a low score on the sixth is read favourably by some practitioners, the sixth being a house of conflict and debt. That vocabulary is set out in the twelve bhavas introduction, and the chart it all sits on in what a janam kundli or janam patri is.

Using Ashtakavarga to judge transits

This is what Ashtakavarga is genuinely good at, and it is where most of its practical value lies.

The natal chart is static. Gochara, transit, is the moving layer, and the recurring problem in transit work is that the same transit plainly does not deliver the same result for everybody. Jupiter entering Taurus is one event in the sky and thousands of different experiences on the ground. Ashtakavarga supplies a chart-specific filter for exactly that problem.

Reading a transit through your own bindus

The rule is straightforward: when judging a transit, look at how many bindus the transiting graha holds in its own BAV for the sign it is entering.

Bindus held by the transiting graha in that sign Conventional reading of the transit
6 to 8 Strongly supported; the transit tends to deliver
5 Workable; results generally follow effort
4 Neutral; other factors decide
2 to 3 Thin; results tend to lag or arrive partially
0 to 1 Poorly supported; the least productive stretch

Two people can therefore experience the same Saturn transit very differently, and Ashtakavarga supplies a concrete, reproducible reason rather than a rhetorical one. A graha with 7 bindus in a sign carries its own scaffolding; the same graha with 1 bindu is working without it.

One refinement is worth stressing: read the transiting graha's own BAV, not the SAV and not another graha's BAV. Saturn's transit is judged against Saturn's Bhinnashtakavarga. The SAV is better used for a general sense of which areas of the chart are load-bearing. Confusing the two is the commonest error people make with this system.

Saturn and Jupiter, the slow movers

Ashtakavarga earns its keep most obviously on the slow grahas, whose transits last long enough for the difference to be felt. Saturn spends roughly two and a half years in a sign; Jupiter roughly one year. A Saturn transit through a sign holding 6 bindus in Saturn's BAV is a materially different stretch of life from the same transit through a sign holding 1, though both look identical on a transit calendar.

This is the sensible way to approach Sade Sati, the seven-and-a-half-year Saturn period around the natal Moon. Sade Sati is not a uniform block of difficulty. Read the three signs involved against Saturn's own BAV and the phases usually separate: one may carry 5 or 6 bindus, another 2. The popular framing of it as a single sentence of hardship does not survive contact with the numbers. Saturn's wider significations are covered in Shani or Saturn in Vedic astrology.

Transit judgement is also no replacement for the dasha system, set out in what a dasha is. Ashtakavarga tells you how well a transit is supported; the dasha tells you whether that part of the chart is active at all.

Kaksha for finer transit timing

For finer work, each sign of 30 degrees is subdivided into eight kakshas of 3 degrees 45 minutes each, one per contributor, in the fixed order Saturn, Jupiter, Mars, Sun, Venus, Mercury, Moon, Lagna from the start of the sign.

As a graha transits, note which kaksha it currently occupies, then check whether that kaksha's lord gave the transiting graha a bindu in that sign. If yes, the sub-period reads as productive; if no, as flat. This is how a two-and-a-half-year Saturn transit gets broken into shorter alternating stretches rather than one undifferentiated block. It is useful for narrowing a window — but it multiplies the small judgements being made, and each inherits whatever uncertainty sits in the underlying table.

The reductions and what they are for

Classical practice adds two reductions on top of the raw counts: trikona shodhana, reduction by trines, and ekadhipatya shodhana, reduction for signs under a single lord. Applied in sequence with multipliers, they yield the sodhya pinda, a figure used chiefly in longevity work.

These reductions are where the authorities diverge most visibly. The order of application, the treatment of a sign with no bindus and the handling of empty houses are all transmitted differently, so two competent practitioners can produce different sodhya pinda values from one chart while each follows a defensible reading. Anyone quoting a reduced figure should be able to say which method they used. Most day-to-day work, transit judgement included, uses the unreduced BAV and SAV.

Honest limits of Ashtakavarga

Ashtakavarga looks quantitative, and because it looks quantitative it feels objective. It is not.

  • The point values come from classical tables, not from measurement. Nobody derived them from observed outcomes. They are inherited assignments, and different manuscript traditions transmit them with variations — small, but real, and enough to shift a sign's total by a point or two.
  • The interpretive bands are conventions. No classical source states that 30 is strong and 22 is weak. Those thresholds are practitioner shorthand that hardened into apparent rules through repetition.
  • A number is not evidence. A score of 22 is simply a low share of a fixed pool of 337. Since the pool is fixed, some sign in every chart ever cast has to sit at the bottom. A reader who sees 22 should not panic — that is a distribution, not a verdict.
  • The resolution is coarse. Bindus are assigned by whole sign, so degrees, dignity, aspects, retrogression, combustion and dasha sequence are all invisible to the calculation. Two charts a few hours apart usually share almost every bindu, since only the Lagna and sometimes the Moon have moved.
  • It settles nothing on its own. A high SAV on a sign whose lord is badly placed does not overrule the placement, and a low SAV does not cancel a strong one.
  • Sign boundaries depend on the ayanamsha. Because the system is computed by sign, a graha near a boundary can shift and change the scores, for the reasons set out in what ayanamsha is.

None of this is a reason to discard the system. It is a reason to use it for what it does well — comparing transits within one chart — and to resist treating its output as measurement. Nothing here is a substitute for medical, legal or financial advice, and no bindu count should decide a treatment, a contract or an investment.

Where to start

Was this article helpful?

Your feedback helps us improve our content