The VLTD Backend: State Servers, Registration, Renewal and Status
The VLTD backend is the state government server your tracking device has to report into. It is separate from your vendor dashboard, and it is the one the RTO checks.
Almost every "my device is fitted but the vehicle still shows non-compliant" problem is a backend problem rather than a hardware one. This page covers what the backend is, how a device gets on it, and what renewal actually pays for.
What the VLTD backend actually is
AIS-140 does not just require a vehicle to be tracked. It requires the tracking data to reach the state, so each state operates a backend control centre that receives location, speed and panic-button events from every registered device in that state.
Your device therefore transmits to two places at once. One stream goes to your vendor platform, which is what you log into. The other goes to the state backend, which is what enforcement and the RTO see.
The distinction matters because only the second one counts for compliance. A device showing perfect live tracking on a vendor app while failing to reach the state backend is, as far as the RTO is concerned, not fitted at all.
Why the backend is state-specific
There is no single national VLTD backend. Each state transport department runs its own, which is why the procedure, the portal and the approved vendor list all change when you cross a border.
That has three practical consequences for an operator:
- A device registered on one state backend is not automatically registered on another. A vehicle re-registered in a new state generally has to be mapped again.
- Vendors are approved per state. A vendor legitimately on the approved list in one state may not be on it in the next.
- Portals differ. Status checks, login and renewal all live in different places depending on the state, which is what the state guides below cover.
How a device gets onto the backend
Fitting the hardware is the first of several steps and the only one most operators are aware of.
The failure point is almost always the middle two. The device works, the invoice is paid, and nobody confirmed the state backend is receiving anything.
- The device must be AIS-140 type-approved, and in most states also on that state's approved vendor list.
- It is then mapped to the vehicle registration number on the state system, usually by the vendor or the fitment centre rather than by you.
- The state backend has to start receiving data from it. Until packets actually arrive, the mapping is a record with nothing behind it.
- The compliance record is then reflected against the vehicle, which is what a fitness or permit check reads.
Fitted but showing non-compliant
This is the single most common VLTD complaint, and the causes are boringly consistent.
The test is not whether your app shows the vehicle. It is whether the state portal shows recent data. Those are different systems and they disagree more often than operators expect.
- The device was never mapped to the registration number, only installed.
- The SIM or data plan lapsed, so transmission stopped. The device still powers up and still shows a light.
- The vendor was removed from the state approved list after fitment.
- The vehicle moved states and was never re-registered on the new backend.
- Transmission is intermittent, so the record exists but the last-seen timestamp is old enough to read as inactive.
Renewal, recharge and what you are actually paying for
VLTD costs recur, and the terminology confuses people because two different things get called renewal.
The first is the device's connectivity and platform subscription, often called a recharge. This keeps the SIM active and the data flowing. Let it lapse and the vehicle silently stops transmitting to the state backend, which is the lapsed-compliance scenario above.
The second is any state or certification-related renewal, where the state requires periodic revalidation of the fitment or the certificate.
Charges vary by state and by vendor and they change, so confirm the current figure with your vendor and your state transport department rather than relying on any published number, including one on this page. What is worth fixing is the process: renewal dates should sit in the same place as your fitness, permit and insurance expiries, because the consequence of missing this one is identical.
Checking status without waiting for a check-post
Most states expose a status lookup that shows whether a vehicle is registered and when data was last received.
Check the last-received timestamp rather than only the registration status. A vehicle can be correctly registered and have stopped transmitting weeks ago, and only the timestamp reveals it.
For a fleet, doing this by hand does not scale, and it is not a check anyone remembers to run monthly. It belongs alongside your other document expiries. Our AIS-140 GPS tracking reports transmission health directly, so a vehicle that has gone quiet surfaces before it is stopped.
State-by-state procedure differs; the guides below cover the portals individually.
Frequently asked questions
What is the VLTD backend?
The VLTD backend is the state government control centre that receives location, speed and panic-button data from every AIS-140 device registered in that state. It is separate from your vendor dashboard, and it is the record the RTO and enforcement check against.
Why does my VLTD show as non-compliant when the device is fitted?
Usually because the device was never mapped to the registration number on the state backend, or because the SIM or data subscription lapsed and transmission stopped. The device still powers on in both cases, so the fault is invisible from the vehicle.
What are VLTD renewal charges?
Renewal normally covers the device connectivity and platform subscription that keeps data flowing to the state backend, and in some states a periodic revalidation of the fitment. Amounts vary by state and vendor and change over time, so confirm the current figure with your vendor and state transport department.
What does VLTD device recharge mean?
It refers to renewing the device's data or service plan. If it lapses the device stops transmitting to the state backend, and the vehicle reads as non-compliant even though the hardware is installed and working.
Is the VLTD backend the same in every state?
No. Each state transport department runs its own backend, with its own portal, procedure and approved vendor list. A device registered in one state is not automatically registered in another, so a vehicle moved between states generally has to be mapped again.
How do I check whether my VLTD is transmitting?
Use your state portal's status lookup and read the last-received timestamp, not just the registration status. A vehicle can be registered correctly and have stopped transmitting weeks earlier, and only the timestamp shows it.