Skip to main content
AstroOne
🇺🇸EN

Sign in

Forgot password?
🔯
Myanmar Astrology / Mahabote

Mahabote calculation walkthrough

Learn the Myanmar Astrology / Mahabote methods AstroOne actually uses, with extra care where traditional schools differ.

Calculation fact

Do the Mahabote arithmetic explicitly

The current method subtracts the weekday code from the Myanmar year and takes modulo 7. Implementations that can return a negative remainder should normalize the modulo.

index = ((MyanmarYear − weekdayCode) mod 7 + 7) mod 7
AstroOne method

How AstroOne maps indices 0–6

The current service maps 0 Binga, 1 Atun, 2 Yaza, 3 Adipati, 4 Marana, 5 Thike and 6 Puti. This mapping is locked as calculation output.

  • 0 Binga · 1 Atun · 2 Yaza · 3 Adipati
  • 4 Marana · 5 Thike · 6 Puti
Limitation

Do not replace the calendar step with a fixed year shortcut

The course does not teach a shortcut such as “Gregorian year minus 638/639” as the universal Mahabote formula. AstroOne converts the actual date through its Myanmar-calendar algorithm and uses the resulting Myanmar year.

Worked example

1990-05-14 → Puti

  1. Input

    Fictional birth date = 1990-05-14.

  2. Calculation

    Engine conversion gives Myanmar year 1352 and Monday weekday code 2. (1352 − 2) mod 7 = 6, so the placement key is Puti.

  3. Factors to inspect

    Inspect Myanmar year 1352, weekday code 2, remainder 6 and the mapping table.

  4. Reasoning

    Puti is the arithmetic result. A personality sentence does not emerge from the formula itself; that belongs to the interpretation layer.

  5. Synthesis

    Only after obtaining Puti should AstroOne’s editorial interpretation and other supported signals be added as separate layers.

Interpretation

Interpretation: the calculation establishes only “Puti.” What Puti means is a subsequent interpretive layer, not a certainty generated by arithmetic.

Methodology sources

These are the main technical, historical or interpretive references used to verify the lesson. AstroOne behavior is cross-checked separately against the current implementation and verification checks.

← Back to track