Vehicle Number Numerology: What Counts on a Plate

Vehicle number numerology, also called car number numerology, sums the digits printed on a number plate down to a single digit. It then checks that digit against the owner's birth numbers. Take RJ14 CD 4521, the plate in our API reference. Our API adds 1, 4, 4, 5, 2 and 1 and gets 17. Then 1 + 7 gives 8, the number of Saturn.

The letters get no value. RJ is the state code for Rajasthan, and CD is the series. Our API sets both aside and names each letter in ignored_letters. The 14 between them is the code of the transport office that registered the car. Those two characters are digits, so they count. Bike plates follow the same rule, and so do house numbers.

Guides do not agree on the letters. Of six guides we read, five give every letter a value and one adds only the last four digits. For RJ14 CD 4521, those rules reach 9, 7 or 3 instead of 8.

The label depends on whose birth date you send. Send John Doe's date, Aug 15, 1990, and this plate gets "Good fit". Send Jane Doe's, Mar 22, 1992, and it gets "Mixed". So an app should show the sum, the skipped letters, the method and each person's own label. It should add the API's not_claimed line, never rank plates as lucky and never let the number set a price.

Vehicle number numerology for RJ14 CD 4521, step by step

On October 19, 2026, we sent RJ14 CD 4521 to POST /v1/number as a plate (kind: vehicle). Our API reference uses this plate as its example. John Doe was the owner.

An Indian plate has four parts. Here is each part of this plate, with what our API does with it.

That leaves six digits: 1, 4, 4, 5, 2 and 1. Together they make 17. A total of two digits is added again, so 1 + 7 = 8. In Indian numerology, 8 belongs to Saturn. The 17 comes back too, in a field called compound. The API returns that value without a reading, as the compound number entry explains.

Next, the 8 meets John's numbers. John was born on the 15th. Adding 1 and 5 gives his mulank, 6. For his bhagyank, the eight digits of 15-08-1990 make 33, then 6. Our free numerology calculator works out both for any date. Venus rules 6 and treats Saturn as a friend. With a friend on both sides, the label is "Good fit". We explain that rule once, in how a phone number is read, so this post does not repeat it.

The reference also uses a US-style sample plate, ABC 4521. Its four digits make 12, and 1 + 2 gives 3, the number of Jupiter. For John, 3 is neutral. For Jane, it is a good fit.

One rule for plates, homes and phones. We also sent RJ14 CD 4521 as a mobile number. The total, the number and the fit did not move. Only kind, kind_name and the about line changed. In our code, one function adds the digits for all three kinds. Our house number numerology post runs the same rule on apartments such as B-402.

The state code never counts, the district code always does

Two plates that differ only in their state code get one answer from our API. We kept the district code, series and number and changed the state.

Our API skips both letters of each state code, so every plate lands on 8. A guide that turns each letter into its Chaldean value gets four numbers: 9, 6, 4 and 1. Under that rule, the state alone decides whether John's plate is good, neutral or not a good fit. The Chaldean sums come from that letter table. We then sent each sum to the API as a single number to read John's fit.

The district code behaves the other way around. Its two characters are digits, so each change moves the total.

Rahu (4) and Ketu (7) are not planets you can see. Both are spots at which the Moon, on its monthly loop, crosses the yearly path of the Sun. The two face each other.

Ask for the full plate. The district digits are part of the number the owner drives with. So take the registration number exactly as the plate shows it, and send all of it. If your app cuts the plate down before the call, the answer changes, and your screen should say so.

Do the letters count? Six guides, three rules

Our API never gives a plate's letters a value. The core's notes say why: sources disagree on whether those letters count. So it sets each one aside and lists it. The six guides we read show that split.

For letters, Indian numerology relies on the Chaldean table. Most Western books use the Pythagorean table instead. Our guide to Chaldean and Pythagorean letter values puts the two side by side. In Chaldean, R is 2, J is 1, C is 3 and D is 4. In Pythagorean, R is 9, while J, C and D keep 1, 3 and 4.

The top row is what our API returns. The three rows below it are the sums those rules reach, each read through the API as a single number. So one plate gets four numbers. For John, only the digits-only rule gives a good fit. For Jane, only the last-four rule does.

ABC 4521 splits the methods in its own way. A, B and C are 1, 2 and 3 in both letter tables. So both letter rules reach 18, then 9. Our API and the last-four rule both stop at 3, since the plate has no other digits.

Name the method on screen. Print the sum under the result. Beside it, add a line such as "C, D, J and R were not counted" so nothing is hidden. If you turn letters into numbers before the call, the answer stops being this method, so say that too. A user who checks the same plate on another site can then see why the two numbers differ.

One plate, typed many ways

Owners type a plate in many ways. We sent RJ14 CD 4521 in seven forms, including two with a shorter series.

Spaces and dashes drop out. A series of one letter, or none, leaves the number alone. Small letters come back small, because the list keeps the case each letter was typed in. Turn the plate into capitals before you send it. Then the skipped letters on screen match the plate.

Leading zeros add nothing. RJ14 CD 0045 and RJ14 CD 45 both make 14, then 5. Indian plates print the number with its leading zeros, and the result is the same either way.

A Bharat series plate, or BH plate, begins with digits. The series lets owners who move to a new state keep their registration. Its first two digits are the year the vehicle was registered. We sent 22 BH 4521 AA, the shape of a plate from 2022. The 2 and 2 count, so the total is 16, then 7 (Ketu). The 4521 alone would give 3. On a BH plate, the year is part of the number.

Car, bike or scooter: one kind called vehicle

Our API has a single kind for every plate, and it is vehicle. We tried car and bike as kinds. The API refused both with a 422 (invalid_input). Its message names the four kinds the route takes: mobile, vehicle, house and business. So map cars, bikes, scooters and trucks to vehicle before the call.

Bike number numerology is the same check. In India, two-wheelers carry the same four-part plate as cars. In some states, the series letters even show what type of vehicle it is. Either way, the letters are skipped. A bike's digits go through the same sum, so a two-wheeler app needs no second path.

Some plates get no answer. A plate made of letters only, such as JOHNDOE, has no digits, and it is refused with a 422. So is RJ00 CD 0000, since its zeros add nothing. Both answers explain that the plate has nothing to add apart from zeros. Hide the check when the plate holds no digit from 1 to 9.

Comparing fancy numbers without ranking them

A fancy number, also called a choice number, is a plate number picked on purpose. AstroMitra notes that many transport offices offer them for a fee. Plates are otherwise handed out in order. POST /v1/numbers checks up to 5 plates of one kind in a single call. We sent five choices from one series, first with John's birth date, then with Jane's. Here they are in the order we sent them.

Both answers came back in our order with "ranked": false. The labels moved with the buyer. RJ14 CD 0001 suits John and is mixed for Jane, and 0007 flips that. Only 9999 came back good for both. That is a fact about two birth dates, not about 9999.

Jane's numbers explain the swing. She has a mulank of 4 and a bhagyank of 1, and John has 6 and 6. We also ran the single digits 1 to 9 as plates with her birth date. Only 3 and 5 were good fits, and the other seven were mixed.

No badges and no scores. Put the API's label next to each plate, in the order the seller listed them. Stars and "lucky" tags have no place on this screen. AstroMitra's calculator rates each plate with a match score up to 100. Ours returns a label with no score, so any score in your app would be one you made up.

Never let the number touch a price. Whatever a fancy number costs in your app, the fit must play no part in it. The label changes with each buyer, so it cannot be a feature of the plate. Leave it out of prices, sort order and sales copy.

Keep it out of premiums and claims. An insurance app may offer a plate check as an extra. It must never feed a premium, a risk score or a claim decision.

Comparing uses 2 reading credits per call, so the John and Jane runs above used 4 between them. One plate on its own uses 1. A sixth plate in the same call gets a 422 back, code invalid_input.

See every field and limit. The number checks page sets out what a plate, phone or home check returns, alone or compared.

Placing the check in five kinds of app

Whose birth date to send. In the API's own words, this person is the owner. AstroMitra suggests the main driver for a family car. When the car is shared, it uses the owner on the registration. Pick one rule, and show on screen whose date was used.

Car dealer. Offer the check as an optional panel once the plate is known. It needs one input, the buyer's birth date. Ask for it inside the panel. Name, birth time and birthplace are not used.

Used-car marketplace. The plate on a listing is already fixed. Read it for the buyer who asks, behind a button. Leave the label off the public listing, since each label belongs to one buyer only.

Ride app. The check fits a driver who owns the car and is curious about their own plate. Never show riders a label for a driver's plate. Never use it to match riders with drivers.

Fancy-number app. The compare call above is the main screen: up to 5 choices, in the seller's order, each with the buyer's own label.

Hindi screens. Add lang=hi. "Vehicle number" then comes back as गाड़ी का नंबर, and "Good fit" as अच्छा मेल. The code in outcome is still good, so nothing in your app's code has to change.

Building the result card

This is the call for the plate used in our reference.

Owner: John Doe, born Aug 15, 1990. The body holds only the plate and his birth date.

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

The answer for plate RJ14 CD 4521, trimmed to the main fields

{
  "kind": "vehicle",
  "kind_name": "Vehicle number",
  "value": "RJ14 CD 4521",
  "digits": "144521",
  "total": 17,
  "compound": 17,
  "number": 8,
  "ignored_letters": ["C", "D", "J", "R"],
  "planet": "Saturn",
  "person": { "birth_date": "1990-08-15", "mulank": 6, "bhagyank": 6 },
  "fit": {
    "links": [
      { "from": "mulank", "from_number": 6, "to_number": 8, "relation": "friend", "via": [] },
      { "from": "bhagyank", "from_number": 6, "to_number": 8, "relation": "friend", "via": [] }
    ],
    "outcome": "good",
    "outcome_name": "Good fit"
  }
}

Each field has a line on the card. Start with the plate in capitals. Below it, write out the sum from digits and total: "1 + 4 + 4 + 5 + 2 + 1 = 17, then 8". Next, list the letters from ignored_letters. Then give the single digit with Saturn beside it, and the owner's label, "Good fit". The short line in fit.reading goes last.

Want the method on one page? The glossary entry on vehicle number numerology covers it with ABC 4521.

The answer ends with not_claimed. In plain words, that line calls a number a hint about leanings, never a fixed event. Keep it on each card, right under the label. A plate check is a small extra for a person who asks for it. It is not a forecast about the vehicle or its driver.

The short version

Vehicle number numerology sums a plate's digits and reads that sum for one person. Our API skips every letter, the state code and the series included, and lists them. It adds every digit, the district code included. Other guides count letters or keep only the last four digits, so one plate can get four numbers. Send the full plate in capitals, show the digits and skipped letters, and name the method. Then show each person's own label, in the order sent, and keep it away from prices, premiums and claims.