Vahan VLTD Registration: Step-by-Step Guide for Fleet Owners and Dealers
Vahan VLTD registration is the process of linking an AIS-140 vehicle location tracking device to a specific vehicle in the national Vahan database and the state monitoring backend, so the RTO sees an activated device when it processes registration, fitness or a permit. This guide explains how the linkage works, who does what, which documents are usually needed and how to fix common errors - and reminds you to confirm state-specific rules with your transport department or RTO.
By GPSBULL · Updated 2026-08-15 · Manufacturer of AIS-140 certified VLT devices, New Delhi
What Vahan VLTD registration actually links together
When people say "Vahan VLTD registration", they mean the chain of records that lets an RTO see a working tracker against a vehicle. Four things get tied together:
- The device - make and model, a unique device ID, the IMEI and the SIM's ICCID. Vahan accepts only models whose type approval has been uploaded by a testing agency.
- The vehicle - a new vehicle is tagged by chassis or engine number before registration; a retro-fitted vehicle is tagged by its registration number.
- The SIM / M2M connection - mobile number, IMSI and provider. State SOPs may also require a minimum plan validity. West Bengal's SOP, for example, asks for two years on a public service vehicle less than eight years old and one year on an older one - check what your own state expects.
- The backend - the state monitoring centre that receives AIS-140 data, checks health packets and the panic button, and pushes the activation status back to Vahan.
Only after the state backend confirms activation can the VLTD fitment certificate be generated from Vahan. That certificate is what the RTO looks for while processing registration, fitness (CF) or a permit.
Why the device must be AIS-140 type approved
Under CMVR Rule 125H, public service vehicles (as notified, with exemptions such as two- and three-wheelers) must carry a vehicle location tracking device and one or more emergency buttons meeting AIS-140. Vahan validates the make and model against type-approval data uploaded by testing agencies referred to in CMVR Rule 126, so a non-approved tracker simply cannot be tagged. GPSBULL's AIS-140-4G tracker (model TRP-4G), for example, carries ARAI type approval TAC AS9026, which is the kind of entry Vahan checks against.
Who does what: manufacturer, fitment centre, dealer and owner
VLTD manufacturer
Gets the model type approved, uploads the TAC on the NIC Vahan / VLTD Maker portal, receives credentials and uploads device inventory (make, model, unique ID, IMEI, ICCID). Also adds approved dealers on the state backend, supervises their work and answers to the transport department for service quality.
Fitment centre or authorised dealer
Installs the VLTD and panic buttons, links the vehicle with the IMEI in Vahan, enters the same details on the state backend, verifies the owner's mobile number by OTP, gets the fitment inspected and downloads the fitment certificate. State SOPs (West Bengal's, for example) expect a dealer to have a local office with GST registration, trained technicians and a customer-support phone number.
Vehicle OEM (new vehicles)
For factory-fitted devices, the vehicle manufacturer or its authorised agency tags the device against the chassis or engine number before the vehicle is registered.
Vehicle owner or permit holder
Chooses an approved model, supplies KYC and RC details, receives the activation OTP, presents the vehicle for inspection, keeps the device powered and untampered, and renews the subscription (yearly, where the state requires it) before the fitness test.
Motor Vehicle Inspector and RTO
The MVI/AMVI checks mounting, wiring, panic buttons and live location in a departmental app; the RTO then approves registration or CF in Vahan.
Step-by-step: how a VLTD is linked and activated on Vahan
Screens differ from state to state, but the flow described in state SOPs generally runs like this:
- Choose an approved device. Type approved nationally and, where the state keeps its own list, empanelled with the transport department. Ask for the TAC number.
- Book a fitment centre. The manufacturer's authorised dealer schedules installation and collects your RC and KYC.
- Install the VLTD and panic buttons. Device mounted out of passengers' reach with the IMEI label visible and no metal shielding; buttons positioned as AIS-140 and your state SOP require - typically at least one on each passenger row in cars, a dedicated one for the driver, and buttons within easy reach along both sides of a bus.
- Link vehicle and IMEI in Vahan. The dealer selects the vehicle by registration number (or chassis number for a new vehicle) and enters the unique ID, IMEI and ICCID.
- Tag on the state backend. Enter IMEI, model code, M2M provider, SIM number/IMSI, vehicle type/make/model and permit-holder details, then save.
- Owner OTP. The owner's mobile number is verified and installation status updated.
- Backend checks. The monitoring centre confirms AIS-140 packets and health data are arriving, the SIM has the required validity and a panic press reaches the server.
- Inspection. The MVI/AMVI compares live location and last-update time in the app, presses the panic buttons and approves or rejects the fitment.
- Activation pushed to Vahan. The backend updates Vahan; the dealer downloads and uploads the fitment certificate.
- RTO processing. Registration, fitness or permit can now be approved in Vahan.
Documents and details typically needed
Requirements vary by state, but be ready with:
- Registration Certificate (RC) - or, for a new vehicle, the chassis and engine numbers.
- Owner KYC (ID and address proof) and an active mobile number in the owner's or permit holder's name for OTP.
- Permit number and holder name, where a permit exists.
- Device details from the dealer: make and model, unique ID, IMEI, ICCID, TAC number.
- SIM/M2M details: mobile number, IMSI, provider, plan validity. Devices with an embedded dual-network eSIM, such as the GPSBULL 4G AIS-140 device, still carry an ICCID and IMSI that must be recorded.
- Dealer's GST invoice and warranty note - some states insist on this.
- After activation: the Vahan fitment certificate and, where the state requires it, a yearly subscription renewal certificate.
How RTOs verify VLTD status during fitness and permit
State transport departments enforce fitment and functional status at registration, permit issue or renewal, and fitness checks. During these visits the inspector or RTO will normally:
- Look up the vehicle in Vahan or the state backend and confirm a VLTD is tagged and shows an active status.
- Match the IMEI on the installed device with the one linked to the vehicle.
- Check the last data update time and that live location matches where the vehicle actually is.
- Press a panic button and confirm the alert appears in the monitoring app.
- Ask for the subscription renewal certificate for the coming year, where the state requires one.
What causes a fitness rejection
A lapsed SIM plan, wiring disturbed during body repair, a tampered or unpowered device, panic buttons that no longer trigger, or an IMEI mismatch after an unrecorded replacement. West Bengal's SOP, for example, treats a tampered or non-functional device as a violation of permit conditions - so fix reporting issues well before your CF date.
Device replacement, upgrades and vehicle transfer
Replacing or upgrading a device
If a device fails, is stolen or you upgrade (say, from an older 2G unit to a 4G VLT device), the old IMEI must be de-linked and the new one tagged - effectively a fresh registration for the same vehicle. The dealer logs a complaint in the state backend (which helps avoid false tamper alerts), installs the replacement, links the new IMEI in Vahan and the backend, repeats OTP and backend checks, and obtains a fresh certificate. Some states may require re-inspection - ask your dealer and transport department what applies. Never let a technician swap a device without updating Vahan; the mismatch will surface at the next fitness test.
Vehicle sold or transferred
The VLTD normally stays with the vehicle, but owner and permit-holder details on the backend need to change with the RC transfer so that OTPs, alerts and renewal reminders reach the new owner. Ask the dealer to update the mobile number and permit details once the RC transfer is complete, and move the subscription into the new owner's name.
Moving to another state
Each state runs its own monitoring backend, so re-registration elsewhere usually means re-tagging on that state's backend, and the manufacturer usually needs to be approved there too. Confirm with both transport departments first.
Common errors and troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Model not found or rejected in Vahan | Type approval / CoP not uploaded, or model not empanelled in the state | Ask the manufacturer to check its VLTD Maker portal entry; verify the state list |
| IMEI already linked to another vehicle | Device re-used or earlier vehicle never de-linked | Ask the dealer or manufacturer to raise a de-link request through their portal login |
| Vehicle number not found | RC not yet in Vahan or typo | Re-check the RC; for new vehicles tag by chassis number |
| Owner OTP not received | Number differs from RC records or SIM inactive | Update the mobile number with the RTO, then repeat OTP |
| "Installed" but never "activated" | No data or health packets reaching the server; SIM validity short; panic test pending | Check power, antenna and server/APN settings; extend the M2M plan; test the panic button |
| Frequent tamper or power-cut alerts | Loose wiring or disconnection during servicing | Log a complaint before workshop visits; get wiring inspected |
Most of these are data problems rather than hardware faults, and the manufacturer's support desk can usually see both the Vahan entry and the backend record. GPSBULL, for instance, runs device support 24/7 to help dealers and fleet owners trace where a linkage is stuck.
Rules vary by state: confirm before you fit
The Vahan VLTD Maker portal and AIS-140 are national, but empanelment, backend software, inspection practice, fees and deadlines are decided by each state or UT transport department. Before you buy or fit anything:
- Confirm the manufacturer and model are approved in your state, not just type approved nationally.
- Ask the transport department or RTO which vehicle categories and deadlines currently apply to you.
- Insist that the dealer completes the Vahan link, backend tagging and OTP on the day of fitment and hands you the certificate.
- Diarise the subscription renewal a month before your fitness date.
Browse our guides library for related topics, or read about GPSBULL as an AIS-140 device manufacturer in India if you are a dealer or fleet looking at device supply.
Frequently asked questions
Can a vehicle owner do Vahan VLTD registration directly?
Normally no. Device linking on Vahan and the state backend is done by the VLTD manufacturer or its authorised dealer using secured credentials. The owner supplies the RC, KYC and a mobile number for OTP, and presents the vehicle for inspection.
How do I check whether my VLTD is linked in Vahan?
Ask your dealer for the Vahan VLTD fitment certificate, which is generated only after activation. Some state transport department portals or backends may also let you check status by registration number, and the RTO can see it during fitness or permit processing.
Why does the backend show my device as installed but not activated?
Activation happens only after the state monitoring centre confirms AIS-140 data and health packets are arriving, the SIM has the required validity and the panic button test succeeds. Check power, antenna, server settings and SIM plan, then ask the dealer to re-run the checks.
What happens to the registration if I replace or upgrade the device?
The old IMEI must be de-linked and the new device tagged to the vehicle in Vahan and the state backend, followed by OTP, backend checks and a fresh fitment certificate. Some states may also require a fresh MVI inspection - confirm with your transport department.
Does the VLTD linkage transfer when I sell the vehicle?
The device normally stays with the vehicle, but the owner and permit-holder details on the backend need to be updated after the RC transfer so OTPs, alerts and renewal reminders reach the new owner. Ask the dealer to update them and transfer the subscription.
Is the Vahan VLTD registration process the same in every state?
The Vahan VLTD Maker portal and AIS-140 are national, but each state or UT decides empanelment, backend software, inspection practice, fees and deadlines. Always confirm the current procedure with your state transport department or RTO.
Questions about your fleet? Talk to the manufacturer.
Speak directly with the manufacturer — device specifications, state-wise compliance guidance, dealer pricing and bulk quotes. Office: Monday–Saturday, 10 AM–7 PM IST. Device support: 24/7.
Related products & solutions
More guides
Official sources & further reading
- Transport Department, Government of West Bengal - Standard Operating Procedure (SOP) for VLTD Fitment and Tagging (AIS-140)
- Transport Department, Government of West Bengal - Registration of AIS-140 Compliant Vehicle Location Tracking (VLT) Device Manufacturers, Phase III
- Ministry of Road Transport and Highways - Fitment of Vehicle Location Tracking Device and Panic Buttons, letter dated 31.10.2018