CSLU2361725 came to Shanghai on OOCL CHANCAY and was discharged there (CNSHA) on 18 October at 22:02 UTC. Its next load, on 2 November at 16:54 UTC, was on OOCL PERU. Both ships carry voyage 002E. Our tracking API raised a vessel-change flag the next day, 3 November at 20:31 UTC. Same voyage code. Different hull. And 14.8 days between discharge and the next load.
A container rolled to another vessel looks like this in tracking. The line leaves the box behind and puts it on a later sailing. In the records pulled for this piece, no event carries that word. You read it from the gap between a discharge and the next load, and from a vessel name that is not the one you were given.
A container rolled to another vessel: what the records show
The DCSA event definitions define load as lifting a container on board and secured, and discharge as lifting it off. A roll sits between the two, as the AJOT piece describes it: the box is off at a hub and the load on the planned ship never happens.
On 18 November 2026 one tracking account held 210 containers, and the Navo tracking API returned 66 of them in full. Those 66 gave 43 discharge-and-reload pairs across 32 containers. The median wait between the two events was about 14 days. Thirteen pairs were under a week and six ran past 30 days. Only five containers carried a vessel-change flag. A long wait alone proves nothing. Neither does a changed ship name.
Ocean Insights, in an analysis published by AJOT, found that in most of the leading hubs between a fifth and a third of transshipment cargo was subject to rollovers. That analysis covers the post-lockdown demand surge, so it is a pandemic-era figure and not a current rate. The same source says shippers are often not told in advance.
Two planned gaps at two hubs
ONEU7693238 (ONE) is a different picture, and it also carries a vessel-change flag: PALAWAN to WESTPORT, raised 27 October at 13:43 UTC. Its discharge at Singapore is planned for 27 November at 17:45 UTC and its load on SINAR CARITA for 16 December at 19:39 UTC. That is 19 days, and the whole gap is already in the schedule. A long planned gap and a flag can sit on one box, and the reason stays with the line.
SEGU4658869 (COSCO) shows the same thing with a ship you can find. It was discharged at Valencia on 8 November at 20:35 UTC. The next sailing is planned on LIMARKO BREEZE, voyage 630S, for 26 November at 20:00 UTC, 18 days later. On 18 November the ship’s AIS position was 39.40 N, 0.26 W, off Valencia.
A swap before sailing, and a wait with a label
HLXU8230568 (Hapag-Lloyd, prefix HLXU) was loaded at Qingdao on 3 November at 10:35 UTC and sailed at 00:20 UTC the next day on EDITH MAERSK. The load on EDITH MAERSK is what shows the swap before sailing. The flag came later, at 05:41 UTC, and records NEW YORK EXPRESS as the earlier vessel. The ETA for London Gateway on file is 5 December, marked as an estimate. For this lane the API shows an on-time rate of 37.93% over 365 days, from 174 observations, with a median delay of 103 hours, and an ETA band that runs from 5 to 13 December.
The longest labelled wait belongs to TLLU7074125 (ZIM, prefix TLLU). It was discharged at Busan on 28 September at 08:57 UTC. At the same minute the line posted an event named “Transshipment Delay”. The next load came on 28 October at 18:26 UTC, on MSC QINGDAO, 30.4 days later. TLLU7073540 and TLLU7073509 show the identical gap. The longest wait in the whole set was 37.0 days, TRDU9305237 at Qingdao.
When to write to the line
Act in three cases. The planned load date has passed with no load. The planned date moves later on every refresh. Or the line posts a delay event and no new vessel. Check the lane on the schedules page, then send the line the container number and ask for the current vessel and voyage on the booking.
A later sailing moves everything behind it. If the lane has another carrier with space, compare the current freight rates from Asia. If the cargo is still to be stuffed, the load planner builds 3D load plans under CTU Code and IMDG rules. A custom Nav agent can watch free time across carriers, there is also an AI assistant page and an AgentMesh page for task requests. Questions about the tracking data itself go to the Navo team.
If the page does not change at all, read why a status stays frozen for days. If the ETA has passed with no arrival, the passed-ETA case has the checks.
Frequently asked questions
What does it mean when a container is rolled to another vessel?
The line leaves the container behind and moves it to a later sailing. Tracking does not print the word. You see a discharge at a hub, a gap, then a load on a later or different ship. Ask the line for the booking's current vessel and voyage.
Does a changed vessel name always mean a rollover?
No. A name can change while the voyage code stays the same, as with OOCL CHANCAY and OOCL PERU on voyage 002E. Read it together with the dates of discharge and next load, and with the ETA marking.
How long can a container wait at a transshipment port?
In one account the waits ran from under a week to 37 days. A planned connection of 18 or 19 days is normal when it is written into the schedule. A long gap with no planned next ship, or a planned date that keeps moving later, is the case to raise with the line.