How to Identify the Shipping Line From a Container Number

Start with the standard container-number format

An ISO 6346 equipment identifier has four letters followed by seven digits. BIC, the organization that maintains the international container-code register, describes the structure as a three-letter owner code, a one-letter equipment category identifier, six serial digits, and one check digit. A typical freight container uses U as the equipment category, so an owner code such as MAE becomes the four-letter prefix MAEU on the equipment.

• Characters 1–3: the BIC-registered owner code.
• Character 4: the equipment category—U for a freight container, J for detachable equipment, or Z for trailer and chassis equipment.
• Characters 5–10: the six-digit serial number assigned by the owner.
• Character 11: the check digit calculated from the preceding characters.

Normalize the number before doing anything else: remove spaces and punctuation, convert letters to uppercase, and make sure there are exactly four letters and seven digits. A missing character can point to the wrong company, and a mistyped serial digit can still look plausible to a person scanning an email.

What the first four letters can tell you

The first three letters identify the registrant of the owner code; the fourth identifies the equipment category. A registry result is therefore strong evidence about the equipment registration. For example, WHLU is registered to Wan Hai Lines equipment, while WHLC is used as a carrier code. ONEU is a registered Ocean Network Express owner code, while ONEY is the carrier's SCAC. The codes are related to the same businesses but serve different identification systems.

Containers can be leased, interchanged, repositioned, or carried under vessel-sharing and slot arrangements. A shipping line can move equipment carrying another registrant's prefix. A merged or acquired brand may also leave legacy codes in circulation. Use the owner code to narrow the search, not to overwrite the carrier shown on the booking confirmation or bill of lading.

Why a SCAC is different from a container owner code

A Standard Carrier Alpha Code, or SCAC, is a transportation-company identifier administered by the National Motor Freight Traffic Association. A BIC owner code registers container equipment. Sometimes the values match—HLCU is both familiar carrier context and a registered Hapag-Lloyd owner code. Sometimes they differ: CMA CGM uses CMDU as a carrier code while CMAU is a registered equipment owner code; Evergreen uses EGLV as its carrier code while EMCU appears on registered equipment.

That is why a database field labelled “SCAC/prefix” creates errors. The fields answer different questions. SCAC asks which transportation company is identified. The BIC prefix asks which owner code is printed on the equipment. Keep both when they are known and label them accurately in search tools, spreadsheets, and customer updates.

Validate the check digit before trusting a lookup

The final digit is not just another serial character. ISO 6346 calculates it from the owner code, equipment category, and serial number. A validator can therefore catch many transcription errors before a lookup is sent to a carrier. A valid check digit does not prove the shipment exists or that a particular line operates it, but an invalid one is a useful signal to re-check the source document or container photo.

1. Normalize the identifier to four uppercase letters and seven digits.
2. Run the check-digit validation and correct any transcription error.
3. Look up the first three letters plus equipment category in the BIC registry.
4. Use the registry result to choose likely official carrier searches.
5. Confirm the operating carrier from the booking confirmation, transport document, or successful official tracking result.

A reliable carrier-identification workflow

Begin with the commercial record when it is available. The booking confirmation normally names the contracted ocean carrier and voyage context. The bill of lading names the carrier for the contract of carriage. The container number then identifies the physical unit inside that shipment. If the documents and equipment prefix point to different companies, do not force them to match—verify the booking and try the operating carrier's official tracker with the complete number.

If you have only the container number, validate it, check the BIC owner-code result, and search that company's official tracking service first. If the number is not found, consider leased equipment, an interchange, a data-entry error, or a different operating carrier. Ask the shipper or forwarder for the booking carrier instead of trying a long list of portals without context.

CargoScope can use container-number context to help start a multi-carrier tracking workflow, but automatic detection should remain overridable because equipment ownership and operation can diverge. Coverage varies by carrier, shipment, route, and available source data. A confident product response is useful only when it leaves room for the real shipment record to correct the inference.

Common mistakes that send teams to the wrong portal

• Treating a three-letter owner code as the complete four-letter equipment prefix.
• Assuming every fourth character is U without checking whether the item is a container, chassis, or detachable equipment.
• Replacing the printed prefix with a carrier's SCAC because the codes look similar.
• Skipping check-digit validation and searching a mistyped number across multiple portals.
• Assuming the registered equipment owner must be the operating carrier for the current booking.
• Using a third-party prefix list as authoritative when the BIC registry and shipment documents disagree.

How to record the result for the next person

Store the complete normalized container number, the BIC owner-code result, the operating carrier you confirmed, the booking or voyage reference, and the source used for confirmation. That small audit trail prevents the next operator from repeating the same lookup and makes a later carrier correction explainable. It also preserves the distinction between a registry fact and an operational conclusion.