House Number Numerology for Real-Estate and Rental Apps

House number numerology, or flat number numerology for an apartment, sums the digits on a home's door. It keeps summing until a single digit remains. That digit is then read against the person who will live there. Take apartment B-402. Our API sums 4, 0 and 2 and gets 6, the number of Venus. It does not count the B. It names the letter in ignored_letters instead, so the buyer can see what was left out.

Dashes, slashes and spaces drop out as well. Every digit you send is added, though, so the input decides the answer. Apartment 1504 adds up to 10, which gives 1. Sent as T3-1504, with the tower number in front, it adds up to 13, which gives 4. Letters are the other split. Of four guides we read that explain the method, three give a letter a value and one skips it.

The reading depends on the buyer, not the apartment. For John Doe, born Aug 15, 1990, B-402 is a good fit. For Jane Doe, born Mar 22, 1992, the same apartment comes back mixed.

So a real-estate app should show four things: the digits counted, the letters skipped, each buyer's own fit and the API's not_claimed line. It should never let the number rank a listing or touch its price.

House number numerology for unit B-402, step by step

We ran B-402 through POST /v1/number as a house number on October 19, 2026. It is the house number example in our API reference. The owner was John Doe.

John's mulank comes from his birth day, the 15th: 1 + 5 = 6. His bhagyank, the sum of every digit in his birth date, is 6 as well. A buyer can find both on our free numerology calculator. Here the unit's number matches both of John's numbers. The API marks each link same. A same link is treated like a friendly one, so the result is good.

Since 6 has one digit, compound comes back as null. A total from 10 to 52 fills it. The compound number entry explains that field.

A house uses the same route and the same digit rule as a phone. We sent 402 as a mobile number too, and it came back as 6 with the same fit. Only three fields differ: kind, kind_name and about. For a house, kind_name reads "House number", and the about line tells the user that letters are left out.

How the fit turns two links into one label is set out in our mobile number numerology post. This post stays on what is new for homes: letters, floors, towers and buyers.

One apartment, eight ways to write it

A listing can write one unit in many ways. We sent apartment B-402 in eight forms, plus a full address line.

Labels such as "Flat" and "Tower" cost nothing, because their letters are skipped. They do fill ignored_letters, though. The list keeps each letter once and keeps its case, so "Flat B-402" sets aside B, F, a, l and t.

The full address is the row that moves. Its PIN code, India's postal code, is 411001. That adds 7 more, so the total climbs to 13 and the number lands on 4. The same thing happens in a US listing. Apt 12A gives 3. The whole line, "Apt 12A, 100 Main Street, New York, NY 10001", gives 6.

Give the unit its own field. Ask for the unit apart from the street, then send that field alone, as it appears on the door. Then ignored_letters holds only the unit's own letter, and you can show it back to the buyer.

Do letters count? The guides split, and our API skips them

Our API never counts a letter in a house number. The core's notes give the reason. Sources do not agree that letters count, so the API sets every letter aside and names it.

Four outside guides show the split.

Indian numerology works with the Chaldean letter table. There, A counts 1, B counts 2 and G counts 3. As the 7th letter of the alphabet, G would be 7 under the first rule. Here is what each rule does to three kinds of unit.

Only the first column is our API's answer for these units. The other two columns are the sums those rules give. We read John's fit for each sum through the API, as house numbers 4 and 8.

For 12A, one letter moves John from neutral to good. For G-01, the three rules give three numbers: 1, 4 and 8. Say the G stands for the ground floor, not a unit. None of the guides we read tells a floor code apart from a unit letter, and our API cannot either. Its answer is to count none of them and list every one.

So be open about the method. Show the skipped letters under the result. For G-01, print a note like "We added 0 and 1. The G was left out." If you turn letters into digits before you send them, the answer is no longer this method. Say so on screen. Names have the same kind of split, as our post on calculators that disagree shows.

Floors, towers and slashes

Where a tower numbers its apartments by floor, 1504 means floor 15, unit 04. Our API does not split the floor from the unit. It adds all four digits. We ran seven forms.

Two of these numbers belong to Rahu (4) and Ketu (7). Neither is a body you can see. Each is a point where the Moon's path cuts across the Sun's.

A tower letter adds nothing, so C-1504 still lands on 1. A tower number is a digit, so T3-1504 gains a 3 and lands on 4. For John, that one digit turns "Not a good fit" into "Good fit". Both sums are right for what was sent.

Two of the guides say which number to use for an apartment, and both point to the unit. TogetherBuying says to use the apartment number, not the building number. KundliGPT says to use the number that leads people to your front door. Neither one splits the floor out of the apartment number.

So send the unit number as the door shows it. Leave out the tower, wing, building, street and PIN code. If a listing writes the tower into the unit, as in T3-1504, decide which part is the unit. Then use that rule for every listing.

Slashes and long city-style numbers keep every digit. A plot number such as 12/3 gives 6. A number such as 8-2-293/82/A adds up to 34, then 7, and its A is set aside. The 34 also comes back as compound, which the API returns but does not read.

The fit belongs to the buyer, not the listing

A buyer with a shortlist wants every apartment on it checked. POST /v1/numbers takes as many as 5 values of a single kind per call. We sent the same five apartments twice, once for John and once for Jane.

Both answers kept our order and said "ranked": false. The labels changed with the buyer. Apartment 12A is neutral for John and a good fit for Jane. B-402 is the other way around: good for John, mixed for Jane. Only A-1103 and D-707 came back good for both.

Jane's numbers explain the change. Her mulank is 4 and her bhagyank is 1, while John's are both 6. Her two planets judge many numbers in opposite ways. We checked house numbers 1 to 9 for her, and 7 of the 9 came back mixed.

That makes the fit a fact about one home and one person, never about the home alone. Three rules follow for a listing site.

Keep the fit off the listing. Do not print it on the listing card, where every visitor would see one label. A label that changes with each visitor is not a feature of the home.

Keep it out of search order. Never use it in a sort, a quality score or a "lucky home" badge. The API gives no rank, and three of John's five apartments tie as good fits.

Keep it away from price. A seller cannot set a price by a number whose reading changes with each buyer. Agents should not use it in a pitch, and it should play no part in a sale. The choice of home stays with the buyer.

A couple buying together gets one call per person. Show the two columns side by side, as in the table, and never merge them into one label. Matching two people with each other is a different check, covered in our numerology compatibility post.

Each compare call takes 2 reading credits, so the two buyers above took 4. A single check takes 1. Send six apartments in one call, and you get a 422 error, code invalid_input.

Plan the whole feature. Our number checks page lists what both routes return for a house, a phone or a plate, with the limits.

Where the check sits in a real-estate app

On the listing page, behind a button. Add a panel such as "Check this home's number" that opens only when the buyer asks for it. It needs one input from the buyer, the birth date. A name, a birth time and a birthplace are not used. Ask for the date inside the panel.

On the shortlist. Send up to 5 shortlisted homes in one compare call, in the buyer's own order. Put the API's own label next to each home, and add nothing that picks a winner.

In a rental app, read it for the tenant. Our API calls this person the owner, but it means the person the number is read against. PanchangBodh, one of the guides we read, speaks of the residents' numbers. For a rental, that is the tenant who will live there, not the landlord.

In an interior design app, add no fixes. The answer holds the digits, the planet, the fit and a short line. It has no remedies and no decor tips. If your app shows any, they are your content, not the API's.

Homes with no number. A house known only by a name, such as Rose Villa, gets a 422 error, code invalid_input. So does G-00, since zeros add nothing. Hide the panel when the unit field holds no digit from 1 to 9.

Hindi screens. Add lang=hi, and "House number" comes back as मकान नंबर, with "Good fit" as अच्छा मेल. The outcome code is still good, so your app's logic is untouched.

Vehicle plates use the same route with kind set to vehicle.

What one result card shows

Here is the request for the reference's sample apartment.

John Doe, born Aug 15, 1990. The request sends the unit and his birth date, and nothing more.

curl -X POST "https://apiforastrology.com/api/numerology/v1/number" \
  -H "Authorization: Bearer $ASTROLOGY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"house","value":"B-402","birth_date":"1990-08-15"}'

The answer for apartment B-402, trimmed to the main fields

{
  "kind": "house",
  "kind_name": "House number",
  "value": "B-402",
  "digits": "402",
  "total": 6,
  "compound": null,
  "number": 6,
  "ignored_letters": ["B"],
  "planet": "Venus",
  "person": { "birth_date": "1990-08-15", "mulank": 6, "bhagyank": 6 },
  "fit": {
    "links": [
      { "from": "mulank", "from_number": 6, "to_number": 6, "relation": "same", "via": [] },
      { "from": "bhagyank", "from_number": 6, "to_number": 6, "relation": "same", "via": [] }
    ],
    "outcome": "good",
    "outcome_name": "Good fit"
  }
}

Build each result card from this answer, top to bottom. Show the unit as sent, B-402. Under it, print what was added, "4 + 0 + 2 = 6", from digits and total. Then show the letters set aside, here only the B. Add the number and its planet, 6 and Venus, and the buyer's label, "Good fit". Finish with the short reading from fit.reading.

For a one-page summary, our glossary page on house number numerology sums up the method with B-402.

The not_claimed field comes with every answer. In plain words, it says a number points to a leaning, not to events in the home. Print it on every card, close to the label. A house check is one input to a buyer's choice. It cannot tell them how life in that home will go.

The short version

House number numerology sums the digits of one unit and checks the result against one person. Our API sets letters aside, names them and counts every digit it receives. That puts your form in charge of the answer. Send the unit as the door shows it, without the tower, street or PIN code. Put the digits and the skipped letters on the card. Then read the fit for each buyer, and keep it away from listings, search order and price.