OpenNavData — open official data along your route · Help · Cases · What's new · Coverage by country · About
Home › Cases › Northern Sea Route vs Suez: Busan to Rotterdam
Northern Sea Route vs Suez: Busan to Rotterdam
Computed on 2026-11-18, beta 3.8.0, valid until 2026-12-18. Figures from OpenNavData's engine on the inputs shown. Reference values illustrative, as of Oct 2026, valid until 2027-01-31; not market quotes.
From Busan to Rotterdam, the Northern Sea Route (NSR) is 7 941.2 nm and the route via Suez 10 946.4 nm (−3 005.2 nm). For a 14 000 TEU class container ship at the same speed, the table compares days, fuel, CO₂, EU ETS and costs; the NSR fee has no reference value yet, so the NSR total is shown without it.
The task
Compare the voyage from Busan (KRPUS) to Rotterdam (NLRTM) via the Northern Sea Route with the voyage via the Suez Canal, for a 14 000 TEU class container ship.
The data used
- The routes: OpenNavData's generated route via Suez, and the route with the NSR requested.
- The ship: EU MRV figures of a real 14 000 TEU class ship.
- The EU ETS rules and factors from EUR-Lex.
- Prices, EUA, hire, the Suez toll and war risk: OpenNavData illustrative reference values, not market quotes.
The NSR route says nothing about ice, season or permits: an NSR voyage needs a permit and, depending on the season and the ice class, escort. Those are outside these figures.
The fields
| input | value |
|---|---|
| ship | a 14 000 TEU class container ship — EU MRV 2025 figures of a real ship |
| fuel per mile (EU MRV) | 255.67 kg/nm at its average 13.66 kn |
| speed | 13.66 kn (the EU MRV average speed) |
| consumption | 83.8 t/day (speed law n = 3) |
| departure | 2026-12-01 |
| VLSFO, USD/t | 1 000 |
| MGO, USD/t | 1 300 |
| EUA, USD/t CO₂ | 95 |
| hire, USD/day | 90 000 |
| canal toll, USD | 900 000 |
| war risk, % of hull | 0.30 |
Ports: one working day at Busan, 1.5 at Rotterdam, with their illustrative costs — the inputs of the tool's container demo case.
The steps
- On the route page, build KRPUS → NLRTM.
- Under «③ Compare scenarios», add a scenario with the NSR requested.
- Fill the vessel and the prices on the Voyage estimate tab, then run the scenarios.
- Read the table, one column per route, and the differences.
The result
| via Suez | via the NSR | via the NSR − via Suez | |
|---|---|---|---|
| distance, nm | 10 946.4 | 7 941.2 | −3 005.2 |
| of which in ECAs, nm | 2 359.3 | 1 580.9 | −778.4 |
| sea days | 33.4 | 24.2 | −9.2 |
| total days | 35.9 | 26.7 | −9.2 |
| VLSFO, t | 2 195 | 1 626 | −569 |
| MGO, t | 568 | 380 | −187 |
| CO₂e, t | 8 791 | 6 381 | −2 410 |
| EU ETS, t | 4 396 | 3 190 | −1 205 |
| bunkers, USD | 2 933 056 | 2 120 342 | −812 713 |
| EU ETS, USD | 417 573 | 303 090 | −114 483 |
| canal, USD | 900 000 | 0 | −900 000 |
| war risk, USD | 270 000 | 0 | −270 000 |
| hire, USD | 3 230 051 | 2 405 051 | −825 000 |
| ports, USD | 320 000 | 320 000 | ±0 |
| total cost, USD | 8 070 680 | 5 148 484 | −2 922 197 |
Via the NSR the voyage takes −9.2 days, costs −2 922 197 USD and emits −2 410 t of CO₂e against the route via Suez. Reference values still pending, and so left out of the totals: nsr_fee.
Sources
- Routing network: Source: Eurostat, SeaRoute (EUPL-1.2), modified · Courtesy of Oak Ridge National Laboratory, U.S. Dept. of Energy.
- MARPOL areas: Marine Regions (VLIZ) CC BY 4.0 for the Baltic, North Sea, North American and US Caribbean rings; the IMO resolutions' coordinates closed by Natural Earth 10m for the rest (derived, ODbL); special areas: the Convention's Annex I, II, IV and V definitions closed by Natural Earth 10m (derived, ODbL)
- Source: EU MRV (THETIS-MRV, EMSA on behalf of the European Commission)
- EU ETS: Directive 2003/87/EC and Regulation (EU) 2015/757, EUR-Lex (the factors and their verbatim text: Help 12)
- Prices, EUA, hire, canal toll and war risk: OpenNavData illustrative reference values, not market quotes (Help 15)
- Source: PDOK / Rijkswaterstaat, CC0
- Source: Korea Hydrographic and Oceanographic Agency (해양수산부 국립해양조사원), data.go.kr, 이용허락범위 제한 없음 — datasets 항로 면형정보 20250813, 통항분리수역 20250714
How it works in the tool: Help 12 · Help 13 · all cases
Indicative corridor for data-procurement planning. Not a passage plan. Not for navigation.