A dead zone makes data late. It does not make it missing.
Every tracking vendor has a coverage map with no gaps on it. Ours has gaps, because the roads do. What matters is what the unit does in them — and how late the answer arrives when someone is asking where a truck was.
- 93.6%
- Of 4,326 km of corridors sent live
- 29 min
- Longest gap: Riyadh – Tabuk
- 39 days
- Of driving a unit can hold offline
- 24 h
- To a fitter in the central region
Six corridors, gaps included
From where our units have actually lost signal, not from a network operator's brochure. Pick a road and a speed: a faster truck crosses a gap sooner, so the same kilometres make the data less late.
The long one. Two real dead stretches in the middle, and a handful of short dips a driver would never notice.
- Arrives live
- 92.8%
- 4 gaps, 48 min in all
- Longest wait for data
- 20 min
- below the 45-minute stale alarm
- Fixes held on the unit
- 119
- 0.04% of its 16 MB buffer
- Lost
- 0
- backlog sent in under a second on reconnect
The buffer is not the constraint
A stored fix is 48 bytes. 16 MB of flash holds 333,333 of them — at one every 10 seconds, 38.6 days of continuous driving with no signal at all.
The longest gap on any corridor here fills 0.05% of it. So the question a fleet should ask is not whether data survives a dead zone, but whether anyone acts on a truck that has been quiet for 29 minutes.
- 0 min Last position, marked with the time it was recorded.
- After 2 min Shown as buffering, with the corridor gap it is probably in.
- After 45 min Marked stale, and a silent-unit event is raised. No gap on these corridors is this long, so a normal crossing never trips it.
- On reconnect The whole gap backfills, and the trip replays as one line with both timestamps kept.
How long a broken unit stays broken
The other coverage. A unit that stops reporting is a visit, and the visit is only as fast as the nearest fitter.
- Central regionSaqr fitters · Riyadh24 h
- Western regionSaqr fitters · Jeddah48 h
- Eastern region and JubailSaqr fitters · Dammam48 h
- Tabuk, Hail, Al Jouf, Abha and Khamis Mushait, Jazan, NajranCertified fitting partner · the nearest partner72 h
Across the border
Trucks do not stop at the Kingdom's edge, and neither does the unit. What changes is whether you see the trip as it happens or after.
- Bahrain, Kuwait, Oman, Qatar, UAE live
Roaming is in the rate. Positions arrive live, and alerts fire as they would at home.
- Jordan live
Roaming is in the rate on the unit, but the network hands over slowly at the border — expect a few minutes' gap at the crossing.
- Everywhere else on return
The unit keeps recording and sends the whole trip when it is back. You see where it went, the day it returns.
Where no coverage map helps
Satellites and cell towers fail in different places. A unit that has one and not the other says so, rather than guessing.
| Place | Satellites | Cell | What you see |
|---|---|---|---|
| Underground car parks | sometimes | No satellites. The map holds the last fix outside and marks it indoors, so a parked van does not appear to be at the entrance ramp. | |
| Steel-roofed warehouses | usually | The unit still talks, it just cannot say where it is. Reported as 'inside' with the last good fix. | |
| Inside a closed container | no | Nothing gets in or out. A vehicle shipped in one reports again when the doors open — which is the limit the security page warns about. | |
| Deep urban canyons | partly | yes | Fewer satellites, more reflections. Accuracy drops from a few metres to tens; speed is filtered so a jump does not become a speeding event. |