Ashtakavarga: What the Points (Bindus) Actually Mean

Every Sarvashtakavarga adds up to exactly 337 — in every chart ever cast. That fixed total is the key to the whole system, and the reason most people misread it. Ashtakavarga scores how much support each sign of a chart receives from the planets, in points called bindus. But because the grand total is always 337, the map is zero-sum: no chart is strong everywhere, and every strong sign is paid for by a thin one somewhere else. That's what turns ashtakavarga from a fortune score into something more honest — a map of where a particular life concentrates its support.

TL;DR

Ashtakavarga assigns each sign a number of bindus (benefic points) based on how the planets sit relative to one another. There are two views: Bhinnashtakavarga (BAV), one chart per planet showing that planet's support across the signs (0–8 bindus per sign), and Sarvashtakavarga (SAV), the sum of all of them. The SAV always totals 337 across the twelve signs, averaging about 28 per sign — so strength is always relative to your own chart, never absolute. Signs well above 28 are strong; well below are thin. Its most reliable use is transit timing: a slow planet crossing a high-bindu sign tends to deliver better than the same planet through a low one, and the kakshya layer refines that down to which exact degrees within the sign are supported. Read it as a support map, not a fortune number.

What the bindus actually are

A bindu is a "benefic point" a planet contributes to a sign, based on classical rules about where it stands relative to the other planets and the ascendant. Each planet's own table — its Bhinnashtakavarga — gives every sign between 0 and 8 bindus, more meaning that planet finds more support there. Add the seven planets' tables together and you get the Sarvashtakavarga: one number per sign summarising total planetary backing for that part of the chart.

The numbers aren't arbitrary mysticism; they're a bookkeeping system. The skill isn't producing them — software does that instantly — but knowing the baselines, so a given figure means something.

What counts as a high or low score

Because the SAV always totals 337, the average sign carries about 28 bindus, and that average is the only reference that makes a single number readable.

Sarvashtakavarga (per sign)	Reading
30 and above	Strong — well-supported; transits here tend to go better
25–29	Average — neither a tailwind nor a headwind
Below 25	Weak — thinner support; transits here ask for more care

For a single planet's Bhinnashtakavarga the logic mirrors this on the 0–8 scale: a planet transiting a sign where it holds 5–8 of its own bindus is on home turf, 0–2 is exposed. None of this predicts a specific event — it grades the terrain a transit is crossing. And because of the zero-sum total, a sign scoring 32 is strong precisely because others in the same chart are lean; you are always reading a sign against the rest of its own chart, never against an absolute scale.

The real use: reading transits

Ashtakavarga's most defensible application is modulating transit timing — it tells you whether a transit is moving through supportive ground or thin ground. A workable method runs like this:

Find the sign a slow planet (Saturn, Jupiter, Rahu/Ketu) is entering.
Read its Sarvashtakavarga. High (30+) is well-supported ground; low (under 25) is thin.
Check that planet's own Bhinnashtakavarga in the sign — does the transiting planet itself hold many of its own bindus there?
Then go finer, to the kakshya (below), to see which degrees of the crossing are supported.

A concrete example makes the use obvious. Suppose Saturn is about to transit the sign on your 10th house of career. Before deciding whether that's a heavy few years or a building one, check the SAV of that sign. At 32 bindus, Saturn works on well-supported ground — the classic "hard but rewarding" Saturn that consolidates a career. At 22, the same transit lands with far less to lean on, and patience matters more. The transit overhead is identical; the ashtakavarga reveals that the ground beneath it differs. It's a large part of why two people with Saturn crossing the same sign report such different years — their bindu maps are not the same. This pairs naturally with the gochara transit reading from the Moon: the transit names which theme is active, the bindus say how much support it has.

The kakshya: which degrees of a transit are supported

Here is the layer that turns ashtakavarga from a coarse sign-score into a precise timing tool, and the part most one-click readings never reach. Each 30° sign is divided into eight kakshyas of 3°45' apiece, each ruled by a planet in a fixed order (classically Saturn, Jupiter, Mars, Sun, Venus, Mercury, Moon, and the Lagna). As a transiting planet moves degree by degree through a sign, it passes from one kakshya to the next — and in each, it is supported only if that kakshya's ruler had contributed a bindu to the planet in that sign.

The consequence is practical and a little surprising: even within a single high-bindu sign, a transit alternates between supported and unsupported stretches. A Saturn transit doesn't deliver one uniform tone for two and a half years; it brightens through the kakshyas whose lords backed it and dips through those that didn't. This is why a careful practitioner can say not just "this is a good year for the transit" but "the supportive window is the months Saturn spends in these particular degrees."

To see it concretely: say Saturn, transiting your 10th-house sign, holds bindus from five of the eight kakshya lords there. As Saturn crawls through the sign over roughly two and a half years, the months it spends in the kakshyas of those five supportive lords tend to read as the productive, consolidating stretches, while the months in the three unsupported kakshyas feel heavier and slower to reward. A reader who knows this won't tell you "the whole transit is good" or "the whole transit is hard"; they'll point to the specific degree-windows where the support actually lands. That degree-level resolution is the real payoff of going past the sign score, and if you'd like the SAV, BAV, and kakshya read against the live transits with the reasoning attached, a depth reading lays them out.

Beyond transits: where a chart keeps its reserves

Transits are ashtakavarga's headline use, but the natal SAV map is quietly informative on its own. Scan the twelve signs and notice where the bindus pool. The houses carrying the highest counts are the areas of life with the deepest reserves of support — the ones that tend to recover, sustain, and reward returning effort — while the lean houses are where effort tends to meet less natural backing. This doesn't predict outcomes: a high-bindu 7th house is no promise of an easy marriage, and a lean one is no sentence to a hard one. What it offers is orientation, telling you which departments of the chart are working from strength and which are working uphill. Laid over the house lords and the dasha sequence, that reserve-map is a useful piece of context — never the verdict, but a real part of the terrain.

Ashtakavarga is not shadbala

A common confusion worth clearing up: ashtakavarga and shadbala are different strength systems. Ashtakavarga scores the signs and houses by bindus and is used mostly for transits. Shadbala measures a planet's strength from six distinct sources (positional, directional, temporal, motional, natural, and aspectual), expressed in units called rupas. When people ask "what do the shadbala percentages mean," they're asking about that six-fold system, not ashtakavarga. Both grade strength; they grade different things, and a serious reading uses each for its own purpose.

A support map, not a fortune number

Ashtakavarga is a genuinely useful grading tool, but it grades support and strength — it does not, on its own, predict events. A high-bindu sign is favourable ground, not a guarantee; a low-bindu sign is demanding terrain, not a sentence. It also hasn't been validated as a standalone predictor under controlled study, so the honest framing is the same as for the rest of the system: use it as a map that modulates the reading, layered with the houses, the planets' dignity, the dashas, and the transits. Read that way it sharpens a reading; read as a fortune number, it over-claims. The points show you where a chart keeps its reserves of support — what you do on that ground is still yours to decide.

FAQ

What is ashtakavarga in simple terms?

It's a points system that scores how much support each sign of a chart receives from the planets, using "bindus." A higher bindu count means more planetary backing for that part of the chart. Because the total is fixed, it's a relative map — and its most reliable use is judging whether a transit is moving through strong or weak ground.

What is the difference between Bhinnashtakavarga and Sarvashtakavarga?

Bhinnashtakavarga (BAV) is one table per planet, showing that single planet's support across the signs (0–8 bindus each). Sarvashtakavarga (SAV) is the sum of all of them — total support per sign. The SAV always adds up to 337 across the twelve signs, which is why strength is always read relative to the rest of the chart.

What is a good Sarvashtakavarga score?

Since the SAV totals 337 across twelve signs, the average is about 28 per sign. Roughly, 30 and above is strong, 25–29 is average, and below 25 is weak. These are baselines for judging support relative to your own chart, not predictions of events.

What is a kakshya in ashtakavarga?

A kakshya is one of the eight 3°45' sub-divisions of a sign, each ruled by a planet. As a planet transits, it's supported in a given kakshya only if that kakshya's ruler gave it a bindu in that sign — which is why a transit has better and worse stretches even within one sign. It's the layer that pins transit timing down to specific degrees.

How reliable is ashtakavarga?

As a classical tool for grading strength and modulating transit timing, it adds real nuance. As a standalone predictor of events, it hasn't been validated and shouldn't be treated as one. Used as a support map layered with the rest of the chart, it's genuinely useful; used as an oracle, it over-claims.

Ashtakavarga: How to Actually Use the Points (Not Just Calculate Them)