How HMM Container Tracking Actually Works: What the Portal Shows, What It Doesn't, and What the Events Mean

Key Takeaways

HMM’s API portal at apiportal.hmm21.com is live but primarily in Korean. Swagger/OpenAPI 2.0 documentation, POST-based endpoints, API key authentication, and a 300 calls/hour limit on the schedule API. Terms of service date from 2021.
HMM’s container SCAC is HDMU, not HMMU. This catches many teams by surprise. HMMU is a secondary prefix. The fleet also includes HAMU, KOCU, GHMU, HDGU, and HMRU.
HMM is approximately 65% state-owned (Korea Development Bank ~32.6%, Korea Ocean Business Corporation ~32.28%). Privatization plans have stalled.
“Vessel Arrival” likely means at anchor, consistent with ONE and Yang Ming in the Premier Alliance, though not definitively confirmed from HMM’s own documentation. Visibility platforms report this pattern.
Schedule reliability sat in the 50-60% range in late 2025, in line with most Premier Alliance carriers per Sea-Intelligence data. The Premier Alliance with ONE and Yang Ming launched February 9, 2025.
HMM is a DCSA founding member with DCSA Booking and eBL pilot participation.

Who This Is For

This guide is for freight forwarders, importers, and operations teams who track on HMM and need to navigate a portal with bot protection, an API documented primarily in Korean, and event labels that mix gerund and past-tense forms. For the cross-carrier perspective, see our event naming comparison.

What the Portal Shows You

HMM rebranded from Hyundai Merchant Marine to HMM Co., Ltd. on April 1, 2020. The tracking portal is at hmm21.com. There has been no subsequent rebrand, and the company continues to operate under the HMM name. If you have historical bookings under “Hyundai Merchant Marine,” they should be accessible through the current HMM portal.

The portal accepts container numbers, B/L numbers, and booking references. Basic tracking is available without login. Registered users get access to additional features including documentation, invoicing, and notification preferences.

Container prefixes require attention. HMM’s SCAC code is HDMU — not HMMU, which is the prefix many teams assume. HMMU is a secondary prefix. The full range includes HDMU (primary), HMMU, HAMU, KOCU, GHMU, HDGU, and HMRU. If you are searching for an HMM container and using HMMU as your reference, you may be searching under the wrong prefix. Our identifier guide covers how to confirm which prefix maps to which carrier.

Event Names and What They Mean

HMM’s event labels use an inconsistent mix of gerund forms (“loading,” “discharging”) and past-tense forms (“departure,” “discharge”). Visibility platforms have documented this inconsistency — the same event type may appear differently depending on where in the tracking pipeline it was generated.

HMM Event Label	What Actually Happened	DCSA Code
Gate In	Laden container entered the origin terminal	GTIN
Loading / Loaded	Container was lifted onto the vessel at port of loading	LOAD
Departure	Vessel left the port of loading	DEPA
Vessel Arrival	Vessel is near the port (likely at anchor — see note below)	ARRI
Discharging / Discharge	Container unloaded from the vessel	DISC
Gate Out	Container left the destination terminal	GTOT

“Vessel Arrival” likely means at anchor, not berthed. Visibility platform Vizion explicitly confirms this semantics for ONE and Yang Ming — HMM’s Premier Alliance partners — and reports similar patterns for HMM. However, HMM’s own documentation does not definitively state this. According to third-party aggregator data, HMM’s “Vessel Arrival” event can precede berthing by several hours to days, depending on port congestion. The safest operational assumption is to treat it the same way as ONE’s anchor-based arrival: do not trigger downstream logistics until the “Discharge” event fires.

The gerund inconsistency is not a bug. HMM’s tracking system appears to pull event data from multiple internal systems that use different label conventions. “Loading” and “Loaded” refer to the same physical event. “Discharging” and “Discharge” refer to the same physical event. If you are building automated parsers, you need to handle both forms for the same milestone.

Update Cadence: How Fresh Is the Data?

HMM’s data freshness is comparable to other mid-tier carriers — events typically appear on the portal within 4-12 hours of occurring. The company does not publish specific lag metrics. Based on observed behavior through visibility platforms, the synchronization frequency is in line with ONE and Yang Ming — HMM’s Premier Alliance partners.

The bot protection can interfere with frequent checks. If you are refreshing the tracking page repeatedly in a short period to watch for updates, the bot detection system may flag your session and block access. Space out your manual checks or use a registered account to reduce the likelihood of triggering the protection.

HMM is reportedly rolling out a digital overhaul in 2025-2026 that unifies its e-commerce platform, EDI/API systems, and SmartShip IoT capabilities. The SmartShip IoT program would add container-level location data beyond traditional milestone tracking. However, specific timelines and feature details have not been confirmed, so it is unclear what impact this will have on tracking data freshness or portal capabilities in the near term.

Known Gaps and Quirks

The API portal is primarily in Korean. HMM’s developer portal at apiportal.hmm21.com is live, with Swagger/OpenAPI 2.0 documentation and POST-based endpoints. But the primary language is Korean. Registration requires name, ID, password, account number, and business number. The terms of service date from 2021. For non-Korean development teams, this represents a significant barrier — not just the language, but the registration requirements that assume familiarity with Korean business identification systems.

HDMU vs HMMU confusion is real. HMM’s SCAC code is HDMU, but the carrier’s name starts with HMM, leading many teams to assume HMMU is the primary prefix. If you are filtering containers by SCAC code in your TMS and looking for HMMU, you may be missing the majority of HMM containers. Update your prefix mapping to use HDMU as the primary.

Bot protection blocks legitimate automated access. The Incapsula/Imperva-style bot detection on HMM’s e-service pages does not distinguish between malicious bots and legitimate monitoring tools. If your operations team uses browser-based monitoring tools to check tracking status, those tools may be blocked. The API is the intended path for automated access, but that requires navigating the Korean-language portal.

Premier Alliance reliability is the lowest among alliances. HMM, ONE, and Yang Ming formed the Premier Alliance effective February 9, 2025. The alliance’s schedule reliability sat in the mid-to-high 50s percent range in 2025 — the lowest among the three major alliances (Gemini at 92.3%, Ocean Alliance in the mid-range) per Sea-Intelligence data. This means nearly half of Premier Alliance sailings deviate from the published schedule.

No “Available for Pickup” event. HMM does not publish a combined availability status. After “Discharge,” you need to independently verify customs clearance, freight release, and terminal availability before dispatching pickup.

State ownership adds a policy dimension. HMM is approximately 65% state-owned through Korea Development Bank (~32.6%) and Korea Ocean Business Corporation (~32.28%). Privatization has been attempted but not completed: the Harim-led deal collapsed in February 2024, and bidding activity resumed in late 2025 with Dongwon Group renewing its exploration. For most shippers, this has no direct impact on tracking. But it means HMM’s technology investment decisions are influenced by government policy priorities, which may explain the slower pace of digital modernization compared to privately held carriers.

Transshipment visibility is limited. HMM’s event table does not include dedicated transshipment milestones. If your container routes through a Premier Alliance hub, the tracking timeline may show a gap between the departure event and the final arrival event with no intermediate updates. This is similar to CMA CGM and ONE’s thin transshipment coverage. For shipments with known transshipment legs, contact HMM directly for hub status updates rather than waiting for the portal to surface them.

What to Do When Tracking Breaks

Scenario 1: Portal shows “Your access has been limited.” HMM’s bot detection has flagged your connection. Try accessing from a different network, disable any VPN, and clear your browser cookies. If the issue persists, contact security@hmm21.com. Using a registered HMM account may reduce the frequency of bot detection triggers.

Scenario 2: “Vessel Arrival” posted but terminal says vessel has not berthed. This is likely the anchor-vs-berth issue. According to aggregator data, HMM’s “Vessel Arrival” may fire when the vessel is near the port, not when it has berthed. Wait for the “Discharge” event before taking operational action. Check the vessel’s position on MarineTraffic to confirm whether it is at anchor or at berth.

Scenario 3: Container search by HMMU returns no results. Try HDMU. HMM’s SCAC code is HDMU, not HMMU. HMMU is a secondary prefix that covers a smaller portion of the fleet.

Scenario 4: Trying to build an API integration. HMM’s API portal is functional but documented in Korean. Options: (1) Use browser translation tools to navigate the Swagger docs and registration process, (2) engage a Korean-speaking developer for the initial setup, or (3) use a third-party visibility platform that has already built the HMM integration. Option 3 is the fastest path for most non-Korean teams.

Scenario 5: Same event appears as both “Loading” and “Loaded.” This is HMM’s gerund inconsistency. Both labels refer to the same physical event. Your parser needs to treat them as equivalent. If you are mapping to DCSA codes, both map to LOAD.

API and Integration Options

HMM’s API portal at apiportal.hmm21.com is live with Swagger/OpenAPI 2.0 documentation and POST-based endpoints. Authentication is via API key. The schedule API has a 300 calls/hour rate limit. The terms of service are from 2021, suggesting the portal has been stable but not actively updated.

The primary language barrier is the biggest obstacle. Documentation, registration forms, and legal agreements are in Korean. Registration requires a name, ID, password, account number, and business number — the latter two are standard Korean business identifiers that non-Korean companies may not have. For Western development teams, this is more than a language issue — it is a process issue.

HMM is a DCSA founding member and has participated in DCSA Booking and eBL pilots. The API output should follow DCSA event structures, but confirming the exact DCSA version and event coverage requires navigating the Korean documentation. In practice, most non-Korean teams that need HMM tracking data use third-party visibility platforms rather than building direct API integrations.

HMM’s fleet is expanding significantly. The company has a multi-year investment plan valued at approximately $17.5 billion (KRW 23.5 trillion), targeting around 1.5 million TEU capacity by 2030 after an April 2024 upward revision, with a return to trans-Atlantic routes. As the fleet grows, the volume of tracking data and the importance of API accessibility will increase. Whether HMM will modernize its English-language developer experience to match this fleet expansion remains to be seen.

Operational Note: HMM’s tracking story is one of capable infrastructure behind language and access barriers. The API exists and follows DCSA standards, but the Korean-language documentation makes it inaccessible to most Western development teams. The portal works but bot protection blocks automated access. The event labels are functional but inconsistently formatted. For teams shipping regularly on HMM, the most practical approach is either a direct relationship with HMM’s Korean-speaking support team or integration through a visibility platform that has already navigated these barriers.

Leave a ReplyCancel reply

New Report: The Future of SCM, and Why Visibility Alone Is No Longer Enough

[TRADLINX Report] 2026 Shipping Market Outlook: Falling Rates, Rising Risks