Library
Vedic Astrology Wiki

Gochara Meaning: How to Count Vedic Transits

Understand gochara as a target-time planetary position compared with a natal reference. A worked example separates Moon-based and lagna-based counts.

Names and related terms
Gochara · Gochaara

Editorially reviewed: · Reviewed by OpenFate · Editorial Methodology

Overview

Gochara means planetary transit: a position evaluated at a selected time, compared with a declared natal reference. Rao distinguishes a planet’s transit position from its birth position. The same transit can receive a different relative house number when the reference changes.

At a glance

Natal layer
Position at birth
Transit layer
Position at the requested instant
Counting here
Inclusive sign count from a named natal sign
Limit
A relative number is not an observed life outcome

How do I calculate a relative transit position?

Choose the natal reference first, such as the natal Moon’s sidereal sign. Keep it fixed while calculating the transit planet at the target instant under the same zodiac convention. Count the reference sign as one and continue forward to the transit sign.

Do not substitute the transiting Moon for the natal Moon midway through the calculation. A moving reference is another method and must be labelled. Nor should a sign-based count be quietly replaced with a degree-based aspect or a different house-cusp system.

Jupiter in Libra from two references

Use invented data: natal Moon in Leo, natal lagna in Gemini, target-time Jupiter in Libra. From Leo, Leo–Virgo–Libra gives three. From Gemini, Gemini–Cancer–Leo–Virgo–Libra gives five. Both counts describe the same hypothetical Jupiter.

Record “third from natal Moon” and “fifth from natal lagna” in separate fields. Jupiter’s degree and any aspect still need their own calculation. Neither count establishes a result concerning learning, children or finances simply because those topics appear in traditional house lists.

What if the natal sign is not certain?

Recompute the credible birth-time interval before using a natal Moon or lagna near a sign boundary. If the reference changes, present both relative counts. A transit position can be precise while the personal comparison remains unresolved.

Rao §25.2 records Moon-based transit interpretation, but its traditional outcome tables are not adopted as verified personal claims here. Use the transit-settings guide for numerical comparisons and the dasha guide when the question concerns a period rather than a sky position.

Sources and editorial basis

  1. P. V. R. Narasimha Rao: Vedic Astrology — An Integrated Approach
    §§25.1–25.2, printed p. 314: definition of gochaara and janma-rasi reference. Inclusive sign-count exposition is applied to explicitly hypothetical Leo/Gemini/Libra inputs.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. Swiss Ephemeris Programmer’s Manual: Time, Sidereal Modes and Houses
    Swiss Ephemeris Programmer’s Manual, §12.1 swe_set_sid_mode (including Lahiri modes) and §12.2 ayanamsa functions; §15 house calculation. The page’s rounded arithmetic examples are original teaching inputs, not ephemeris outputs.Primary software documentation for numerical time and position calculations. Sidereal modes, including named Lahiri variants, are explicit settings. The manual does not validate astrological interpretations.
  4. OpenFate Vedic implementation: local source review, 2026-09-08
    Read-only local source review: app/modules/vedic/interpretation/forecastFacts.ts module contract and prompt/chat/en.ts §11 prohibit invented transits and use frozen Vimshottari intervals; logic/types.ts records unavailable transit factors; logic/policy.ts lists D1/D2/D6/D9/D10/D24, not D4 or D20. This does not verify deployed screens or demonstrate Panchanga, Muhurta or Sade Sati outputs.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