Ten seconds is the difference between a map and a record.
Anything updates often enough to show a dot moving. The question is whether, six months later, you can prove where that vehicle was at 14:48 — and what it was doing on the approach.
A real trip, replayed
Drag the timeline, or press play. Events are where they actually happened.
A. Al-Harbi
- Ignition
- On
- Heading
- 90°
- Fuel
- 75.1%
- Odometer
- 412,876
−7.2 m/s², junction approach
3 of 7 events · 16.1 of 38.4 km
38.4 km, 34 minutes, Al Kharj depot to Sulay industrial, Riyadh. This is the same view you get on a trip from last March — full resolution, nothing thinned.
What the cadence actually costs you
A vehicle at 90 km/h covers three kilometres between two-minute fixes. Below is one stretch of road at three update rates — same road, same drive, sampled differently.
The faint line is the road. The solid line is what the system believes happened. At two minutes the corner has stopped existing — and with it, any chance of showing which lane, which junction, or how fast on the approach.
What Saqr sends
Common on cheap trackers
Typical of an OBD dongle on a budget plan
The gap is in the network, not the record
Riyadh to Jeddah has stretches with no usable signal for twenty minutes at a time. The unit keeps recording at the same cadence and stores it locally, then backfills the whole window on reconnect.
Two timestamps come with every position — when it happened, and when we received it. A replay of a dead-zone crossing is a continuous line, and you can still tell it was late.
What arrives, every time
Not a marketing list — this is the record, and all of it is on the API under the same names.
Developer documentation| Field | Type | Notes |
|---|---|---|
| position | lat, lng | GPS + GLONASS, typically 2.5 m in open sky |
| speed | km/h | From the satellite fix, not the odometer |
| heading | 0–359° | Course over ground |
| ignition | bool | Hard-wired, not inferred from movement |
| odometer | km | From the engine bus where available |
| fuel_pct | 0–100 | Tank probe or engine bus |
| driver_id | string | From assignment, or a driver key fob |
| accel | x, y, z | Drives the harsh-event detection |
| gsm | dBm | Signal, so a dead zone is distinguishable from a fault |
| recorded_at | ISO-8601 | When it happened on the unit |
| received_at | ISO-8601 | When we got it — the two differ after a backfill |
How long it stays
Most platforms thin old data to save storage, so the trip you need two years later is a straight line between two towns. We keep every fix.
- Live
Positions on the map within seconds of arriving
- 90 days
Full-resolution replay, every fix, instant to load
- 6 years
Complete trip history retained, no thinning
- Any time
Export the lot as CSV or Parquet to your own bucket
Tracking is the floor, not the product
Position on its own tells you where. These turn it into something you can act on.
Routing and dispatch
Plan the day, send it to the driver's phone.
Asset and trailer tracking
Trailers, generators, plant and containers.
AI dashcam
Road and cabin, clipped to the event.
Driver behaviour
Scored per driver and per trip.
Incident centre
Footage, telemetry and witnesses in one file.
Maintenance
By odometer, engine hours or date.