Route corridors for transit cargo
A route corridor is a virtual tube drawn along the road a sealed container should travel from Dar es Salaam. Trakora's e-lock checks every GPS fix against the corridor, raising an off_route alert when the truck leaves it and a stoppage alert when it sits still too long.
Container route corridors at a glance
- Rules it owns
- off_route · stoppage
- Geofence model
- 3-layer (yard, corridor, destination)
- GPS reporting interval
- 5 min
- Off-route thresholds
- 5 min warning · 8 min critical
- Stoppage threshold
- —1 set per leg
- Corridor width
- —1 tuned per route
- Alert channels
- SMS · WhatsApp · push
- Live corridors
- Dar→Mbeya · Dar→DRC · Dar→Mwanza
- On request
- Dar→Kigali · Dar→Lubumbashi · Dar→Lusaka
Off-route and stoppage, exactly
A corridor is not a line on a map — it is a rule evaluated against every five-minute fix. Two questions get answered on each one: is the truck still on the road it declared, and is it still moving?
The truck left the declared corridor
A GPS fix places the container outside the corridor tube for its route — a diversion off the Dar highway toward a side road that was never on the plan.
A warning at five minutes off-route and a critical alert at eight, naming the corridor, the last fix and the point of departure — to SMS, WhatsApp and push.
Call the driver while the trail is fresh, and keep the alert with its timestamps as the record that shows exactly where and when the cargo left its route.
The container has been stationary too long
The unit stays still longer than the dwell allowed for that leg. A rest stop is normal; a long unexplained halt on the shoulder is not.
A stoppage alert naming the container, where it stopped and how long it has been still, so a stall is caught before the consignee starts calling.
Check whether it is a breakdown, a queue at a weighbridge, or something worse — and act on a fact, not a guess about why the container has gone quiet.
The corridor is the middle layer of a three-layer geofence:
Corridors out of Dar es Salaam
Dar is the gateway for the landlocked hinterland. Each corridor is drawn along the real road to its border, and configured per route.
Dar → Mbeya → Zambia
The Southern corridor down the TANZAM highway toward Tunduma and the Nakonde border into Zambia and on to Lusaka. Live today; the Lusaka leg is configured on request.
/ route-corridors · liveDar → DRC (Kasumbalesa)
Toward the Copperbelt and Lubumbashi via the Kasumbalesa crossing — the long haul where corridor and stoppage monitoring matter most. Live today.
/ route-corridors · liveDar → Mwanza
North-west toward Lake Victoria, and the staging point for cargo continuing across the lake. Live today.
/ route-corridors · liveDar → Kigali (Central corridor)
The Central corridor toward the Rusumo crossing into Rwanda. Configured on request, drawn along the declared route the same way as the live corridors.
/ route-corridors · on requestSetting a corridor on a booking
The corridor is chosen when the container is booked and evaluated from the moment the lock is applied.
Pick the corridor on the booking
Each container booking carries a route corridor and a destination yard, so the tube it must stay inside is set before it leaves the port.
Apply the lock and start the clock
Sealing the container starts the corridor evaluation. From then on every five-minute fix is tested against the tube.
Watch off-route and stoppage
Leaving the corridor raises off-route at five minutes and critical at eight; sitting still too long raises a stoppage — all to SMS, WhatsApp and push.
Close with the trail
Arrival at the destination geofence closes the booking, and every corridor event lands in the signed PDF audit trail for the consignee and the file.
What corridor monitoring cannot do
What to expect
- Trakora is an operations and monitoring platform, not an accredited customs seal system. It records and proves chain-of-custody with a signed PDF audit trail; it does not replace a customs seal where one is legally required.
- Off-route detection needs a configured corridor. A container moving outside any configured corridor is still tracked, but it is not corridor-evaluated until a route is drawn for it.
- The corridor width and the stoppage dwell are tuned per route and marked as figures to be confirmed here — a corridor too tight produces false off-route events, one too loose misses a real diversion.
- The lock reports over GSM, so in a coverage dead zone fixes buffer and backfill when signal returns. An off-route or stoppage raised while offline is delivered on reconnection with its original timestamp, not the delivery time.
Values marked — are figures to be confirmed: the stoppage dwell threshold and the corridor tube width are tuned per route and per leg and are not fixed defaults in the module manifest, so no value is stated here as fact. The 5-minute GPS interval and the 5-minute / 8-minute off-route thresholds are the container module's committed settings.
Frequently asked questions
What is a route corridor?
A virtual tube drawn along the road a container should travel. Every GPS fix is checked against it, and leaving it raises an off_route alert.
How quickly do I know the truck has diverted?
A warning fires at five minutes off-route and a critical alert at eight, naming the corridor and the last known fix.
What if the container just stops?
A stoppage alert fires when it stays still longer than the dwell allowed for that leg, naming where and how long — so a stall is caught early.
Which corridors are available?
Dar→Mbeya, Dar→DRC and Dar→Mwanza are live; Dar→Kigali, Dar→Lubumbashi and Dar→Lusaka are configured on request along the declared route.
Is this a customs seal?
No. Corridor monitoring proves chain-of-custody with a signed PDF audit trail, but it is not an accredited customs seal and does not replace one where the law requires it.
More in container tracking
Draw your corridor
Tell us the routes you run out of Dar and we will scope corridor monitoring in TZS, with a VAT invoice and Swahili support.