Transhipment hubs, decoded.
Singapore. Tanger Med. Manzanillo. Algeciras. Why your container changes ships in places you've never been, and what those swaps mean for your timeline.
Roughly 60% of the world's containers travel on more than one vessel. Your box leaves Shanghai on a 24,000-TEU ultra-large, gets discharged at Singapore four days later, sits in a stack for 36 hours, then loads onto a feeder bound for Chennai. The carrier calls this a "service routing." You call it the reason your shipment took 23 days instead of 17.
Welcome to the strange geography of transhipment.
Why transhipment exists
Ocean carriers want their biggest, fastest vessels — the 18,000-24,000 TEU monsters — running the trunk lines. Those routes (Asia-Europe, Trans-Pacific, Asia-Med) generate the highest revenue per nautical mile. But trunk-line ships are too big for 80% of the world's ports. They can't enter Chittagong or Lagos or Salvador. So they discharge their containers at strategic hubs, where smaller "feeder" vessels pick them up and run the last 1,500–3,000 nautical miles.
This is the hub-and-spoke logic that defines modern shipping. It's economic — big ships have unbeatable cost-per-TEU on long routes. It's also fragile — when the hub clogs, everything downstream clogs with it.
The eight hubs that matter
These eight terminals handle the bulk of global transhipment traffic. If your container is moving inter-regionally, there's an ~85% chance it touches one of them.
Singapore
The world's transhipment capital — ~85% of its container traffic is transhipment, not import/export. PSA International runs Tuas + Pasir Panjang. Connects Asia-Europe and Asia-Australia rotations to virtually every Southeast Asian port via feeder.
Tanger Med
Gibraltar Strait's busiest hub. Built from a sand dune in 2007, now ~9M TEU/year. Connects Mediterranean and Atlantic loops. APMT and Hapag-Lloyd's Eurogate operate the major terminals.
Algeciras
Tanger Med's Spanish neighbour, across the strait. Maersk's biggest Mediterranean transhipment node. Different terminal operators, similar geographic logic.
Port Said East
At the Mediterranean mouth of the Suez Canal. Critical for Asia-Europe traffic. Feeder distribution to the Eastern Mediterranean and Black Sea ports.
Salalah
Oman's deep-water gateway on the Indian Ocean. Handles Asia-Mediterranean traffic when fleets bypass Suez (e.g. during canal disruptions or Red Sea instability).
Jebel Ali
The Persian Gulf's transhipment anchor — DP World's flagship. ~14M TEU/year. Feeder distribution to Iran (when sanctions permit), Iraq, the wider Gulf, and East Africa.
Manzanillo (Atlantic)
Caribbean-side Panama, just east of the canal locks. Critical for transhipment between East Coast Americas and Asia-Europe trunks. APM Terminals + MIT.
Colombo
Sri Lanka's deep-water port, on the Asia-Europe trunk line. India's primary transhipment partner (Indian ports lack the depth for ULCS). Now handling ~7M TEU/year.
What a transhipment event actually costs you
The good case: 36 hours of dwell. The container is discharged, sits in a stack for a day and a half, gets loaded on the feeder, sails on schedule. You barely notice.
The bad case: missed connection. The mother vessel was late, the feeder departed on time. Your container now waits 5-14 days for the next feeder sailing. ETAs slide. Demurrage starts ticking at destination. Customers ask uncomfortable questions.
The ugly case: storm-induced cascade. A typhoon delays the trunk vessel. It arrives Singapore three days late. The next two feeders are already committed. Your container waits seven days. Then a strike at the destination port adds three more. Now you're looking at a 23-day delay on a 17-day schedule.
The transhipment event is where most ETA churn originates.
A container that doesn't transship has a roughly stable ETA. A container that does transships sees the ETA move ±3 days, ~40% of the time. Plan for it; it's not a bug.
How tracking systems handle the swap
When a container transships, the carrier issues a new voyage record. A naive tracker would stop receiving AIS updates because it's still subscribed to the first vessel's MMSI. A good tracking system watches for the transhipment status, looks up the new vessel, and seamlessly swaps the AIS subscription. From the dashboard's perspective: the box just keeps moving.
Broadpath surfaces every transhipment as a discrete event in the timeline — "Discharged at Singapore PSA · loaded on EVER ACE · departed for Rotterdam." If the new vessel's MMSI changes, the live map smoothly follows.
What you can't fix is the underlying physics. If the feeder takes 5 days instead of 3 because of weather, no system makes that go faster. What you can do is find out today — not three days from now when the carrier finally updates their portal.
Want a list of every transhipment event from your last quarter? We can pull it from the indefinite event archive. Email [email protected].