October 31, 2025, was the AIS 140 compliance deadline for commercial vehicles registered before January of that year. GPS with NavIC tracking, a panic button, and certified data transmission to the Vahan portal. Every yellow plate vehicle in the country needed certified hardware installed or the Regional Transport Office would refuse to renew its fitness certificate, which in practice means the truck sits in a yard until somebody fixes the problem.
Fleet operators spent most of last summer getting devices wired in, sometimes three or four trucks a week going through the same workshop in places like Bhiwandi or Ludhiana, just to make the cutoff. Most of them did. The part that almost nobody bothered with was figuring out what the device could actually do beyond satisfying the government’s tracking requirement. I’ve covered enough compliance rollouts in other countries to know this is how it goes. The regulator forces hardware onto vehicles, the operator pays for it resentfully, treats the whole thing like a road tax, maybe checks the login screen once. Meanwhile, the data just accumulates on a server somewhere while the real operational costs never get touched.
India’s fleet management software market sits at about USD 1.91 billion in 2026 and is projected to reach USD 3.51 billion by 2031 at a 12.96 percent CAGR, according to Mordor Intelligence. IMARC Group puts the broader fleet management market at USD 1.30 billion in 2025, growing to USD 3.04 billion by 2034 at 9.87 percent. Future Market Insights projects India will record 17.8 percent CAGR in fleet management through 2036, which would make it the fastest growing country market globally.
The growth looks real on paper, but the composition of that spending tells a different story. Almost all of it is compliance driven, operators buying the cheapest certified device that will get them through the fitness certificate renewal. A fleet coordinator I spoke to in Pune told me they spent four lakh rupees getting twenty two trucks fitted before the deadline. The vendor brought up fuel monitoring once during the sales conversation, framed it as an optional add on, nobody in the room wanted to hear about it.
Fuel runs between 40 and 50 percent of total fleet operating costs in India. That ratio has held steady for years regardless of what diesel prices do, because the sheer consumption volumes on long haul routes dwarf any per litre savings. India’s road freight carries over 65 percent of the country’s goods, nearly 2300 billion tonne kilometres every year, all of it burning diesel that somebody should theoretically be monitoring.
The pilferage estimate that keeps circulating at fleet conferences, originally from MotorIndia, is about 8 percent of all fuel filled in Indian trucks. Run that against a 20 truck operation over a month. You get 15000 to 25000 rupees per truck disappearing, 3 to 5 lakh rupees for the fleet. Some operators I’ve spoken to genuinely did not know it was that high. Others had a rough sense of it for years but wrote it off as an unavoidable line item, something you budget for the way you budget for tyre wear. Neither group had thought seriously about the fact that the AIS 140 device bolted to their dashboard already has the sensor inputs to catch most of it.
Capacitive fuel sensors and ultrasonic variants. Both have been sold in India for years by domestic manufacturers. Wiring one into a GPS tracking unit that is already transmitting location data to Vahan takes maybe half a day per vehicle. The sensor rides the same cellular connection the AIS 140 device already uses, just a second data stream on an existing link. The same drop off between compliance hardware purchases and fuel monitoring activation shows up in GPS fleet tracking numbers for the Indian market.
The additional hardware cost per truck is somewhere in the 3000 to 5000 rupee range depending on tank size. This is against a 15000 rupee monthly pilferage loss means the sensor pays for itself before the first month is out. That calculation has not moved many operators. The conversation at fleet level is still stuck on compliance, partly because MoRTH’s February 2026 mandate on heavy vehicle safety technology created a fresh round of regulatory urgency before anyone had time to think about what to do with the last one.
Fuel theft in Indian trucking is not a complicated crime. The most common method is still a driver with a jerry can at an overnight halt somewhere off the highway, siphoning maybe 20 or 30 litres while the vehicle sits parked from eleven at night until five in the morning. Pump attendant collusion on short fills is the other big one, harder to prove individually but obvious in aggregate when you compare billed litres against consumption data.
Detecting either of these requires nothing more than continuous fuel level readings matched to GPS location, since a drop in fuel at a spot that is not a registered filling station is about as obvious a signal as telematics gets. The fleet operators who have actually turned on fuel monitoring rarely discuss it openly. A logistics manager in Hyderabad told me his company found they were losing close to 12 percent on certain routes through central India. Two of his drivers had been selling diesel to a dhaba owner outside Nagpur, probably for close to a year, before the data flagged it. He only discovered any of this because his AIS 140 vendor offered a free trial of fuel analytics after the compliance rush wound down, trying to keep the account active.
The data architecture behind AIS 140 is worth looking at because it explains part of the disconnect. Tracking data from every compliant vehicle flows to the Vahan portal, where Regional Transport Offices can theoretically pull movement histories for audits or accident investigations. The operator’s own visibility into that data depends entirely on what tier of service they bought from their device vendor. I’ve talked to fleet owners running 30 or 40 trucks who have no login, no dashboard, no way to see where their vehicles are in real time.
They paid for a certified box that transmits to the government server, satisfies the fitness certificate check, nothing beyond that. If they want to actually use the GPS data their own trucks are generating, they need to pay again for a software subscription on top of the hardware. Consider that 11.86 crore FASTags had been issued through December 2025, according to the Ministry of Road Transport. Every one of those toll transactions creates a location timestamp. Cross referencing FASTag movement data with fuel fill records is technically possible right now, but I have not come across a single fleet operator in India doing it systematically.
Delhi NCR accounts for over 56 percent of vehicle thefts nationally. Car thefts in Delhi alone surged 52 percent in 2025, with ZIPNET logging 2529 cases between January and July versus 1662 in the same stretch the previous year, per Business Standard’s reporting. Vehicle theft draws police attention, media coverage, NCRB statistics. Fuel theft generates none of that. It moves too slowly, in amounts too small per incident, spread across too many fill ups for any individual case to justify a complaint.
Twenty trucks over twelve months, though, the cumulative fuel loss on a badly monitored fleet will often run higher than the replacement value of a stolen vehicle. The February 2026 MoRTH mandate on heavy vehicle safety technology is now pushing yet another round of hardware installations, most of which will support the same unused auxiliary sensor inputs that the AIS 140 devices already have.
The fleet management market projections from Mordor Intelligence, IMARC, and Future Market Insights all point upward, 10 to 18 percent growth depending on how you measure it. Almost all of that growth traces back to regulatory compulsion rather than operators voluntarily investing in operational visibility. Fitness certificate enforcement keeps tightening through 2026 via RTO audits. Trucks will keep getting devices bolted on. Whether anybody connects a fuel sensor to those devices is a question nobody at MoRTH is asking, and most fleet operators have not gotten around to answering.
