Africa Lanes (Europe/Asia → Africa) Shipment Tracker

Because the variance lives there: a Shanghai–Lagos ocean leg is predictable to a day or two, while Apapa's gate, customs and equipment cycles have ranged from days to multi-week. Port-authority storage regimes (short free time, mandatory escalation) compound it. Successful traders on these lanes budget destination dwell explicitly and track 'discharged → gate-out' as the headline KPI, not the sailing time.

Published schedules say highly port-dependent: 7–15 days to North Africa, 18–30 to West Africa, 20–35 to East Africa via Indian Ocean hubs. Reality adds origin dwell, destination clearance and the lane's specific friction (destination-port dwell is the lane's defining variable). Your own log is the honest answer: after 15–20 shipments the actual door-to-door distribution — including the tail — is sitting in your CSV export.

Year-end consumer surges meet infrastructure limits; election cycles and policy shifts add country-specific risk. Peak behaviour to expect: space sells out earlier, rollover risk rises, rates firm, and the lane's chokepoints run hotter. Rows you add in those windows should carry earlier bookings and more conservative ETAs than the same route in the slack months.

Because lanes have personalities — different chokepoints, peaks and failure modes — and mixing them averages the signal away. A dedicated board per major lane keeps the dataset clean: this lane's transit distribution, this lane's exception causes, this lane's carrier ranking. That's the granularity rate negotiations and buffer-stock math actually need.