On the morning of 16 November 2026 our lookup for FCIU9422985 said arriving, with an ETA of 07:00 UTC that same day. The latest AIS fix in the record was from 08:45 UTC and put CMA CGM Montmartre at 50.03 N, 1.64 W, in the English Channel. The box had left Ningbo on 29 September. The ETA was in the past and the ship was not in the port.
The next morning, 17 November, the same lookup carried a new line: ARRI, actual, Southampton, 16 November 19:00 UTC. Twelve hours after the planned time. The ship had covered roughly 98 km from the position I saw the day before. Between my two lookups the record gained that arrival and nothing else. The estimate is a promise made at the quay, and the sea answers when it likes.
Does “arrived” mean the ship, the berth or the box?
Three different events hide behind that word. In the DCSA standard for track and trace, a vessel has arrived once it is berthed at the port terminal, ready for load and discharge to begin. The DCSA event definitions keep discharge, the lifting of the container off the vessel, as a separate event with its own timestamp. Gate-out is a third.
Not every carrier reads the word the same way. A Tradlinx comparison of carrier event labels says “Vessel Arrival” means berthed on most lines, but at anchor or near the port on ONE, Yang Ming and HMM, a gap it puts at 3 to 48 hours. If your line is one of those, an “arrived” can come before the ship has a berth.
Our API shows the other gap, between ship and box. FCIU9422985 had an actual ARRI at 19:00 on 16 November. At 08:20 the next day it had no discharge line and its status was still arriving. Thirteen hours and twenty minutes without a move on the box itself. Crane time? Reporting lag? I do not know. The last poll of the line had run at 06:49 UTC, before the AIS fix of 08:20, so the line may simply not have been asked again yet. The prefix FCIU and the line, CMA CGM, are on the reference pages if you want the owner.
Compare HLBU1480830, a Hapag-Lloyd box. At Busan, YOKOHAMA EXPRESS was logged as arrived at 18:31 UTC on 13 November (03:31 local, 14 November). The discharge followed at 00:09 UTC, five hours and thirty-eight minutes later, and the status in this record is discharged. Two events with two timestamps came out of one ship call.
When the ship is already in and the line has not said so
TGHU6187236 is an MSC box on MSC KATALIN II, bound for Khoms in Libya, booked from Chicago. On 17 November its ETA read 18 November 00:00 UTC, marked date_only and estimated. Midnight in that field is not a time. It stands for some hour of that day.
The same record held something more useful. An ais_pod_arrival block said the vessel had been observed at Al Khums on 16 November at 12:58 UTC, 3 km from the port reference point, with the note that the line had not reported the arrival. So the carrier still showed a future date, and the ship was at the port a day earlier. In this record the AIS arrival sits in its own field and the status stays arriving.
A second figure sat in the same record, a predictive ETA of 13 November 16:00, next to a confidence field of 89. That is four days before the carrier’s date, and already in the past when I read it. The file does not say when the prediction was made, so I cannot tell you which of the two a tracker should print. The explainer on ETA as a live signal covers how such numbers are built, and the piece on AIS shows why the position is more honest than the typed arrival.
What to check when the container ETA has passed
If the container ETA passed with no arrival, position comes first. A vessel on the map beside the port and an ETA a few hours old can mean a wait for a berth. When many ships wait together the pattern shows on the ports and congestion feed, and the North Europe knock-on story shows how one backed-up hub pushes ETAs elsewhere.
The event list is next. Short check. An ARRI with no DISC usually means the ship is in and the box is not yet off, unless your line logs arrival at anchor. A box that goes inland by rail has a later arrival at the ramp, so check whether the ETA you hold belongs to the port or to the final stop. The schedules page groups sailings by vessel, and freight has rates for the next leg.
Then the number itself. A container ETA passed in silence can simply mean a bad reference. A wrong digit, a leased prefix without a line, or a reference the tracker cannot place all produce silence that looks like a delay. The container not found guide sorts those cases. The tracking API returns the raw JSON, so you can read ARRI and DISC yourself, and the track page takes a container number. Both missing for days? Use the contact form.
I cannot give you a number of hours after which a missing arrival becomes a problem. The DCSA text defines the events and sets no limit, and my three boxes cover only a few ship calls. How long a vessel may sit at anchor before the line should call it a delay is not written down in any source I opened.
Frequently asked questions
Is my container late if the ETA has passed and the status still says arriving?
Not necessarily. On 16 November 2026 FCIU9422985 showed an ETA of 07:00 UTC and was still in the English Channel at 09:02. The actual arrival at Southampton was logged at 19:00 the same day, twelve hours after the planned time.
What is the difference between arrived and discharged in container tracking?
Arrival means the vessel has berthed and is ready for work. Discharge means the container has been lifted off. For HLBU1480830 at Busan the two events were 5 hours 38 minutes apart (18:31 and 00:09 UTC). A tracker can show one without the other.
Why does the ETA show 00:00 for my container?
A date-only ETA is stored as midnight. TGHU6187236 carried an ETA of 18 November 00:00 UTC marked date_only and estimated on 17 November. It means some time on that day, so the box is not late at 00:01.
