Official portal: vahan.parivahan.gov.in. To check RC, insurance and fitness for a whole fleet at once, see vehicle verification.
Definition
Vahan is the Indian government’s national vehicle registration database. Its API allows verification of a vehicle’s Registration Certificate (RC), insurance validity, PUC status, and pending challans from the number plate.
Vahan verification lets fleets confirm a vehicle’s documents are valid before onboarding or dispatch, avoiding fines for expired papers and reducing fraud.
Vahan is the national vehicle registration database operated by the Ministry of Road Transport and Highways. Every vehicle registered in India has a record in it, created by the RTO at registration and updated through the vehicle's life.
It is the authoritative source. A state RTO record, an insurance record and a dealer record can all disagree; Vahan is what a permit, fitness or enforcement check is run against.
Vahan handles the vehicle. Its counterpart Sarathi handles the driver, covering licences, endorsements and driving records. People frequently search one and need the other.
"Vahan" is not one website, which is why searches for Vahan Beta, Vahan Citizen and Vahan Analytics all end up in different places. There are four destinations and they do different jobs:
If you are trying to look up a vehicle and landed on a login screen, you are on the transactional portal and want the public lookup instead.
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.
That matters mainly because the spelling variants attract lookalike sites. The government services sit on parivahan.gov.in and its subdomains, and anything asking for payment to show you a vehicle record is not one of 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.
Owner name is partially masked and personal contact details are not returned at all. Any service promising full owner details from a plate is either misrepresenting what it does or handling data it should not be.
For a single vehicle the free public route is enough.
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.
Manual lookups work for one vehicle. They do not work for a transporter onboarding forty subcontracted vehicles, a fleet re-verifying insurance across two hundred trucks each quarter, or an institution checking every bus before a school term.
The Vahan API is the programmatic route to the same records. Instead of a person typing plates into a portal, a system queries the government source directly and returns structured data.
MoboSafe provides this as a service. We connect to the government sources through secure APIs and return RC status, insurance validity, PUC status, fitness certificate expiry and challan history, for a single vehicle or in bulk. It is available through the platform and as an API for integration into your own systems, so verification can sit inside your onboarding or dispatch flow rather than beside it.
A single call returns the full document picture for a registration number: RC status and ownership category, insurance company and policy validity, PUC validity, fitness certificate expiry, hypothecation status, permit details for commercial vehicles, and challan history. The same call runs against one plate or ten thousand.
Typical uses are onboarding checks on market vehicles before a load is released, scheduled re-verification so an expiry surfaces before dispatch rather than at a check-post, and embedding verification inside a product of your own — used-vehicle marketplaces, lending and insurance underwriting all run the same lookup.
See vehicle verification for the vehicle side, and driver verification for licence and challan checks against Sarathi. For access, book a demo with the volume you expect, or see pricing.
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.
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 the "Know Your Vehicle Details" page are the read side. No login, no account, one plate at a time. This is what you want if the question is simply whether a vehicle's papers are current.
Vahan Sewa, at vahan.parivahan.gov.in, is the transactional side. It needs a citizen login, created against a mobile number and verified by OTP, and it is where applications and payments happen. Nothing on the read side requires it.
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.
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.
Most Vahan questions from fleets are really questions about when a document expires. The timelines differ sharply between private and commercial vehicles.
A private vehicle is registered for fifteen years, then renewed in five-year blocks subject to a fitness test. A commercial vehicle carries a fitness certificate instead: two years from new, then renewed annually once the vehicle passes eight years.
That annual cycle is why commercial fleets get caught. A forty-vehicle fleet has forty independent fitness dates, and the practical failure is always two or three vehicles that lapsed quietly, not a fleet-wide event.
Vehicle age also drives the scrappage regime, where commercial vehicles face mandatory fitness testing at fifteen years and private vehicles at twenty. The vehicle age and scrappage checker works this out from the registration date.
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.
Vahan is the Indian government's national vehicle registration database, operated by the Ministry of Road Transport and Highways. Every registered vehicle has a record created by the RTO at registration, and it is the authoritative source that permit, fitness and enforcement checks are run against.
No. Owner name is partially masked and personal contact details are not returned. You can see make and model, vehicle class, registration date and RTO, fuel type, insurance and PUC validity, fitness expiry for commercial vehicles, and hypothecation status.
Yes. The Vahan API is the programmatic route to the same records, used where manual lookups do not scale. MoboSafe provides bulk and single-vehicle verification through secure government APIs, returning RC status, insurance validity, PUC, fitness expiry and challan history, available in the platform and as an API for integration into your own systems.
Vahan covers the vehicle: registration, ownership, hypothecation, fitness and permits. Sarathi covers the driver: learner and permanent licences, renewals, duplicates and endorsements. Vehicle questions go to Vahan, driver questions to Sarathi.
Usually the chassis number does not match the record. Enter the last five digits exactly as printed with no spaces. If the registration number itself is rejected, try it without spaces or hyphens, since format handling varies between state implementations.
Insurance, PUC and fitness expire on independent schedules, so a check at onboarding is only valid on that day. Scheduled re-verification, typically quarterly or ahead of each renewal date, catches lapses before a roadside check does.
No. Vahan is the database. mParivahan is the mobile app that reads from it, and Vahan Sewa is the portal where applications and payments are made. Lookups need no login; Vahan Sewa needs a citizen account verified by OTP on your mobile number.
Vahan 4.0 is the centralised version of the vehicle database. States previously ran separate instances and migrated to the central system at different times, which is why some older registrations still return a "backlog" response rather than a record.
Apply for hypothecation termination on Vahan Sewa once the loan is closed, using the financier's no-objection certificate, then complete verification at the RTO. It is the step owners most often skip, and it usually surfaces years later when the vehicle is sold.
Two years from new, then renewed annually once the vehicle passes eight years. A private vehicle is registered for fifteen years instead, then renewed in five-year blocks subject to a fitness test.
Begin
Join thousands of vehicle owners and businesses across every Indian state and union territory that trust MoboSafe for real-time tracking, safety, and peace of mind.