Library
Vedic Astrology Wiki

Sarvashtakavarga SAV: Add BAV Rows and Map Houses

Calculate a SAV cell from seven BAV values, distinguish sign order from house order, and check raw totals without turning them into outcome guarantees.

Names and related terms
Sarva Ashtakavarga · Samudaya Ashtakavarga · SAV

Editorially reviewed: · Reviewed by OpenFate · Editorial Methodology

Overview

Sarvashtakavarga, or SAV, adds the raw BAV counts of Sun, Moon, Mars, Mercury, Jupiter, Venus and Saturn in each sign. It is a combined sign distribution, not one planet’s strength or a probability.

At a glance

Aggregation
Seven target-planet rows per sign
Not added
No extra lagna target row here
Display mapping
Sign order and house order differ
No conversion
A point count is not a percentage

How is a SAV cell calculated?

Keep every component in the same sign column and add its seven planetary BAV values. Lagna already contributes within each of those tables; adding another lagna target row would define a different aggregate.

SAV may be displayed Aries-to-Pisces or rotated from the lagna into house order. Identify the labels before comparing two exports. A rotation changes where a number appears on screen, not the underlying sign count.

Twenty-nine in Aries is not always house one

For an illustrative Aries column, take BAV values 4, 5, 3, 6, 4, 5 and 2 for Sun through Saturn. Their sum is 29. This single-column exercise does not claim to be a complete calculated birth chart.

With Cancer lagna and whole-sign houses, Aries is house 10, so that 29 belongs to H10 rather than H1. Copying an Aries-first array directly into a house-first display would mislabel the evidence even if the overall total remained correct.

Does a high value guarantee a good result?

No. It is a traditional count under a defined table, not a calibrated probability of wealth, marriage or safety. Published interpretation thresholds also vary and should not be treated as universal measurements.

Check each component, the sign-to-house rotation and the raw-versus-reduced label. The 337 checksum page explains a useful invariant for a named table set, but matching that number alone cannot validate every cell.

Sources and editorial basis

  1. P. V. R. Narasimha Rao: Vedic Astrology — An Integrated Approach
    Rao, Chapter 12, §§12.1–12.4, printed pp. 145–153; Tables 19–25: eight reference contributors, individual raw BAV values and seven-target SAV aggregation. §12.6, pp. 156–157: prastara preserves contributor identity. §§12.7–12.8, pp. 157–162: reduced tables are separate; bindu/rekha notation and Moon/Venus contribution positions vary. The 337 figure is an explicitly identified raw-table checksum; it does not establish cell-wise equivalence between Rao’s preferred variant and the inspected OpenFate table or validate any life outcome. Example vectors and sums are editorial arithmetic, not claimed calculated birth charts.A named practitioner’s introduction to Jyotish. Used for terminology and a stated method, not universal school agreement or scientific validation. The added March 18, 2010 note describes changed views; it does not establish a fully revised 2010 edition.
  2. OpenFate Editorial Methodology
    OpenFate Editorial Methodology, stable sections #editorial-principles, #editorial-workflow, #editorial-ai, and #editorial-context. Used for the calculation/interpretation and evidence-boundary policy.OpenFate separates deterministic chart calculation, traditional interpretation, and modern editorial explanation.
  3. OpenFate Vedic implementation: local source review, 2026-09-08
    OpenFate local implementation review, 2026-09-08: app/modules/vedic/logic/policy.ts VEDIC_ENGINE_POLICY.karakaScheme and supportsVedicBav; facts.ts computeKarakas and computeSarvashtakavarga; constants.ts SAV_TABLES, SAV_EXPECTED_TOTALS and SAV_EXPECTED_GRAND_TOTAL; career-evidence.ts buildVedicCareerEvidence.unavailable. The reviewed policy uses seven roles without Rahu and a fixed classical-order exact-tie break. Raw BAV rows total 48/49/39/54/56/52/39, summing to 337; the Moon/Venus variant entries differ from Rao’s stated preference. BAV visibility depends on stored contract, and career evidence explicitly marks shadbala unavailable. This is a dated code review, not proof of current deployment or empirical prediction accuracy.An editorial review of local policy and calculation source files, not an independently accessible publication or proof of the deployed version. Implementation limitations and discrepancies remain separate from traditional arithmetic.
Was this article helpful?

Search the Wiki