GPS telematics for a fleet — Wialon wired into trips
The challenge
A fleet of 10 trucks. The dispatcher logged arrivals, mileage and remaining fuel by hand from drivers’ calls — late and error-prone. Fuel theft surfaced after the fact, and trip economics (how far it really drove and burned) were guessed. The system needed to pull the facts straight from GPS.
What was built
Wialon (GPS and telemetry) was integrated into the Fleet trips module. The system detects arrival at a point and closes the trip leg on its own, pulls actual mileage and fuel burned per trip, watches fuel-level sensors and flags sharp drops (anti-theft). GPS mileage feeds the maintenance schedule, and the drive to pickup is computed via OSRM and shown on a live map.
Auto-arrival
when a truck enters a point’s geofence, the trip leg closes automatically, no calls to the driver.
Actual vs planned
real mileage and fuel burned per trip from Wialon next to the plan, deviations visible at a glance.
Fuel as an asset
fuel left in tanks from sensors is counted as a company asset; a sharp drop flags possible theft.
Mileage-based service
real GPS mileage drives the maintenance schedule, reminders fire on kilometres, not memory.
Drive to pickup
ETA computed via OSRM shows the empty run to the next load.
Live map
every truck on a Leaflet map in real time: where each is, its status, last signal.
Driver↔truck↔Wialon unit binding
telemetry lands on the right trip and driver automatically.
The result
The dispatcher stopped logging by hand — arrivals, mileage and fuel come from GPS on their own. Fuel theft became visible immediately, and every trip’s economics is computed on real data, not hearsay.
Tech stack
Have a similar challenge?
Discuss a projectNext case
Carrier ERP
ERP for an international carrier — trips, fuel, multi-currency →