Most transport companies will tell you their trucks have GPS. That is true of almost every truck in India now. The harder question is what happens with that GPS: who looks at it, how often, and what they do when something is wrong at two in the morning.
This is how we answer it at Aditya Logistics. We built our own fleet system in 2026 because the tracking apps we had showed a dot on a map and nothing more. Here is what it does, and what we learned building it.
One truck, several trackers
Many of our trucks carry more than one tracking device. There is our own GPS unit, a second tracker on some trucks, the telematics built in by the truck maker on our Tata trucks, and the tracker our client fits for its own system. Four feeds in all.
We first thought of the extra devices as duplicates. They turned out to be the most useful part of the system, because each one behaves differently:
- Our own units report every few seconds while the truck moves.
- Another tracker reports every few minutes once the truck is parked.
- The truck maker’s telematics reports about every quarter of an hour.
- The client’s tracker can go half an hour between reports when the truck stands still.
When all of them are live, they agree with each other to within about 70 metres. But any one of them can go quiet — a loose wire, a device that sleeps when the engine is off, a server outage at the provider. So the rule in our system is simple: every minute, the newest position from any tracker wins. A single silent device never blinds us to a truck.
Every one of those positions is saved — more than 25,000 a day across the fleet — so any trip can be replayed stop by stop long after it ends.
Trust, but check, every device
Merging devices taught us not to believe any single one blindly.
- Engine status. Some units report “engine off” all the time, even at 80 km/h. So we trust the engine signal only from a device that has proved itself: enough readings while moving at speed, with almost none of them saying the engine was off. On other devices we ignore it.
- Distance. One tracker’s odometer read 7–8% high on a few trucks. For kilometres we use a single, reliable device per truck, never a track stitched together from several.
- Built-in ETAs. One system’s “ETA” turned out to be the straight-line distance to the destination divided by 40 km/h — fine on a straight highway, wrong anywhere with a ghat. We do not use it.
None of this is visible from a dashboard. You only find it by checking the data against what actually happened.
A halt is not a traffic jam
The single most important question in line-haul is: is the truck moving towards its destination? A truck can stop for many reasons, and only some of them need a phone call.
Our system treats a stop as a halt only when the truck is really standing:
- It has to stand 45 minutes away from any hub on its route before an alert goes out.
- Creeping around within a hundred metres — moving to a different spot at the same dhaba — is still the same halt.
- A truck crawling forward with its engine on, making real progress, is in traffic. That is not a halt, and nobody is called for it.
- To count as moving again, the truck has to show it: two positions away from the spot, or one position driving well clear of it.
The system also protects itself against bad data. An alert needs a live position no more than five minutes old; if the trackers have gone quiet, the message says the GPS cannot confirm, rather than guessing. If one tracking provider goes silent for the whole fleet, trucks that only it covers are put on hold instead of flooding everyone with false alerts.
Alerts that go to the people who can fix them
When something needs attention, the system does not wait for someone to look at a screen. It sends a WhatsApp message — in Hindi, the language our drivers and supervisors speak — to the people subscribed to that alert. The main ones:
| Alert | When it fires |
|---|---|
| Dispatch created | A new trip is made, with the time the truck is due |
| Hub exit delay | The truck is still at the hub 45 minutes after dispatch, then every 30 minutes |
| Road halt | The truck has stood 45 minutes away from any hub on its route, then every 15 minutes |
| Touching point delay | A hub on the way has held the truck past its allowed time |
| Late arrival | The trip closes later than its schedule allows |
| FASTag low balance | The toll wallet falls below ₹8,000 |
The road halt alert comes with two buttons: one to say the matter is resolved, which stops the alerts for that halt, and one to keep them coming. When an alert needs a person urgently, the system can also ring their phone with a spoken message in Hindi — one call per incident, inside calling hours.
ETAs from trucks that went before
When a truck halts, everyone wants to know when it will arrive. We answer from history, not geometry.
For each spot on a route, our system knows how long earlier trucks on the same route took to reach the destination from that spot. The ETA in an alert is the middle of at least five such trips. If there is not enough history for a spot, the alert does not invent a time.
Every forecast is stored next to the real arrival, so we can measure how good our ETAs are. When we checked them, the text in the alerts was right every time, and the forecasts drifted mainly when a truck stopped again after the alert — which is exactly the case where a new alert takes over.
Reports that settle questions
Data is only useful if it ends arguments. Three reports do most of that work:
- Trip journey report. Every halt of 15 minutes or more on a trip, with its place and length, and halts close to a hub marked as such. It can be printed for any trip someone questions.
- Hub delay mails. When a hub holds a truck past its allowed time, a mail goes to the hub with the arrival time and hours held, while the truck is still there — not a week later.
- Dispatch reconciliation. Every dispatch in the client’s system is checked against our own records on every sync, so a trip we have not seen is caught the same day, and every trip is matched to its payment line.
The rest of the control room
Around the tracking sit the things that stop a truck in other ways: the FASTag wallet, with every one of our toll crossings matched to its truck and trip; the papers of every truck with their expiry dates, sent as one PDF on WhatsApp when someone asks; and fuel figures from the truck maker’s telematics. Staff sign in with a one-time WhatsApp code, see only what they are allowed to, and every change is written to a log that cannot be edited.
What this means for a customer
You should not have to care about any of the above. What you should notice is:
- You hear about a delay from us, before you have to ask.
- When you question a trip, you get a report with times and places, not an opinion.
- The papers for any truck on your contract arrive in minutes.
That is the standard we hold ourselves to. If you want it on your freight, see our services or send us your routes.