Skip to content
Navo24Navo24
Shipping container with the owner code TGHU and serial 796484 painted on the door

Container Not Found: What the Tracker's Answer Really Means

Photo: Gazouya-japan, CC BY-SA 4.0

Our tracking API answers TGBU6232252 with invalid_number. Change the last digit to 1 and TGBU6232251 returns a voyage under way from Nhava Sheva toward Long Beach. Same prefix. A tracker with a single error message would print “container not found” for both, and for a lot of other cases too.

Our tracking API let me count the others. On 8 November 2026 I pulled 4,000 tracked references from one account. Of those, 1,026 sat at the status unknown, and for 1,011 the system had recorded a reason. Seven reasons cover 951 of them. A further 58 references carry a different marker, no_data, and 2 more an unconfirmed variant of the first group. Those are left out. The shares describe this pile. It includes some test entries, identifiers like ZZ0. It says nothing about the whole industry.

Our own first attempt produced the exact message in the title. We called the lookup endpoint with the number in a query string and got Container not found for every number, including the one that tracks fine. The endpoint wants the identifier in the path. Same call, number in the path, and it worked. So a “not found” can mean the box does not exist, the question went to the wrong place, or the box exists and nobody is reporting it. The groups below run from the largest to the smallest.

The line has no record of the box (369 of 1,011)

TFLU4505062 returned “no results found at carrier side”. The line was Transfar Shipping. UETU3269340 got the same answer. UES Investment owns it. Asian Express Shipping (Hong Kong) leases it. TCKU3442774, owned by Triton and marked off lease, came back with an empty event list and the tracking status not_found.

This group is 36.5% of the pile. The API gives only the reason code carrier_no_record and no cause. The code does not say why, so these are my guesses: a box booked but not yet gated in has no events, or it was tracked at the wrong line. The owner pages for TCKU and UETU name the lessors, Triton and UES. The lessee for UETU3269340 comes from the tracker record. The line, not the lessor, reports a box’s moves, so for UETU3269340 the question about booking and gate-in goes to the line or the forwarder. TCKU3442774 is marked off lease, so no line may be involved at all.

The box is leased and the tracker cannot tell which line has it (222, 22%)

TGHU3855882 passes the check digit. The prefix belongs to Textainer, a leasing company, and the record shows the box on lease to a line recorded as DOLPHIN SHPG. The lookup answered REFERENCE_NOT_RESOLVABLE. Reason: leased_needs_reference. No carrier attached.

Compare TGBU6232251. Also Textainer. Also on lease. There the lessor lookup mapped the box to KMTC (the record marks the carrier source as lessor), and the API returned the journey: gate-out at Nhava Sheva on 19 September, loaded on XIN CHANG SHU on 24 September (UTC), discharged at Busan (KRPUS) on 28 October, status at transshipment, ETA at Long Beach 6 December. Two Textainer leases, two answers.

Why the owner and the line are different companies is covered in container prefix lookup. For a leased box the most reliable key is the shipping line’s bill of lading or booking number, since the line, not Textainer, reports the moves. That is what our pages for TGHU and TGBU advise, and the forwarder has the number.

The tracker cannot identify the carrier (213, 21%)

GATU1284385 has a correct check digit (5). The record has no owner, no lessor and no carrier. The prefix is not anonymous. The 2016 BIC industry alert that listed the owners of boxes previously on lease to Hanjin names GATU as a Textainer prefix, the same lessor as TGHU and TGBU above. That list covers only Hanjin’s lessors, and prefixes can change hands since 2016. Our container prefix reference has no GATU page, and the tracker’s record has no owner for it.

A different error from our API gave advice that probably applies here too: “Please repeat the request specifying the shipping line SCAC code.” It came back when a hyphenated number could not be matched, and we did not test it on GATU1284385. Some lines have no SCAC code in the directory, but the SCAC code list shows yours if it has one. Name the line in the tracker’s Carrier field. That may let it skip the guessing.

The line is known and says nothing (100, 9.9%)

CAIU7958630 was added on 5 November with the carrier set by the user as CMA CGM. The lessor, CAI, lists the box on lease to CMA CGM, so the pairing looks right. The last poll, at 03:02 UTC on 8 November, still found nothing. Reason: line_no_info.

The question went to the right place and came back empty. Open the line’s own website. Try the same number there. Then try the bill of lading. The CMA CGM page shows its SCAC code (CMDU) and the prefixes its boxes start with (CMAU, CMDU, CMNU), so you can confirm you are asking the right line. If the line’s site is blank too, call the forwarder.

Only an old trip is visible (21)

SEGU1112302 is pinned to COSCO and has carried the reason previous_trip_only since 3 November. TEXU2209771 has the same reason, set on 1 November, and its record still shows a vessel called KUO LUNG and an ETA of 27 July 2026. The last poll was 7 November.

One container makes many trips under one number. A lookup by number alone may land on the previous trip. The data gives no cause for the missing new trip. When you expect a new shipment, track the new booking or bill of lading. The COSCO page lists its SCAC code (COSU).

The number is wrong (20)

TGBU6232252 came back as invalid_number. Why? The check digit is the eleventh character. It is calculated from the first ten. Each letter takes a value starting at 10 for A and skipping multiples of 11, each position is weighted by a power of two starting at 2⁰, and the sum is divided by 11, with a remainder of 10 counted as 0, as the ISO 6346 standard lays out. For TGBU623225 the sum is 4,049, and 4,049 modulo 11 is 1. So TGBU6232251 is valid. TGBU6232252 is not. The BIC check digit calculator calculates the digit for an owner code and serial you give it.

The invalid number took 46 seconds to get its answer on the first call. The repeat took 0.6 seconds. A wrong digit does not always get a fast no.

Format is the other half. tgbu6232251 and TGBU 6232251 both found the box, while TGBU-6232251 with a hyphen came back as “could not find tracking data”. Copy the number from the door or the bill of lading. Watch for O against 0 and I against 1. Do this check first. It takes a minute. Then read the prefix page to see whether the box is leased.

The vessel has no name yet (6)

TRDU9288422 was added on 18 September. The reason awaiting_vessel_tbn has stood since 21 September. TBN means “to be nominated”, so no ship has been named yet. That is all the code says. When I looked it up, the call hung for 45 seconds and returned STILL_RESOLVING, a 202 with the instruction to retry in 60 seconds.

By 8 November the reason was 48 days old. The data does not say how long is too long, so ask the forwarder for the nomination date. Meanwhile the sailing schedules show which vessels run the lane. Got a 202? Wait the 60 seconds. For a clean lookup, paste the number into the Navo tracker and add the line if you know it. The same desk has ocean freight rates and a Load Calculator. A team that tracks many boxes by hand can hand the watching to a Nav agent or one of the AI assistants, and Navo Mesh is a task exchange for logistics. Questions go through the contact page.

Frequently asked questions

Why does my tracker say container not found for a number that looks valid?

A number can pass the check digit and still return nothing. In our 8 November 2026 pull, the most common cause was that the shipping line had no record of the box (369 of 1,011), followed by leased boxes whose line was unknown (222). Confirm the booking with your forwarder.

How long should I wait before deciding a container number is wrong?

Not long. The check digit tells you in a minute whether the number can exist. If it passes, the wait depends on the shipment: before gate-in or vessel nomination there may be no events at all. One box in our data had had carried a vessel-nomination reason for 48 days.

Can I track by bill of lading or booking number instead of the container number?

Yes, and for leased boxes it is usually the better key. Our lookup accepts a container number, a bill of lading or a booking number. The shipping line reports the moves under its own reference, so a booking number points the tracker at the right system.

Built by people who move boxes for a living.

Tracking, schedules and load planning, as components you can adopt one at a time.

Track a container

Container, B/L or booking number. 240+ carriers, live status and ETA.