TRADLINX

Four carrier announcements in the past few days revised seven services across the Adriatic, West Africa, the Far East–Bangladesh trade, and an intra-Asia loop. Most are rotation and vessel-provider changes rather than new launches, which makes them easy to miss and costly to overlook: the booking still exists, but a port call, a transit assumption, or which carrier actually carries your box may have changed. Here is each one and the specific assumption it puts in question.

Changes below are reported by Container News, drawing on schedule trackers including Alphaliner and DynaLiners and, for WAF7, Maersk’s own information; effective dates are not specified for every change.

Maersk / ONE — Adriatic AD1, now “Adriatic Sea”

What changed: Maersk replaces ONE as vessel provider on the jointly operated Adriatic service (run with Admiral Feeders) and will market it as Adriatic Sea. ONE stays in the partnership as a slot charterer, but with limited port coverage. The rotation also changes: Haifa and Ashdod replace Aliaga and Piraeus.

Revised rotation: Koper, Venice, Ancona, Haifa, Ashdod, Damietta, back to Koper.

Re-check if: you move boxes through Aliaga or Piraeus on this service — both are off the rotation. And if you book via ONE rather than Maersk, note that ONE’s slot agreement does not include the new Haifa and Ashdod calls, so Israeli-port coverage on this loop is a Maersk-booking question now.

Maersk — WAF7 (Mediterranean–West Africa)

What changed: A seasonal extension to South Africa for the fruit export season. WAF7 adds Pointe Noire (Republic of the Congo) and Port Elizabeth (South Africa), and drops Freetown. Freetown is now served by a separate Northern West Africa Plus (NWAP) feeder running Tangier–Freetown.

Revised rotation: Tangier, Conakry, Pointe Noire, Port Elizabeth, back to Tangier.

Re-check if: you ship to or from Freetown — your cargo moves to the NWAP feeder rather than the mainline WAF7, which may change transit and, for cargo originating beyond Tangier, introduce or alter a transshipment leg. If you ship South African or Congolese cargo on this corridor, the new direct calls are the upside.

Maersk — Far East–Bangladesh network (SH1, SH2, SH3, IA7)

What changed: Following the earlier SH2 revision, Maersk adjusted four services across the Far East–Bangladesh trade, per Alphaliner. All four call Chittagong, so a Bangladesh shipper may have more than one rotation to re-check depending on which string carries the cargo.

• SH1: removes Hong Kong, Qui Nhon and Da Nang. New rotation: Ningbo, Shanghai, Xiamen, Port Kelang, Chittagong, Port Kelang, Tanjung Pelepas, back to Ningbo.
• SH2: Ningbo, Shanghai, Kaohsiung, Tanjung Pelepas, Chittagong, Singapore, Qui Nhon, Da Nang, Hong Kong, Keelung, back to Ningbo.
• SH3: Nansha replaces Kaohsiung; northbound Mongla and Tanjung Pelepas calls removed. New rotation: Yokohama, Kobe, Qingdao, Shanghai, Nansha, Tanjung Pelepas, Port Kelang, Chittagong, Tanjung Pelepas, Ho Chi Minh, Shenzhen (Yantian), back to Yokohama.
• IA7: no longer calls Shantou. New rotation: Hong Kong, Shenzhen (Yantian), Nansha, Tanjung Pelepas, Port Kelang, Chittagong, Tanjung Pelepas, Nansha, back to Hong Kong.

Re-check if: you route Far East–Bangladesh cargo and your origin is Hong Kong, Qui Nhon, Da Nang (off SH1), Mongla (off SH3 northbound), or Shantou (off IA7). The Chittagong call holds across all four, but the other Asian port calls have shifted.

If your team is reconciling rotation changes like these across several carriers and strings, watching which revised service actually carries each booking — and catching a dropped port call before the box is already routed — is the kind of exception that is easy to miss in a spreadsheet. Walk through how ops teams track service and rotation changes across carriers in one view.

CNC Line — KCM2 (Korea–China–Malaysia)

What changed: CNC Line cut KCM2 from seven to six vessels of roughly 4,250 TEU and revised the rotation, per DynaLiners. The service removes Shantou and the second Busan call, and adds Xiamen.

Revised rotation: Tianjin, Busan, Qingdao, Ningbo, Shanghai, Shenzhen (Shekou), Port Kelang, Penang, Port Kelang, Singapore, Nansha, Xiamen, Qingdao, back to Tianjin.

Re-check if: you ship through Shantou on KCM2 — the direct call is gone. The cut from seven vessels to six is also worth noting, but it does not on its own mean fewer departures: the shorter revised rotation may let CNC hold the same frequency with one fewer ship. Check the published schedule rather than assuming reduced sailings.

The pattern under the notices

Across the week, the changes split into three types: a provider-and-rotation reshuffle (Adriatic, where which carrier holds your slot now determines port coverage), seasonal extensions (WAF7 to South Africa), and deployment trims (CNC cutting a vessel on KCM2). The common thread for a planner is that none of these is a headline launch — they are quiet edits to live services, and the cost of missing one is a box routed on an assumption that no longer holds.

The practical takeaway is narrow: when a service you book gets revised, confirm three things before the next sailing — whether your specific port calls survived, whether the vessel provider or slot arrangement changed who carries your cargo, and whether the effective date applies to a booking already in motion.

Further Reading

• Maersk replaces ONE as vessel provider on Adriatic service (Container News)
• Maersk extends WAF7 service to South Africa (Container News)
• Maersk revises Far East–Bangladesh service network (Container News)
• CNC Line revises KCM2 service (Container News)

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).