⚓ Gosships Intelligence

Gosships Intelligence Is Published At Gosships.com

For Sponsorship And Partnership Inquiries Contact intelligence@gosships.com

|⚓ About Us | 🛢️ Exclusive Report | 📋 SwiftAction Training |

**🏅Black Gold Membership (*53 Slots Left)**

On August 26 Bloomberg reported that MSC, the world’s largest container line, had suspended new bookings into and out of Novorossiysk, and an employee at its St Petersburg office confirmed to the wire that operations in Novorossiysk were idled. Russian-language outlets ran it as MSC leaving Russia’s Black Sea ports. That is not what happened. The service it paused had been restricted to food, medical and humanitarian cargo since March 1, 2022. The company still works St Petersburg, and its own Russia page carried a Novorossiysk feeder schedule when this brief read it on August 30 and again on September 1. The move that puts the world’s largest carrier on one shore of this war was filed in May. Nobody announced it.

Ukraine's state register lists Container Terminal Pivdennyi LLC, registration 37468475, with 81.625 percent of its shares held by a Dutch company in Rotterdam. Ownership data behind that company puts Diego and Alexa Aponte at 25.5 percent each of the terminal company, 51 percent between them, held indirectly. They have owned MSC since late 2025, a transfer the company announced itself on April 13, with the founder staying on as executive Chairman.

They did not buy it from DP World, which is the version now in circulation. DP World sold its 51 percent back to TIS Group, its Ukrainian joint venture partner since 2020, and said so in a written answer to a query from a Ukrainian agricultural news site on March 18. Two months passed. Then the register changed.

There was no announcement of any of it. No press release, no securities filing, no competition decision this brief could locate. It surfaced on June 1 because Latifundist noticed that a line had moved in a corporate database. Three months later neither MSC nor TIS has commented publicly, TIS having declined when Latifundist asked, and Alphaliner’s note, as carried on June 3, recorded the deal as finalised but subject to confirmation.

The sea around that terminal has meanwhile been repriced, and nobody can tell you precisely how bad it got. Four bodies published counts of vessels hit or attacked in this war inside 12 days of each other and none of them agrees. Only one breaks its total down by who did the shooting, and it puts 93 on Russia and 47 on Ukraine.

The notice everyone read was a pause on a service that had already been reduced to almost nothing. The commitment nobody read was a controlling stake at a container berth on the Ukrainian shore, filed while the drones were still flying.

📋 In This Issue:

⚖️ The Story:
What the Novorossiysk notice actually said and who confirmed it, the vessel that triggered it and the four things nobody can establish about it, the terminal purchase that was never announced, why four institutions cannot agree how many vessels have been hit and why the straits did not clog.
📊 By The Numbers:
The stake, the register dates, four counts between 146 and 262, the two war risk numbers that are not a range, the transit figures that refute the queue and the confirmations MSC, TIS and DP World have never given.
🔍 Why It Matters:
What changes for the tanker owner, the charterer, the war risk underwriter and the grain trader.
👀 What To Watch:
The five markers that will show whether this was a commitment or a hedge, including the two that would prove this reading wrong.
🚨 Gosships Signal:
Why the register moved and no announcement followed.

🔔 Not A Member? Unlock The Full Analysis, Data Cards, Archive, & More!

Get 50% off for 1 month

📊 Order Our Exclusive Report
→ Global Tanker Market Outlook Q3 2026 Edition

📋 Competency-Based Maritime Training
→ SwiftAction

🔗 Related Coverage

📌 Gosships Data Card

March 1, 2022: MSC begins accepting bookings only for food, medical and humanitarian cargo moving to or from Russia. The restriction is still stated on the company’s own Russia page four and a half years later (MSC Russia page, read August 30 and again September 1).

March 18: DP World tells the Ukrainian outlet Latifundist, in a written answer to a query, that it “has sold its 51% stake in the container terminal in Pivdennyi, Ukraine, as well as the associated marine services business back to TIS.” DP World asserts in the same statement that the relevant regulatory approvals had been obtained and the transaction completed, but gives no date for the signing, the clearance or the completion, and no press release, filing or regulator notice has been located. The buyer is TIS, not MSC (Latifundist, March 18; CFTS, April 1).

May 14: The ownership structure document for Container Terminal Pivdennyi LLC is filed with Ukraine’s state register. Ownership data captured the following day shows Diego Aponte and Alexa Aponte at 25.5 percent each. This is a filing date rather than a confirmed closing date, and only mid-May is supported for the closing itself (Ukrainian state register via Clarity Project, read August 31; YouControl data as of May 15 via Latifundist, June 1).

June 1: Latifundist notices the change in the registry data and publishes at 13:16 Kyiv time. USM.media follows at 13:32, and CFTS and ZN.ua the same afternoon. There is no announcement from any party. International reporting begins the following day and Alphaliner’s own note, carried on June 3, records the deal as finalised but subject to confirmation (Latifundist, USM.media, CFTS and ZN.ua, June 1; Kyiv Independent, June 2; Splash247 and The Loadstar, June 3).

August 21: The roro Ural, IMO 7725386, Turkish-owned and Cameroon-flagged, is struck off Novorossiysk while carrying 18 seafarers she had taken off the Necibe. İlker Lazoğlu, aged 47, is killed and eight others are injured. He was the Necibe’s chief cook, taken off her by the Ural’s crew three days before. The Ural continues her voyage and is reported as expected at Samsun the following day (Maritime Executive, August 24; Cumhuriyet, August 22; Xinhua, August 22).

August 25: The MSC Ulsan III, IMO 9305001, is struck by a drone. No party has claimed the attack and no named source attributes it. The date comes solely from EOS Risk Group; Bloomberg states that “The company didn’t say when the incident occurred.” Direction of travel is contested: MSC’s own customer notice, as quoted by Bloomberg, says the vessel was en route to Novorossiysk, while EOS Risk Group and the trade press that followed it have her outbound from Novorossiysk toward Turkish waters (EOS Risk Group via Maritime Executive, August 27; Bloomberg, August 26; Container News, August 27; Marine Insight, August 28).

August 26: Bloomberg reports that MSC has suspended new bookings into and out of Novorossiysk, citing a notice to customers seen by the wire. The wire reports that the company is pointing customers at its Russia agency to find other ways of moving import and export cargo, and framing that as an interim step until weekly sailings from the port can start again. Bloomberg records that “An employee at the company’s St. Petersburg office confirmed to Bloomberg News that operations in Novorossiysk are currently idled,” while its request to the press service was not immediately answered (Bloomberg, Pyotr Kozlov, August 26).

August 27: The Turkish Shipowners Association publishes a tally dated the previous day putting 146 merchant vessels in the hit or damaged column since February 24, 2022, and attributing 93 of them to Russia, 47 to Ukraine, five to mines and one to an unknown cause. At that same council the İMEAK Chamber of Shipping's own chairman, Tamer Kıran, gives a different figure for the same war, 226. Neither reconciles with the other, nor with Ukraine's own two counts of 262 on August 21 and more than 240 on September 1 (Türk Armatörler Birliği via 7deniz Haber, August 27, and Dünya, August 28; Tamer Kıran via Vira Haber, August 28; Serhii Derkach via gCaptain, August 21; Mariana Betsa via Ukrinform, September 1).

⚖️ The Story

What The Notice Said, & What It Did Not

The document at the centre of this is a customer notice, not a press release. Bloomberg has seen it and no other outlet has published it, so every account of the suspension in circulation descends from that one wire story by one reporter.

The company did confirm it, though not in the way a reader would assume. Its press service did not immediately answer Bloomberg’s request for comment. An employee at its St Petersburg office confirmed to the wire that operations in Novorossiysk were idled, which is a confirmation from a staffer at a different port rather than a statement from the company.

What the wire actually reports is narrow. New bookings to and from Novorossiysk are suspended, and the company is pointing customers at its Russia agency to find other ways of moving cargo until weekly sailings from the port can start again. That is a pause, and pauses are written to be lifted.

Three facts sit against the reading that MSC has left Russia. The first is that the service being paused had already been cut to almost nothing: since March 1, 2022 the company has accepted bookings only for food, medical and humanitarian cargo on Russian services, a restriction still printed on its own Russia page. The second is St Petersburg, where the company continues to work. The third is the page itself, which on August 30 still carried Novorossiysk, the NUTEP terminal and a Novorossiysk feeder schedule document, with no suspension notice anywhere on it.

A suspension of new bookings on a humanitarian-only service, at the one Russian Black Sea port this carrier serves, is not an exit. It is a risk decision about that port.

Which Side Of The Black Sea Did MSC Pick?

Comments on this post are for subscribers