Library
Vedic Astrology Wiki

Ashtakavarga 337 Points: Checksum, Not a Destiny Score

See why the named seven raw BAV totals add to 337, how bindu notation and table variants differ, and why a matching total does not validate every cell.

Names and related terms
337 bindus · ashtakavarga 337 points · SAV total

Editorially reviewed: · Reviewed by OpenFate · Editorial Methodology

Overview

The 337 total is the sum of seven raw BAV row totals in the declared table set: 48, 49, 39, 54, 56, 52 and 39. It is an arithmetic invariant, not a score distinguishing a better life from a worse one.

At a glance

Named raw totals
Sun 48, Moon 49, Mars 39, Mercury 54
Remaining rows
Jupiter 56, Venus 52, Saturn 39
Sum
337 before reductions
Audit limit
Equal total does not prove equal cells

Why is 337 the same for different charts?

With a fixed contribution table, moving a reference changes which signs receive its points, not how many positions its rule lists. The inspected OpenFate raw tables therefore assert seven row totals and a grand total of 337.

These numbers must be tied to that named table set. Rao’s Chapter 12 supplies the raw-table framework and discusses Moon/Venus entry variants; a common total does not show that every author or program uses the same individual entries.

A total catches some errors but misses others

Add 48 + 49 + 39 + 54 + 56 + 52 + 39 to obtain 337. If a broken row adds one extra contribution without removing another, the total becomes 338 and the invariant catches it.

Moving one point from Aries to Taurus leaves the total at 337. So does exchanging a contribution between two rule positions. Those errors require cell-level or source-table checks; renormalizing 338 back to 337 would hide the first error rather than fix it.

What do bindu and rekha mean here?

OpenFate calls a counted favorable contribution a bindu. Rao uses rekha for that 1 and explicitly notes the opposite naming convention. Always read the legend before assuming that a dot represents the same numerical value in two sources.

The total applies to the raw seven-row aggregate, not a reduced table or weighted pinda. A person does not gain merit, wealth or longevity by “having 337”; it is the table’s conservation rule, not an individualized outcome measure.

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