---
title: "The Three Lhosars of Nepal (尼泊爾三洛薩)"
method: GET
path: "/api/trpc/threeLhosars.year"
tags: ["Nepali"]
---

# The Three Lhosars of Nepal (尼泊爾三洛薩)

`GET /api/trpc/threeLhosars.year`

## Request

- Base URL: `https://api.asktian.com`
- URL: `https://api.asktian.com/api/trpc/threeLhosars.year`
- Auth: HTTP bearer

THE THREE LHOSARS OF NEPAL — one word, three new years: Nepal’s holiday calendar carries TAMU LHOSAR (Gurung), SONAM LHOSAR (Tamang) and GYALPO LHOSAR (Sherpa/Tibetan) on three different dates by three different rules — one solar-fixed, one lunar by the Nepali reckoning, one lunisolar by the Tibetan arithmetic. Each rule cross-locked to a catalogue engine: Tamu is POUSH 15 of the Bikram Sambat (the Nepali engine — so solar-stable it lands on 30 December year after year, asserted); Gyalpo IS the Tibetan Losar (the verified Phugpa engine, its 2024/2025 anchors re-asserted); Sonam follows the new moon of Magh, served from the published tables 2024–2027 and refused outside. THE COINCIDENCE OSCILLATION is the jewel, asserted: in 2024 Sonam and Gyalpo fell the SAME DAY (10 February, the Chinese New Year beside them); in 2025 and 2026 they split a FULL MONTH (gaps asserted); in 2027 they agree again (7 February) — two lunar reckonings drifting together and apart, the intercalation heartbeat visible in a national holiday calendar. Nepali becomes three. Pure compute and served tables, no LLM.

Cost: 1 TIAN Points per call. tRPC procedure `threeLhosars.year`.

## Query parameters

- `input` string

## Response `200`

tRPC result envelope

- TrpcResult: tRPC HTTP response envelope.
  - `result` object
    - `data` object: The procedure's return value (system-specific).

---

[API](https://skmtc.dev/asktian/apis/asktian-metaphysics-api.md) · [All operations](https://skmtc.dev/asktian/apis/asktian-metaphysics-api/llms.txt) · [OpenAPI document](https://skmtc.dev/asktian/apis/asktian-metaphysics-api/revisions/3c8fdc979206?raw)