Key Takeaways
- Hapag-Lloyd’s portal shows both planned and actual events — one of the few carriers that displays the full expected timeline alongside what has already happened.
- Hapag-Lloyd implements the DCSA AVPU code (“Available for Pick-up”), making it one of the only carriers that publishes a true combined-availability event.
- Live Position IoT covers roughly 85% of the dry container fleet. Launched April 2024, this is the first fleet-wide dry container IoT program among major carriers.
- The API at api-portal.hlag.com is self-service with a sandbox, but it is labeled BETA, and Hapag-Lloyd’s own documentation warns to trust website data over API data until the next release.
- Schedule reliability is second-highest among all carriers — 75.2% in December 2025, bolstered by the Gemini Cooperation with Maersk.
- Legacy UASC containers (UACU prefix) are trackable on the Hapag-Lloyd portal following the 2017 acquisition.
- Live ETA accuracy improved by 75% through a February 2026 WiseTech/CargoWise pilot combining IoT data with predictive analytics.
Who This Is For
This guide is for freight forwarders, importers, and operations managers who track containers on Hapag-Lloyd and want to understand what sets this carrier’s tracking apart — particularly its IoT capabilities and AVPU implementation — and where the remaining gaps are. For teams tracking across carriers, this sits alongside our event naming comparison.
What the Portal Shows You
Hapag-Lloyd’s tracking portal is one of the most informative among major carriers. Accessible at hapag-lloyd.com, the portal accepts container numbers, B/L numbers, and booking references. No login is required for basic lookups, though registered users get access to additional features including document management and notification settings.
The standout feature: planned and actual events side by side. While most carrier portals show you only events that have already fired, Hapag-Lloyd displays the full expected milestone timeline from origin to destination. You see what has happened, what is expected to happen next, and the estimated dates for each upcoming event. This makes it significantly easier to plan downstream logistics without needing to look up vessel schedules separately.
Container prefixes include HLCU (primary), HLXU, and UACU. The UACU prefix is a legacy from Hapag-Lloyd’s 2017 acquisition of United Arab Shipping Company (UASC). All three prefixes are trackable on the same portal. For guidance on when to use container number vs B/L for tracking, see our identifier guide.
Event Names and What They Mean
Hapag-Lloyd’s event labels are clear and granular, with one of the most complete transshipment event sets among major carriers. The table below maps each label to its meaning and the DCSA code.
| Hapag-Lloyd Event Label | What Actually Happened | DCSA Code |
|---|---|---|
| Empty Released | Empty container released for pickup at the origin depot | — |
| Gate In (Full) | Laden container entered the origin terminal | GTIN |
| Loaded at POL | Container was lifted onto the vessel at port of loading | LOAD |
| Departure from POL | Vessel left the port of loading | DEPA |
| Arrival at T/S Port | Vessel arrived at the transshipment hub | ARRI |
| Discharged at T/S | Container unloaded at the transshipment port | DISC |
| Loaded at T/S | Container loaded onto the connecting vessel at the hub | LOAD |
| Arrival at POD | Vessel arrived at the final destination port | ARRI |
| Discharged at POD | Container unloaded from the vessel at destination | DISC |
| Available for Pick-up | Container is cleared (customs, freight, terminal) and available in the yard | AVPU |
| Gate Out (Full) | Container left the destination terminal | GTOT |
| Delivered | Container delivered to the consignee’s location | DLVD |
The AVPU event is the single most operationally useful milestone in this table. “Available for Pick-up” means three things have happened: customs has cleared the container, freight charges have been settled, and the terminal has made the container accessible in the yard. Most carriers do not publish this as a combined event — you have to piece it together from separate sources. Hapag-Lloyd is one of the only carriers implementing the DCSA AVPU code, and it makes a meaningful difference for dispatch teams.
Transshipment events are broken out separately. Unlike CMA CGM (which compresses transshipment into a single label) or MSC (where transshipment updates can go silent for weeks), Hapag-Lloyd publishes distinct arrival, discharge, and reload events at the transshipment hub. This gives you actual visibility into whether the container is waiting at the hub or has been loaded onto the feeder.
“Empty Released” appears at the beginning, not the end. On Hapag-Lloyd’s timeline, “Empty Released” refers to the origin depot releasing the empty container for the shipper to pick up and stuff. This is the opposite of what some teams expect — it is not about empty return at the destination.
Update Cadence: How Fresh Is the Data?
Hapag-Lloyd’s tracking updates are event-driven with a data freshness that ranks among the better carriers. Terminal milestone events typically appear on the portal within 2-8 hours of occurring. The backend synchronization frequency is comparable to Maersk — faster than CMA CGM’s confirmed 6-12 hour structural lag.
The IoT layer adds a new dimension. With Live Position tracking covering roughly 85% of the dry container fleet, Hapag-Lloyd can source location data directly from the container rather than relying solely on terminal systems. This does not eliminate the lag for milestone events (gate-in, discharge, etc., still flow through terminal systems), but it means vessel-level position data can be more current than what traditional milestone tracking provides.
The February 2026 WiseTech pilot deserves attention. Hapag-Lloyd partnered with WiseTech Global (CargoWise) to combine IoT position data with predictive analytics, reporting a 75% improvement in Live ETA accuracy. This is specific to the CargoWise integration — the improvement is not yet reflected across all Hapag-Lloyd tracking interfaces — but it signals the direction: IoT-powered ETAs replacing schedule-based estimates.
Known Gaps and Quirks
The API is labeled BETA and Hapag-Lloyd’s own documentation says not to trust it yet. The developer portal at api-portal.hlag.com is live, offers self-service registration, includes a sandbox, and supports DCSA v2.2.4 — the most current version among any carrier. However, Hapag-Lloyd has published a warning that reads, in essence, that users should trust the website data until the next release. This is an unusual level of transparency: the carrier is publicly telling you its API data may not match its portal data.
What this means in practice: if you build an integration against Hapag-Lloyd’s API and notice discrepancies with the portal, the portal is the authoritative source. The API is usable for development and testing, but production workflows should cross-reference critical events against the website until Hapag-Lloyd removes the beta label.
Live Position IoT has a cost. Hapag-Lloyd charges $15 per container per voyage for Live Position tracking on Merchant Haulage shipments. If the container moves under Carrier Haulage, the tracking is included at no additional charge. This pricing model means the IoT layer is not automatically available for all shipments — it depends on your haulage terms.
Gemini Cooperation introduces partner-vessel data flows. Since February 2025, Hapag-Lloyd and Maersk operate a joint hub-and-spoke network under the Gemini Cooperation with ~340 vessels across 57 services. When a Hapag-Lloyd-booked container travels on a Maersk-operated vessel, the tracking data flows through an alliance data layer. The 92.3% schedule reliability recorded for Gemini services in November 2025 reflects the alliance’s operational performance, but the data-sharing lag can mean slightly delayed updates on partner-operated legs.
D&D free-time information is available but requires attention. Hapag-Lloyd’s portal shows Last Free Day information for containers at destination, but the display depends on the port and terminal. Some terminals feed this data more reliably than others. If you do not see Last Free Day on the tracking page, contact Hapag-Lloyd’s local office or the terminal directly.
Empty return tracking is available but not always visible. Hapag-Lloyd’s event timeline includes a “Delivered” milestone, but empty return after delivery depends on the haulage type and terminal. If you need to confirm empty return within the free time window for detention purposes, the Equipment Interchange Receipt (EIR) from the depot is your authoritative record. The portal may show the delivery event but not always the subsequent empty return.
Schedule reliability figures, update cadence estimates, and carrier performance data referenced in this guide are based on third-party industry reports and may reflect specific monthly snapshots rather than sustained averages. Carrier systems and capabilities are subject to change.
What to Do When Tracking Breaks
Scenario 1: Portal shows “Arrival at POD” but no “Discharged at POD” for 48+ hours. Vessel arrival and container discharge are separate events. A large vessel can take 2-3 days to fully discharge depending on the terminal’s capacity and the container’s position in the stowage plan. If the vessel has been at berth for more than 72 hours with no discharge event, contact Hapag-Lloyd — the container may be involved in a customs inspection or terminal operational delay.
Scenario 2: “Available for Pick-up” posted but container is actually on hold. The AVPU event fires when Hapag-Lloyd’s system registers that all three releases (customs, freight, terminal) are in place. In rare cases, a terminal hold applied after the AVPU event posts can block actual pickup. If your trucker is turned away, check with the terminal for any holds applied after the availability event fired.
Scenario 3: API data does not match the portal. This is expected during the beta period. Hapag-Lloyd has explicitly stated that the portal should be treated as the authoritative source. If you are building integrations, use the API for development but validate critical operational decisions against the website.
Scenario 4: UACU container returns no results. Legacy UASC containers should be trackable, but some very old bookings from before the full integration may not resolve. Try searching by B/L number instead of the UACU container number. If that fails, contact Hapag-Lloyd customer service with the original UASC booking details.
Scenario 5: No planned events showing on the timeline. Hapag-Lloyd’s planned-event display depends on having confirmed vessel and routing information in their system. If you see only actual events without the forward-looking timeline, the booking may not yet have confirmed routing assigned, or the planned-event feature may be temporarily unavailable for that particular service loop.
API and Integration Options
Hapag-Lloyd’s API portal at api-portal.hlag.com offers self-service registration with a sandbox environment for testing. The signup process is straightforward — no sales rep required. The API supports DCSA Track and Trace v2.2.4, which is the most current DCSA version implemented by any carrier as of early 2026.
The beta caveat cannot be overstated. Hapag-Lloyd’s own documentation warns users to trust the website data over the API until the next production release. This is not a minor disclaimer — it means Hapag-Lloyd is aware of data inconsistencies between the API and the portal and has chosen to be transparent about them rather than ship silently flawed data.
What the API adds over the portal: programmatic access to milestone events, vessel schedules, and container status. For teams building multi-carrier integrations, Hapag-Lloyd’s DCSA v2.2.4 alignment means the data structure is the most current standard available — ahead of Maersk, CMA CGM, and MSC, which are on v2.2 or earlier.
EDI remains available for teams with legacy integration infrastructure. Hapag-Lloyd supports UN/EDIFACT and XML-based EDI messaging alongside the REST API. This dual-track approach means you do not need to migrate off EDI immediately to take advantage of Hapag-Lloyd’s API improvements.
Operational Note: Hapag-Lloyd is the carrier to watch for tracking innovation. The combination of fleet-wide IoT, DCSA AVPU implementation, planned-event timelines, and granular transshipment events gives it the most complete portal experience among major carriers. The API beta label is a temporary gap, not a permanent limitation. For teams that need shipment-level visibility across carriers, Hapag-Lloyd’s data is the easiest to work with — the challenge is normalizing it with data from carriers that do not yet match this level of granularity.
Further Reading
- DCSA Track and Trace Standards — Digital Container Shipping Association
- Hapag-Lloyd API Portal
- Hapag-Lloyd Press Releases — Live Position IoT
- Sea-Intelligence Global Liner Performance Report
- WiseTech Global Newsroom — CargoWise Live ETA
- Hapag-Lloyd Tracking Portal
Need help interpreting this disruption or your shipment?
For a quick question, chat with Tradlinx on WhatsApp. For a deeper discussion, book a time below.
Prefer email? Contact us directly at min.so@tradlinx.com (Americas), sondre.lyndon@tradlinx.com (Europe), or henry.jo@tradlinx.com (EMEA/Asia).
Leave a Reply