The Belawan port code is IDBLW. Five characters, no spaces, no punctuation, and the same five characters whether they appear on a bill of lading in Hamburg, a customs declaration in Medan, or a vessel-tracking screen in Singapore.

That is the short answer. The longer one matters more, because a code that looks this simple is responsible for a surprising share of the delays that hit Sumatran export cargo. This guide covers what each part of the code means, who maintains it, where it is required, and the specific errors that get shipments queried at the wrong end of a voyage.

Last updated: 31 August 2026

What the Belawan Port Code Actually Is?

IDBLW is a UN/LOCODE, short for the United Nations Code for Trade and Transport Locations. The system is maintained by the UNECE secretariat and has been running since 1981, when the first edition covered around 8,000 places. It now carries more than 103,000 locations across 249 countries and territories.

The point of the system is that a location should have exactly one identifier that survives translation, transliteration, and local spelling habits. “Belawan” is unambiguous in English. It is less so once it passes through a Chinese-language booking system, a Korean customs form, and a Greek shipowner’s operations desk in the same week. IDBLW passes through all three unchanged.

The Belawan port code is therefore not a label the port chose for itself, and not something Pelindo or any terminal operator can amend. National focal points, usually a country’s customs administration or national statistics office, submit new entries and amendments, and UNECE verifies and publishes them. The dataset is open, free to download, and revised twice a year.

How the Five Characters Are Built

Every UN/LOCODE splits at the same point. The first two characters are the country under ISO 3166-1 alpha-2. The last three identify the place within that country.

BLW is not arbitrary. UNECE tries to build a mnemonic link to the place name wherever the combination is still free, which is why NLRTM reads as Rotterdam and DEHAM reads as Hamburg. That courtesy is getting harder to extend. With only 17,576 three-letter permutations per country, large maritime nations are running out, and the code structure rules permit digits 2 through 9 as substitutes once letters are exhausted.

One detail from those rules explains a lot of transcription errors. The digits 0 and 1 are never used, because on a monospace screen or a faded dot-matrix bill of lading they are indistinguishable from the letters O and I. The people who designed this system in the 1970s had watched enough documents go wrong to legislate against it.

Codes are republished twice yearly, with submission cut-offs at the end of April and the end of October according to the UNECE executive guide. Any system holding a hard-coded copy of the list drifts out of date on that same cycle.

Where the Belawan Port Code Is Required

IDBLW is not decorative. It is a required field in more places than most exporters realise, and the failure mode is usually a query rather than a rejection, which is worse: the paperwork moves, then stops somewhere expensive.

Two consequences follow. First, an error in the Belawan port code propagates. It is entered once, then copied automatically into every downstream document, which means a typo caught at booking costs minutes and the same typo caught at discharge costs days.

Second, anyone quoting freight to or from northern Sumatra is better off searching by code than by name. Port-name searches return partial matches and near-misses. IDBLW returns one place.

What the Code Does Not Tell Anyone

A UN/LOCODE identifies a location. It says nothing about what happens there. IDBLW does not indicate which terminal inside the port a container is destined for. Belawan contains several, including the container facility known as BICT, and terminal-level identification uses a separate code system entirely. Booking a box to IDBLW is roughly as precise as addressing a letter to a city rather than a street.

The code also carries no information about depth, berth availability, equipment, opening hours, or whether a vessel of a given size can actually be accommodated. Those live in port handbooks and terminal agreements. A forwarder who treats a matching LOCODE as confirmation that a service exists will eventually book cargo onto a route nobody sails. And national customs systems frequently maintain their own port code lists that do not map cleanly onto UN/LOCODE. The code required on an Indonesian import declaration is not automatically IDBLW.

Common Mistakes With the Belawan Port Code

Four errors account for most of the trouble, and all four are avoidable:

1. Confusing Belawan with Medan. This is the most frequent one by a wide margin. Medan is the city, roughly 18 kilometres inland; Belawan is the seaport that serves it. They hold separate entries in the UN/LOCODE list. Cargo booked against the Medan entry when the vessel calls at Belawan produces a mismatch between the booking and the manifest, and the discrepancy usually surfaces during customs processing rather than at the desk that created it.
2. Treating the Belawan port code as a terminal code. IDBLW gets a container to the port. It does not nominate BICT, or any other facility inside it. Terminal nomination is a separate field, and leaving it to be inferred invites the wrong inference.
3. Reversing or mistyping the segments. IDBLW, not BLWID. The country code always leads. This sounds too obvious to mention until it appears in a manifest, at which point it validates against nothing and the message is rejected without explanation.
4. Working from a stale code table. Systems that cached the LOCODE list years ago and never refreshed it drift on the same twice-yearly cycle the list is published on. Codes are added, corrected, and occasionally retired.

None of these is a difficult problem. They persist because the code looks trivial, so nobody checks it, and because the person who enters it is rarely the person who discovers the error.

Belawan at a Glance

Context for anyone using the Belawan port code without having worked the lane before. Figures below are drawn from published port data and should be verified against current sources before commercial use.

Belawan is served by a long list of international and regional carriers, and current schedule and connectivity data is a better guide to live services than any static table. Detailed operational figures including annual throughput are published in commercial port databases.

The maximum draft figure is the one worth noting. At roughly 10 metres, Belawan sits well below what fully laden Panamax and larger vessels require, which shapes how cargo from northern Sumatra reaches deepwater tonnage and why additional port capacity in the region keeps being proposed.

Frequently Asked Questions

What is the Belawan port code?

The Belawan port code is IDBLW. It is a UN/LOCODE, where ID is the ISO country code for Indonesia and BLW identifies Belawan. The code appears on bills of lading, manifests, customs declarations, and carrier booking systems worldwide.

Is the Belawan port code the same as the Medan port code?

No. Medan is the city and Belawan is the seaport serving it, roughly 18 kilometres away, and each holds a separate UN/LOCODE entry. Using the Medan code for cargo moving through Belawan creates a mismatch that typically surfaces during customs processing.

Who assigns the UN/LOCODE for Belawan?

The UNECE secretariat maintains and publishes UN/LOCODE. National focal points, usually a country’s customs administration or statistics office, submit new entries and amendments. Neither the port operator nor any shipping line can alter a code independently.

Does IDBLW identify a specific terminal?

No. IDBLW identifies the port as a whole. Terminals inside Belawan, including the container facility BICT, are identified through a separate coding system. Terminal nomination is a distinct field on booking and documentation.

How often do UN/LOCODEs change?

The list is republished twice a year, with submission cut-offs at the end of April and the end of October. Entries are added, corrected, and occasionally retired, so cached code tables should be refreshed on the same cycle.

Belawan and What Is Being Built Beside It

Belawan handles the majority of northern Sumatra’s seaborne trade from a site with a draft limit of roughly 10 metres, which constrains the vessel classes that can call and, by extension, the freight cost the region absorbs.

SIIPE (Sumalacca Integrated Industrial and Port Estate) is a planned integrated industrial estate and bulk port development in Medan Belawan, positioned about 4.7 km from Belawan Port on the Strait of Malacca. The port component is at the planning stage and is not operational. The estate is masterplanned so that industrial plots sit within 5 km of its own planned jetty.

Operators evaluating northern Sumatra as a manufacturing or transhipment base can review the industrial land available at SIIPE, or request current port specifications and development-phase detail at info@siipe-port.com or on WhatsApp at +62 811 860 980.