Live positions & history
Where each vehicle is now, and the movement behind it: speed, direction, stops and mileage, kept so you can replay any day someone asks about.
Tracking
See every vehicle move, and replay what happened
Every vehicle on one live map, even on 2G. When a driver tells you about the route, the roadworks or the stop, the history is already on screen to check it against, without waiting for calls or screenshots.
Where every vehicle is, right now
Positions arrive over 2G, so the map keeps working on the roads your fleet actually drives.
The route it was supposed to take
Planned against actual, so a detour is a thing you can see rather than a thing you are told about.
What happened, hours later
History stays on the vehicle's own record, so yesterday's trip is still there when the question comes up.
Capabilities
Tracking capabilities
Tracking is part of running the fleet here, not a separate device portal. Tracker data links back to vehicles, drivers, trips, maintenance and documents.
Devices tied to the right vehicle
Trackers stay linked to the vehicle they are fitted in, so the map shows your fleet, not a loose list of device IDs.
Same vehicles everywhere else
Trips, maintenance and documents use the same vehicle records, so what you see on the map matches what the rest of the platform runs on.
Verification
What it helps verify
Three questions an owner asks every day, each answered from the same record, not from three separate systems.
Where a vehicle is now
Current coordinates, map position, and stationed or in-transit status.
Where it has been
Position history, movement trace, speed, direction, mileage, and related telemetry.
What was expected
Trips, routes, stops, pickup points, and schedules beside the tracking record.
Live and history
One record, read two ways
The same packet answers the question you have now and the question you have on Friday. Nothing is written twice, and nothing has to be reconciled between a live view and a report.
Where every vehicle is
Position, speed and heading on one map, with moving, stopped and not reporting told apart rather than lumped together. A tracker that has gone quiet looks different from a vehicle that is parked, which is the distinction that decides whether you call the driver or the workshop.
What happened on the day
Replay the route, the stops and the time spent at each one, beside the trip that was planned. When a driver explains a late delivery or a fuel claim, the movement behind it is already on screen, so the conversation starts from the same facts instead of from memory.
Telemetry
What one report carries
Every fitted tracker writes these against the vehicle, not against a device ID. Which of them arrive depends on the device: some report power and odometer, some report position and little else.
- Position5.6037, −0.1870
- Speed42 km/h
- HeadingNNE
- IgnitionOn
- Odometer128,443 km
- External power13.8 V
- Battery4.1 V
- Network2G · 3 bars
Illustrative values.
On the ground
Built for the network your vehicles are on
Most of this fleet is not on a strong connection, and a tracking product that assumes one is a tracking product that goes blank where the work happens.
Works on 2G
Trackers report over the network the vehicle actually has. A thin connection means smaller, less frequent reports, not a blank map.
Gaps are shown as gaps
When a vehicle passes through somewhere with no coverage, the history says so rather than drawing a straight line through it and calling that the route.
Teltonika and H02 today
Those families connect now, and other families are decoded on request. Already-fitted trackers can be brought on if they can be configured to report to our server.
Want to see your own routes replayed before you commit?
Request a demo