What is Vahan?

Vahan is the national vehicle registration system under the Ministry of Road Transport and Highways. RTO registration and subsequent vehicle-related transactions contribute to the record; digitisation and available service coverage can affect what a lookup returns.

Use the official service for the required transaction. If records disagree, ask the relevant RTO or issuing authority to resolve the mismatch rather than treating a third-party summary as a correction.

Vahan handles the vehicle. Its counterpart Sarathi handles the driver, covering licences, endorsements and driving records. People frequently search one and need the other.

Choose by the task you need to complete. A search phrase such as "Vahan Beta" does not by itself identify the correct current service or login.

• For vehicle-information services, start at Parivahan Sewa and select “Know Your Vehicle Details”. Follow the current authentication instructions.
• For vehicle-related applications such as a duplicate RC, address change, or hypothecation request, use VAHAN Citizen Services and the service offered for your state.
• For aggregate registration statistics, use the official Data Analytics destination linked from Parivahan; this is a different task from checking a vehicle record.
• mParivahan is the mobile app, and it carries the virtual RC and licence that are valid to present to enforcement.

A login screen does not mean you chose the wrong service: authentication requirements depend on the service. MoboSafe does not provide a Vahan login, process government applications, or take official service payments on this page.

The name is transliterated from Hindi, so there is no single correct spelling and searches split across several. Vaahan, vahaan and evaahan all refer to this same database; none is a separate system and none is an official alternative site.

Use the service links from Parivahan Sewa rather than choosing a destination by spelling alone. Follow the official portal’s instructions for any application fees; this glossary does not collect them.

e-Vahan Bima is a different thing, and the similarity of the name causes real confusion. It is the digital motor insurance certificate, issued by the insurer rather than by the transport department. Vahan will tell you an insurance policy exists and when it expires; e-Vahan Bima is the policy document itself, and you get it from the insurance company, not from a Vahan portal.

A number plate lookup returns the vehicle, not the person. This is deliberate and it is worth knowing before evaluating any service that claims otherwise.

• Make, model and vehicle class, for example LMV or commercial.
• Registration date, registering RTO and state.
• Fuel type and vehicle age.
• Insurance company and policy validity date.
• PUC (Pollution Under Control) validity.
• Registration and fitness expiry for commercial vehicles.
• Whether the vehicle is hypothecated to a financier.

Personal details may be masked or restricted, and the fields available depend on the service and record. A number-plate lookup should not be presented as a way to obtain unrestricted owner contact details.

For an individual vehicle, start with the official information service.

• Open the official mParivahan app or the “Know Your Vehicle Details” service linked from Parivahan Sewa, and follow its authentication steps.
• Enter the registration number without spaces or hyphens if the standard format is rejected.
• Read make and model, RTO, registration and fitness dates, insurance and PUC validity.
• For pending fines, use the official eChallan service.

To decode the registration series itself, meaning the state and RTO region behind a plate, use the free RC check tool, which needs no login.

If you manage repeated fleet checks, define the required fields, review frequency, and process for resolving missing records. Authorised programmatic access is a separate service question from a citizen’s portal login.

For a MoboSafe evaluation, review vehicle verification and confirm the configured source, authorised access, returned fields, batch limits, scheduling, and integration scope. Do not assume one API call provides every registration, insurance, PUC, fitness, permit, and challan field.

For document administration, fleet asset management keeps document dates and device assignments with the asset. Stored documents and expiry records do not themselves establish a live Vahan connection or complete an official renewal.

Three situations account for most usage, and all three are about avoiding a cost rather than gaining one.

Onboarding a subcontracted vehicle. A transporter hiring market vehicles is accepting liability for documents it has not seen. A lapsed fitness certificate or expired insurance becomes the hiring party's problem when the vehicle is stopped or has an incident.

Buying a used vehicle. Registration date, RTO, hypothecation status and accumulated challans are all visible before money changes hands.

Ongoing compliance. Insurance, PUC and fitness all expire on their own schedules across a fleet, and the failure mode is never the whole fleet lapsing at once. It is two vehicles out of forty, discovered at a checkpoint.

Most people give up at one of these, and each has a specific cause.

• "Details not matching": the chassis number does not match the record. Enter the last five digits exactly as printed, without spaces.
• "Record not found": the format may be rejected, or the vehicle is registered in a state whose data has not fully migrated. Try without spaces and hyphens first.
• "Backlog": the record exists in an older state system and has not migrated to the central database. Only the RTO can resolve this; retrying will not.
• Service unavailable: the state server is down rather than your record being wrong. These portals are busiest at month end.

For the full portal walkthrough see the Vahan portal services guide.

People use "Vahan" for two systems that do different jobs, which is why instructions found online often do not match what is on screen.

mParivahan and “Know Your Vehicle Details” provide vehicle information. Follow the current login or OTP requirements and review the fields available for the record; do not assume anonymous access.

VAHAN Citizen Services is the application path for supported vehicle-related transactions. Choose the state and service and follow its authentication, document, and payment instructions.

There are also dealer and RTO logins on the same portal. These are issued to registered dealers and to RTO staff, not to vehicle owners, and a citizen account will not open them. If a walkthrough tells you to log in as a dealer, it was written for a dealer.

The service list is longer than most people expect, and nearly all of it is applied for online and completed at the RTO.

• Transfer of ownership, on sale of a vehicle.
• Change of address on the RC.
• Hypothecation addition when a vehicle is financed, continuation on refinancing, and termination once a loan is closed. Termination is the one owners forget, and it surfaces years later when the vehicle is sold.
• NOC for moving a vehicle to another state, required before re-registration there.
• Duplicate RC, where the certificate is lost or damaged.
• Renewal of registration, and fitness certificate renewal for commercial vehicles.
• Road tax payment and, in some states, tax refund on inter-state transfer.

What is applied for online still generally needs documents verified and, in many states, the vehicle physically inspected. The online step books the slot and takes the fee; it does not replace the visit.

Registration, fitness, insurance, and PUC are separate records with their own validity dates. Read the dates on the applicable documents and official service rather than calculating every renewal from vehicle age alone.

Confirm the current category-specific renewal rules and process with the relevant RTO through Parivahan Sewa. A stored expiry date or fleet reminder does not renew a document, and this glossary does not establish a current validity table for every vehicle class.

The plate itself carries information, and knowing the format explains several lookup failures.

A standard number runs state code, RTO district code, series letters, then four digits: RJ 14 AB 1234 is Jaipur, Rajasthan. The state code is two letters, the district code two digits, and the series is one to three letters depending on how many numbers that RTO has issued.

Older plates may carry a single-letter series or a shorter format, and these are the records most likely to have migrated imperfectly. Newer BH-series plates, intended for owners who move between states, do not follow the state-code pattern at all: they begin with the year, then BH, then the number.

Portals differ in whether they accept spaces and hyphens, which is why the same number can fail on one service and work on another. Entering it unspaced first avoids most of it. The RC check tool decodes the state and RTO region from a number without any login.

Vahan 4.0 is the centralised version of the database. Before it, states ran their own instances, and a vehicle registered in one state was not readily visible from another.

States migrated to the central system at different times, and older records did not all come across cleanly. This is the direct cause of the "backlog" response: the vehicle is genuinely registered, but its record still sits in a legacy state system rather than the central one.

The practical consequence for a fleet is that a national lookup is now possible, but completeness is not uniform. A 2008 registration from a state that migrated late is more likely to return nothing than a 2021 registration from the same state. A blank result is not proof that a vehicle is unregistered, and treating it that way will reject legitimate vehicles at onboarding.