Ashtakavarga Chart Calculator

Ashta means eight. For each of the seven grahas, eight sources — the seven grahas themselves plus the ascendant — each contribute a point, a bindu, to certain signs counted from where that source sits. Every source has its own contribution table, given in the Brihat Parashara Hora Shastra, and the resulting grid of twelve signs by seven planets is the Bhinnashtakavarga.

The totals are fixed and are the reason this technique is checkable in a way almost nothing else in astrology is. Whatever the chart, the Sun's bindus across all twelve signs total 48, the Moon's 49, Mars's 39, Mercury's 54, Jupiter's 56, Venus's 52 and Saturn's 39. Add all seven and you get 337, every time, for every chart ever cast. The result panel above prints those totals so you can verify them, and the engine asserts the 337 rather than trusting it.

This matters because the commonest implementation error produces plausible numbers that fail the check. Applying the target planet's own contribution row to every source instead of each source's own row gives a grid with cells above eight, per-planet totals that vary, and a Sun-in-Cancer value of seven where BPHS gives one. This calculator uses the eight-source classical tables; the module's older approximation is retained only for a regression test and is read by nothing.

What a bindu count means

A sign with many bindus for a planet is one where that planet has broad support; a sign with few is one where it does not. The usual reading threshold is four, the average, though the per-planet averages differ — Jupiter's mean is 4.67 and Saturn's 3.25, so the same raw number is not the same finding for both.

The transit use

The classical and by far the commonest use is for transits: when a planet transits a sign, its bindu count there is read as how supported that transit is. Saturn crossing a sign with one bindu and the same Saturn crossing a sign with seven are the same transit in two different chart environments.

Kaksha and reduction

Fuller Ashtakavarga practice adds the kaksha subdivisions, and the Trikona and Ekadhipatya reductions before computing the shodhya pinda. This engine computes the Bhinna and Sarva grids and does not perform the reductions, so this page does not report them.

The combinations above were tested against a Gemini ascendant, and that single fact decides every one of them. A yoga defined by the second and eleventh lords is a statement about two specific planets, and which two depends entirely on which sign was rising. Change the ascendant and you change the lords, the categories they belong to, and therefore the answer.

The categories are the vocabulary the whole yoga literature is written in. Kendras — the 1st, 4th, 7th and 10th — are the pillars: the houses that hold a chart up. Trikonas — the 1st, 5th and 9th — are the sources of fortune and merit. A Raja Yoga is a link between a lord of one group and a lord of the other, and that is the whole definition. Dusthanas — the 6th, 8th and 12th — are the houses of difficulty, and a lord of a dusthana placed in another dusthana is the Viparita reversal. Upachayas — the 3rd, 6th, 10th and 11th — are the houses that improve with time, which is why malefics there are read differently from malefics anywhere else.

The first house belongs to two categories at once, being both a kendra and a trikona, and that is not a bookkeeping accident: it is why the ascendant lord is the single most important planet in a Parashari reading, and why a yoga involving it carries more weight than the same structure built from any other pair.

The occupants column is there because a house lord and a house occupant are different things and are constantly confused. A planet sitting in the tenth house is not the tenth lord unless it also rules the sign there. Most yoga definitions are about lords; a few — Budha-Aditya, Chandra-Mangal, the Mahapurusha set — are about occupants. The table gives you both so a definition can be checked rather than taken on trust.

1. Check the totals first 48, 49, 39, 54, 56, 52, 39, and 337 for the grand total. If a calculator anywhere gives you different figures, its grid is wrong regardless of how reasonable the cells look.
2. Read each planet's own row, not the column The comparison that means something is between signs for one planet. Comparing Jupiter's 6 with Saturn's 6 compares two numbers on different scales, since their totals differ by 17.
3. Find the high and low signs for the slow planets Saturn and Jupiter transit slowly enough for the bindu count of a sign to describe a period of years. Those two rows are the practically useful part of the grid for most people.
4. Read the transit against the natal chart, not on its own A bindu count says how supported a transit is, not what it does. What a transit touches — which house, which natal planet — is the birth chart's question and the more important half of the reading.
5. Do not convert bindus into a forecast The grid describes environments, not events. It is one of the few techniques in this system with a genuinely objective output, and turning it into a prediction throws that away.

Every combination reported above is produced by a named detector in this site's astrology engine, not by a language model and not by a lookup table of pre-written paragraphs. A detector takes the planet-to-house map, the planet-to-sign map and the ascendant, applies one classical condition, and returns three things: whether the condition held, a strength between zero and one, and the rule it applied. All three are printed.

Strength is not a score. It reflects how firmly that detector's own condition was met — how many qualifying conjunctions were found, how many of the three benefics participated, how many debilitations were cancelled. It is calibrated per detector and is not a common currency, so adding the column up produces a number that means nothing. It exists so that a marginal case can be told from an emphatic one, and for no other purpose.

Absent combinations are printed. A calculator that lists only what it found leaves a reader unable to distinguish a chart with no yogas from a check that ran incompletely, and the omission always flatters. Every page here reports the number tested alongside the number found, and both numbers come from the same list.

What is not checked is named rather than hidden. This engine has no detector for Dharma-Karmadhipati yoga — the ninth and tenth lords in conjunction or mutual aspect — so no page here claims to test it. It has none for Kaal Sarp Dosha either. Both are well-known enough that their absence looks like an oversight, which is precisely why it is stated: a row that silently reports 'not present' for a condition nothing evaluated is a lie a reader cannot detect.

The Pancha Mahapurusha set is assembled in exactly one place in the engine. It used to be detected in two modules at once, so three of the five came back twice in a single chart and Saturn's came back under two different spellings — which inflated both the count of yogas a chart carried and the scores derived from it. The count this page reports is a real count.

Almost every combination on this page is defined by house position or by house rulership, and houses are the part of a chart that moves fastest. The ascendant travels through all twelve signs every twenty-four hours — roughly one sign every two hours, and roughly one degree every four minutes — so an hour's error in a recorded birth time routinely changes the rising sign. Change the rising sign and every house lord changes with it, which changes most of the table above.

The planets themselves are far steadier. The Moon changes sign about every two and a quarter days, the Sun about every month, and Jupiter and Saturn are fixed across a whole day. So a combination defined purely by two planets sharing a sign survives a rough birth time, and one defined by houses does not. Where a result on this page depends on a house, treat it as provisional unless your birth time is recorded to the minute.

Every reading here assumes a rectified birth time. The same caution applies with more force to the divisional charts a combination should be checked against: beyond the D9 they are highly birth-time sensitive, and the D60 changes ascendant about every two minutes.

The ascendant is not a property of the instant alone. It is the point of the ecliptic rising over a particular horizon, so it is a function of the moment and of the coordinate together, and the two trade off exactly: the sky turns one degree every four minutes, and one degree of longitude is four minutes of local time. Moving one degree of longitude — about 103 km east or west at Indian latitudes — moves the ascendant a degree, and 3096 km moves it a whole sign. A different rising sign means different house lords, and every combination on this page is a statement about house lords.

Latitude matters separately and less obviously. It does not shift the clock, it changes how fast each sign climbs — the ascensional difference — so two places on the same meridian and the same instant still rise different degrees, and the gap grows the further from the equator you are. This is why a chart cast for a state capital is not a rounding of a chart cast for a village two districts away; it is a different chart that happens to look plausible.

So enter the town you were actually born in. The place search above accepts any village, town or city a geocoder knows, not a shortlist of metros, and it prints the latitude, longitude and timezone it used above the result so you can check them against a map. Since one whole sign of the ascendant is the unit this page is built from, a birth place picked for convenience damages the result in the same way and by the same mechanism as a birth time rounded to the nearest quarter hour.

A bindu count is not a percentage and not a score out of eight. It is a count of contributing sources, and the meaningful comparison is between signs for one planet, not between planets.

A low bindu count in a sign does not predict a bad event when a planet transits it. It describes an environment. Reading a misfortune out of a bindu count is the standard way this technique is used to frighten people.

Ashtakavarga does not produce a life prediction and is not a remedy market. It is a per-sign support grid, and it is at its most honest when used comparatively for transits.

Two limits apply to every page in this family and are worth stating in one place. Divisional charts beyond the D9 are highly birth-time sensitive, and every reading here assumes a rectified birth time. And nothing on this site is medical, legal or financial advice: a chart is a traditional interpretive framework, not a diagnosis, not a forecast, and never a reason to delay professional help.

A combination found in the birth chart is a first reading, not a finished one. The classical instruction is to test it against the divisional charts, and above all against the Navamsa: a yoga formed by planets that hold their dignity in the D9 is described very differently from one formed by planets that collapse there. That cross-check is the single most useful thing a reader can do with a positive result, and almost no calculator performs it.

The sixteen vargas are Parashara's Shodashavarga, and the weighting between them — Vimshopaka Bala — puts the D1, D9 and D60 highest. Every one of them is computed on this site from the classical start-sign rules rather than the cyclic shortcut that collapses the D12 and D60 into Aries. The Navamsa calculator is the one to run next after a ashtakavarga chart check; the Shashtiamsa calculator is the final dignity test, and it needs a birth time good to the minute.

Timing is a separate system again. A natal combination is a standing feature of a chart with no dates in it; when it expresses is a Vimshottari Dasha question, read from the periods of the planets that form it. Any tool that produces a date from a natal yoga has generated a sentence rather than read a chart.