To track leased container numbers you need the right reference. In one account’s list, pulled on 8 November 2026, 222 references stopped at the reason leased_needs_reference. Only 17 had a lessee name on file. Nine had a carrier name.
The prefix on the door of a TGHU, TCNU or FCIU box names a leasing company. TGHU is Textainer, TCNU is Triton, FCIU is Florens. The shipping line has rented the box and reports its moves under its own reference. A tracker that holds only the container number has to guess which line to ask. Our earlier post Container Prefix Lookup: When the Owner Is Not the Line covers that gap, and the full list of causes sits in the Container Not Found guide.
On 16 November I ran nine numbers through our tracking API to see how the guess goes. I took nine numbers from that list and from two prefix pages: three TGHU, four TCNU and two FCIU, a chosen mix, so treat it as a sample of nine. Three more lookups from the same session sit outside the count: a TGBU box, an FCIU box that SPIL answered, and a test number. The first two answered. All nine pass the check digit. I calculated each one. A typo is off the table. Five answered. Four did not.
Five that answered, four that did not
TGHU6187236 came back with MSC, the vessel MSC KATALIN II, a trip from Chicago to Khoms and an ETA of 18 November. The record also carried a bill of lading, MEDUAFX61384. I looked that bill up on its own and got the same box. MEDU is one of the codes MSC uses on its documents, next to MSCU.
FCIU5376449 answered with ONE, a 20-foot box going from Gurugram to Haifa, ETA 19 December. Its booking number and bill of lading were the same string, DELG41479900. FCIU9422985 answered with CMA CGM, Ningbo to Southampton, ETA 16 November. TCNU1564398 answered with Evergreen, Shanghai to Algiers, ETA 12 December, bill of lading 142653242673.
Then TGHU9074552. Found. The tracker named Emirates Shipping and showed a bill of lading, ESLCHNQIN073454. The status was unknown. One event only, a gate-in at Ankleshwar on 2 October, and an ETA that was also 2 October. The tracker found the box, but the answer was old.
The four that failed were TGHU3855882, TCNU7053081, TCNU7377666 and TCNU8600840. Each returned REFERENCE_NOT_RESOLVABLE: “no carrier and no data source can identify it. We will re-check it whenever we add a new carrier or source.” The record for TCNU7053081 names a lessee, Rock-It Cargo USA. Still no line. The record for TCNU8600840 names DHL Global Forwarding (UK), which is a forwarder.
Across the whole list, which is a larger set than the 222 unresolved references, 268 TCNU boxes carry a lessee name. After China United Lines (114) come Manuport Logistics (21), Remant Globe Logistics (21), DHL Global Forwarding (18) and Kuehne + Nagel (14). DHL and Kuehne + Nagel are forwarders, 32 of the 268. It is one account’s list and says nothing about the industry as a whole.
How to track leased container numbers: from a bare number to a moving ship
- Read the prefix page first. It names the owner, a lessor, and says the shipping line holds the moves. Start there.
- Ask your forwarder or look in the booking confirmation for the bill of lading or the booking number. The line issues a master bill. A forwarder issues a house bill. Formats vary: the MSC bill in our sample began with MEDU, the Evergreen one was twelve digits, the ONE one was letters and numbers.
- Send that number to the Navo tracker or the API. Both take a container number, a bill of lading or a booking number. In my test all four bills of lading returned their container. They came from records that had already resolved, so the test shows the lookup works. It does not show that a bill rescues a number that failed. None of the four failed boxes had a bill I could try.
- You do not have to name the carrier when you send a bill. If you know the line anyway, the SCAC code list shows which codes belong to which line.
- Read the date of the last event before the status. In the Emirates Shipping case the status said unknown and the last event was six weeks old. The last date tells you whom to call.
If every lookup still fails, the number is registered but no carrier or source can identify it. The API says it will re-check “whenever we add a new carrier or source”. Write to the forwarder with the container number and the booking date.
Hanjin, 2016: the prefix list that mattered
When Hanjin Shipping filed for bankruptcy, boxes it had leased sat in several ports. Container lessors issued an industry alert listing prefixes next to owners. A copy sits on the Bureau International des Containers site, in a file named for 27 September 2016. It asked anyone who came across a box to contact the owner. The box could then be identified and returned. All three prefixes here are on it. TCNU sits under TIL, TGHU under Textainer, FCIU under Florens.
A prefix gives you the owner. Where the ship is this week is a separate question, and the line answers it. For the lane a late box is moving on, the sailing schedules list the ships, and freight rates price the next booking if the delay forces a new one.
Frequently asked questions
Why does a TGHU, TCNU or FCIU number return nothing in a tracker?
The prefix names a leasing company, not the shipping line. A tracker holding only the container number must guess the line. In our 16 November 2026 test, four of nine valid numbers returned REFERENCE_NOT_RESOLVABLE with no carrier attached.
Which number should I use to track a leased container?
The bill of lading or booking number from the shipping line. The line reports the moves under its own reference. In our test the lookup returned the same box for all four bills of lading we tried, including MEDUAFX61384 and DELG41479900, though those boxes had already resolved by container number.
The tracker found my leased container but the status says unknown. Is the box lost?
Not necessarily. TGHU9074552 was found under Emirates Shipping with status unknown, one gate-in event on 2 October 2026 and nothing after. Check the date of the last event and ask the forwarder for the current voyage.