The fuel receipts looked normal. That was the problem. When I talk to fleet operators in Nepal, this is almost always where the conversation starts. The bill is higher than last year. Nobody can explain why. Every driver has a reason that sounds plausible. Traffic on the Ring Road. Extra loading trips. A closed pump near Kalanki. None of it adds up to NPR 80,000 extra per month, but none of it is obviously wrong either.
After building GPS fleet infrastructure and analysing trip data from tracked vehicles across Nepal, I can tell you where that money usually goes. It is not one thing. It is three things happening at the same time, and none of them show up on a fuel receipt.
The Information Gap That Costs Money
Fleet operators in Nepal almost universally manage fuel by receipts. A driver fills up, brings back a chit, and the number goes into a ledger. What the receipt does not show is whether the engine was running for 40 minutes in a Thankot queue with no load on board, or whether the vehicle took a detour through Dakshinkali that added 18 kilometres to a route that should have been 54.
GPS tracking closes that gap. Not in theory. In the data, trip by trip.
When you look at raw GPS trip data from a long-haul fleet running routes like Kathmandu-Birgunj or Kathmandu-Hetauda, three patterns appear almost every time.
Idle Time: The Fuel That Moves Nothing
On Nepal's long-haul corridors, idle time is consistently the biggest single fuel drain that operators are not aware of. Vehicles waiting for return loads in Naubise or Simara, sitting at loading points in Birgunj, queuing outside depots with engines running because drivers are not sure how long the wait will be.
A light commercial vehicle burns roughly 0.8 litres per hour at idle. On a fleet of 14 vehicles averaging 90 minutes of daily idle time each, that is approximately NPR 47,000 per month in fuel that produces zero movement and zero revenue. At NPR 150 per litre, the calculation is straightforward. The problem is that without GPS, nobody knows the idle time is happening.
When idle alerts are set at 15 minutes, behaviour changes quickly — and the mechanism is simpler than most operators expect. Drivers start calling dispatch before waiting rather than leaving the engine running, because they know a 16-minute idle will show up in the next report with their name on it. In the fleets I have tracked, idle time drops from 90 to 100 minutes per vehicle per day to under 40 minutes within the first three to four weeks. That single change, across a mid-size fleet, recovers NPR 30,000 to 50,000 per month.
Route Deviation Compounds Every Trip
A planned route is not always the route that gets driven. On a corridor like Kalimati to Birgunj, planned distance is roughly 255 kilometres. What GPS trip data shows on unmonitored fleets running this route is actual distances running 10 to 15% higher — not on one bad trip, but consistently, across vehicles, across months.
Some deviation is legitimate. Road closures, diversions, post-monsoon detours near Hetauda. I have seen GPS tracks that make complete sense once you know a bridge was out. Some deviation is not legitimate, and the data shows that difference clearly too. A pattern of regular stops at locations that are not depots, fuel stations, or loading points looks different from a flood diversion. Both are visible in the same trip report.
Bringing actual trip distance within 4 to 5% of planned distance, which route deviation alerts make achievable, typically cuts fleet fuel spend by 8 to 12% on its own. That is before touching idle time or speed.
Speed and Fuel Efficiency on Nepal's Highways
The Prithvi Highway and the Mahendra Highway both have long flat stretches where drivers push past 90 km/h. I understand why — it feels efficient to make up time on the open road. The problem is that above 85 to 90 km/h, fuel burn per kilometre increases sharply. A vehicle that averages 80 km/h on a Kathmandu-Butwal run will use meaningfully less fuel than the same vehicle averaging 95, even if the total distance is identical.
Most fleet operators I speak to know this in principle. None of them have seen it measured against their own vehicles on their own routes until GPS makes it visible. When overspeed alerts are active at 85 km/h and drivers know the threshold, highway fuel consumption on long-haul routes typically falls 7 to 9% per vehicle. I have seen this consistently enough across different fleet types that I now treat it as a reliable baseline, not an optimistic projection.
What the Combined Numbers Look Like
Idle time reduction, route deviation control, and speed monitoring are not independent. They compound. A fleet that works on all three does not see 8% plus 10% plus 8% — the effects overlap and reinforce each other. In practice, total fuel reduction across 60 to 90 days lands in the range of 18 to 26% for fleets that engage with the data consistently.
For a fleet of 14 vehicles spending NPR 3.2 lakh per month on fuel, a 22% reduction is NPR 70,000 per month. The monthly tracking cost for 14 vehicles is NPR 56,000. The numbers work even before accounting for reduced maintenance costs from lower speeds and less idle engine wear.
I focus on these three variables specifically because they are the ones GPS data captures with precision on Nepal's road network. Fuel card fraud and odometer manipulation are real problems too, but harder to attribute with certainty from GPS alone. Idle time, route deviation, and speed are objective. The device either recorded the engine running or it did not.
Why the Data Does Not Help If Nobody Reads It
This is the part that matters more than the technology.
GPS data generates automatically. Idle time reports, trip distance summaries, overspeed logs — all of it runs in the background whether or not anyone opens the dashboard. The operators who see 20% fuel reductions are the ones who check that data twice a week and have specific conversations with specific drivers about specific events. Not general instructions to save fuel. A conversation that starts with: on Tuesday at 2:30 PM your engine was running for 48 minutes outside Narayanghat with no movement recorded. What was happening?
That conversation changes behaviour. A policy announcement does not.
What to Do With This
If your fuel costs have been rising without a clear explanation, the data to understand why is available the moment you install tracking. NepTrack's fleet management platform includes idle time monitoring, route deviation alerts, overspeed notifications, and trip-by-trip analysis built for Nepal's road network and GSM infrastructure.
The idle time calculation alone, done honestly against your current fuel spend, will tell you whether the numbers justify the tracking cost. For most fleets running long-haul routes in Nepal, they do. If you want to work through what the numbers look like for your specific fleet, get in touch directly.
