Back to Home

How Naamrit Calculates Suggestions

Calculation, tradition, editorial content, and family preference

Naamrit combines software calculations with tradition-based mappings, catalog content, and family choices. The result is a comparison aid, not a canonical ruling, scientific measure, or prediction.

Birth date, time, and location

The child’s date and optional local birth time are converted to UTC using the timezone resolved from selected city coordinates. The server uses geo-tz 8.1.7 for that lookup. If no city is selected, it assumes Asia/Kolkata. The conversion uses a two-pass IANA timezone offset calculation; daylight-saving gaps and repeated local times have not been separately validated.

City selection supplies city-level latitude and longitude from the selector, not hospital-level coordinates. With both coordinates, the service applies a topocentric correction and assumes an elevation of 0 metres. Without coordinates, it calculates geocentrically. The timezone shown beside the city is informative; the server independently resolves its timezone from the submitted coordinates.

The Moon’s longitude is calculated with Swiss Ephemeris through sweph 2.10.3-5, explicitly using the Moshier ephemeris and Chitrapaksha/Lahiri sidereal mode. The app rejects impossible calendar dates and expects dates in YYYY-MM-DD form.

These software settings describe the current implementation; they are not an independent accuracy guarantee. The ranking formula does not have a separate API version token.

What happens when details are missing

No birth time: the service estimates the Moon position at local noon in the selected or default timezone. That estimate does not establish the actual birth Pada. All four candidate syllables receive equal treatment in name ranking.

No selected city: the service uses Asia/Kolkata and a geocentric Moon position. It does not apply a topocentric correction.

If time is known but location is not, the time is interpreted in Asia/Kolkata. If location is known but time is not, the service uses local noon for that location and still applies the topocentric correction.

From longitude to Nakshatra and Rashi

The calculated sidereal longitude is normalized to 0–360°. The app divides it into 27 equal Nakshatra bands of 13°20′, then divides each band into four Pada intervals of 3°20′. The four associated syllables come from Naamrit’s mapping table. Rashi is mapped from the same longitude using twelve 30° bands.

Boundaries are assigned by a floor calculation. There is no uncertainty buffer around a boundary, so small differences in time, timezone, coordinates, or calculation can change a result that is close to an edge.

The Tithi, Vara, Yoga, and Karana summaries in Pandit Insights remain date-only approximations; they do not use the selected birth time or location.

How the 0–99 name ranking works

The current rule-based ranking starts at 40 raw points and adds applicable signals:

  • Parent zodiac match: +15 for each parent; parent-element affinity: +8 for each parent.
  • Name numerology compared with the child's date-derived life-path value: +10 for an exact match, or +5 when the difference is 1–2.
  • Lo Shu: +10 when the name value is missing from the child's grid and +5 when it is dominant; these can stack.
  • Nakshatra syllables: with a supplied birth time, +30 for the calculated Pada syllable or +8 for another listed syllable; without time, +14 for any of the four.
  • Pandit mode: +20 for a recognized origin. Optional Gotra adds +0, +2, +5, or +8 by blessing level. Sibling context adds +0 to +8, with −5 for a Rashi caution.

Raw points are scaled as round(points ÷ 177 × 99), then bounded to 0–99. The 177-point divisor is the fixed theoretical maximum. Missing optional details do not incur a penalty, but their bonuses cannot be applied.

These weights are Naamrit’s product rules, not a universally accepted Vedic formula. The separate 0–100 Name Insights index uses a different calculation and is not this ranking score. Individual factor contributions are not shown on each name card.

What is calculation—and what is interpretation

Calculated: date fields, timezone conversion, Moon longitude, Nakshatra/Pada bands, Rashi bands, date-derived numerology values, and the deterministic ranking formula. The same valid inputs produce the same score under the same software versions.

Tradition-based mapping: the association of Nakshatra Padas with starting syllables and other cultural classifications. Practices can vary by lineage and teacher; Naamrit does not speak for a specific tradition.

Editorial catalog: name meanings, origins, transliterations, and regional variants are catalog content, not outputs of the Moon calculation. Source-page citations are not currently displayed for every entry.

Family preference: gender, preferred initial, Gotra, and sibling context are optional inputs. They influence filtering or ranking, but the family makes the final choice.

Reproducible example

Illustrative input: 1 January 2024, 12:00 local time, New Delhi (28.6139° N, 77.2090° E). The server resolves Asia/Kolkata and converts this to 06:30 UTC. The current calculation returns sidereal Moon longitude 134.514407°, which maps to Purva Phalguni, Pada 1, syllable “Mo”.

With the same date but no time and no city, the service assumes local noon in Asia/Kolkata and calculates geocentrically. The result is 135.005556° and still maps to Purva Phalguni, Pada 1; however, because the actual birth time is unknown, the Pada is not treated as confirmed and all four syllables are weighted equally.

Both examples are asserted by the API server’s methodology fixture. They demonstrate the current implementation; they are not a practitioner-validated accuracy benchmark.