- The strikes of 5 and 6 June 2026 did not destroy Mariupol's port, but they ended regular navigation. Before June every sailing was publicised as proof of revival; from mid-June the occupation administration published no sailings, no tonnage and no monthly plan, and by August it still had not.
- The port was already a loss-making state enterprise. In 2024 the port administration earned about 183 million roubles and lost about 54 million, roughly 30 roubles lost for every 100 earned, while the profitable cargo operations sat with separate Russian operators. Russia must now fund a 441 million rouble dredging contract, repairs and air defence for a port that earns nothing.
- The response has been political, not operational. A reconstruction project announced twelve days after the strikes said nothing about ship safety; the first "Maritime Council" of the "DNR" on 3 July discussed dredging and a passenger route to Rostov but gave no figure for ships handled or damage repaired; and on 27 August Pushilin proposed the port as a testing ground for counter-drone systems. The port has moved from the economic sphere into the security one, and freight has moved onto the land corridor.
In March 2026 TOT Insights traced the reoriented traffic through occupied Mariupol's port: coal, kaolin and scrap brought in by rail from occupied Donetsk and Luhansk, shipped out in small dry-bulk carriers to Russian ports and on to Turkey, much of it under flags and registrations designed to evade sanctions. That picture described a port that was working, narrowly but on a schedule. This briefing covers the three months after the strikes of early June 2026, in which the schedule disappeared, and asks what a port that cannot sail but must still be dredged, repaired and defended means for the economics of the occupation.
- 10 to 20sailings a month, November 2024 to mid-2025
- 183m / 54mroubles: port administration revenue and net loss, 2024
- 441mroubles: Coal Harbour dredging contract, May to October 2026
- 0published sailings, tonnage or plan figures after mid-June 2026
The port before June: working, narrowly
Through the first quarter of 2026 the port operated in a limited mode. The main shipping channel remained silted, its hydraulic structures damaged and its bed obstructed by sunken objects, so vessels used separate parts of the water area, the small entrance and some of the old berths near the ship-repair yard. Cargo turnover rested on coal, kaolin, scrap metal and a few other bulk goods delivered by rail from the occupied parts of Donetsk and Luhansk oblasts, accumulated on the port territory and dispatched in small dry-bulk carriers to Russian ports on the Azov and Black Seas. From November 2024 to the middle of 2025 the Centre for the Study of Occupation counted between ten and twenty departures a month: not a recovery, but enough to sustain a regular scheme for moving resources out.
The Russian side was preparing the port for larger vessels. The main project was the dredging of the Coal Harbour: about 400,000 cubic metres of spoil, a contract worth more than 441 million roubles, and a schedule of May to October 2026. Compared with the first quarter of 2025 the port was busier. But its operation depended on a handful of ships, a few berths and a small circle of shippers, and that narrow structure is what made it so vulnerable.
Costs without revenue
The port was loss-making before a single strike. For 2024 the state port administration, a unitary enterprise, reported revenue of about 183 million roubles and a net loss of about 54 million. The state structure maintained the berths, access tracks, security and other infrastructure, while the profitable part of the cargo operations could be routed to separate Russian operators and intermediaries. On every 100 roubles of revenue the administration lost about 30.
Stopping regular sailings makes that model worse, not different. Even with cargo sitting on the territory, the administration continues to pay for security, staff, repairs, electricity, berth maintenance and rail infrastructure, while transshipment income stops or arrives irregularly. If regular operation is not restored the port becomes ever more dependent on direct budget funding, and that at the moment of Mariupol's first budget cut and a general drive to optimise spending. Russia must simultaneously finance dredging, post-strike repairs, transport security and the running costs of an enterprise that does not produce a stable income.
5 and 6 June, and the silence after
In early June Russian military Telegram channels reported a series of attacks on vessels in the Azov Sea and on the port infrastructure of Mariupol and Berdiansk. On 5 June individual Russian channels reported cargo ships hit and crew members killed; the following day they reported a second attack directly on the territory of Mariupol's port, and one widely read Russian military channel stated plainly that the port had been attacked. The Russian side released no list of damaged vessels, no coordinates, and nothing on the state of berths, handling equipment, rail infrastructure or warehouses. The physical loss cannot be assessed from open sources.
What can be assessed is the administration's behaviour afterwards. Until June even a single ship call or the dispatch of a few thousand tonnes was presented as proof that maritime logistics were "reviving". After the strikes such reports practically disappeared. In the second half of June occupation sources published no data on ship calls, tonnage handled, coal dispatched or fulfilment of the monthly plan, and no confirmed report of a restored schedule. The pause itself is the finding: the Russian side had every political interest in demonstrating that the port was still working and produced no convincing evidence that it was.
That does not mean the port stopped entirely. Security, repairs, cargo accumulation, the access tracks, the movement of technical vessels and the restoration of damaged facilities could all continue. But regular cargo navigation was put on pause. Either ships could not be brought in safely, or they were being brought in with far more care than before: irregular night calls, transponders switched off, short time windows and electronic-warfare and air-defence cover. Both readings mean worse operating conditions, and neither is commercial shipping.
Dredging after the strikes
On 18 June, twelve days after the attacks, Russia's Unified Institute of Spatial Planning announced that it was preparing a technical project for the reconstruction of Mariupol's seaport. The announcement was framed as the continuation of systematic development work. It said nothing about how the safety of vessels would be ensured. Before the strikes the main constraint on the port was the depth of the channel; after them it was whether a ship could enter the water area at all. Dredging raises the permissible draught and tonnage. It does nothing against drones and nothing for insurance. The case for spending 441 million roubles on it became correspondingly weaker: even a completed project guarantees no increase in turnover if shipowners judge the route too dangerous.
The Maritime Council and the passenger route
On 3 July the first meeting of a "Maritime Council" under the "DNR" government took place. Its chairman opened by saying that systematic work on developing the maritime sector was beginning, a striking formulation after several years of statements that the port had been restored. The meeting discussed dredging, transport security, the development of the Mariupol and Berdiansk ports and a possible passenger route from Rostov-on-Don via Taganrog to Mariupol. It published no confirmed indicator of the port's actual operation since the strikes: not the number of ships handled, not the tonnage, not the date for restoring a regular schedule, not the list of damaged facilities, not the cost of repairs, not the companies willing to keep sailing. The Council was a political answer to the crisis, not a report on overcoming it.
The passenger route had, at the end of June, no confirmed operator, timetable, vessel, fare or launch date. After attacks on cargo ships the security problem for a passenger service is harder still, since the whole crossing of the Azov Sea would need protecting, not just the harbour. The route's function is to keep the theme of Mariupol's return to peaceful life in circulation without a project behind it.
Insurers and the land corridor
Regular operation depends on shipowners willing to carry the risk. After June that risk includes damage to the vessel, death of the crew, a repeat strike, the absence of standard insurance cover and sanctions exposure. For most international insurers a call at an occupied Ukrainian port was already unacceptable, so the Russian scheme relies on domestic insurers, captive operators or no full cover at all. Freight rates and risk premiums should have risen; the Russian side does not publish them. Reports circulating in Russian industry and military channels suggested that some owners of small dry-bulk carriers had suspended sailings or demanded extra payment. No individual refusal is documented, but the absence of regular calls in the second half of June is consistent with it.
The pause at sea coincided with a heavier load on the land route through Mariupol, Berdiansk and Melitopol. Cargo that could have gone by sea moved by road and rail, adding traffic to the R-280 highway, its access roads, filling stations and storage yards. The port's problems do not stop Russian logistics; they make it more expensive and more dependent on a single overland direction. In the first quarter sea and road complemented each other. From June the corridor began to compensate for the loss of regular shipping, which raises Mariupol's strategic weight as a transport node and its vulnerability at the same time.
August: from the economy to the security sphere
By August the picture had not changed. Where the October 2025 monitoring could follow a specific vessel, route and cargo, open occupation sources in August 2026 offered no systematic statistics on ship calls, tonnage or export destinations; transparency fell after the strikes and stayed down. On 27 August the regional labour inspectorate met the port administration and the transport prosecutor's office about workers' rights, which points to arrears or violations serious enough to need federal oversight, though no figures were published. The same day the head of the "DNR" proposed using Mariupol's port as a testing ground for systems to counter aerial, surface and underwater drones, including navigation without satellite signals and protected communications. The port had shifted from the public economic sphere into the security and military one, and the body of evidence contained no public proof that regular navigation had returned to its pre-June level.
Assessment
The June strikes did not destroy Mariupol's port. They broke the slow process of restoring regular navigation, and they exposed a model that was already unprofitable. In the first quarter the port's problem was low capacity; from June it was whether a voyage could be made safely at all. The administration's response was to stop publishing current figures and start talking about the future: a reconstruction project, a Maritime Council, a passenger route. The port has become an object of restoration again rather than a functioning economic enterprise, and Russia has acquired new costs for repair and security with no guarantee of recovering the previous turnover, at the same time as its dependence on the overland corridor has grown. Set against the March picture of a port busy evading sanctions, the summer shows what that traffic was worth to the occupier: less than it cost to keep the port open, and nothing at all once the ships stopped coming.
Sources and method
This briefing is based on the Centre for the Study of Occupation's monitoring of occupied Mariupol for June 2026, in particular its section on the seaport, and on the port section of its August 2026 report. The Centre draws on Russian federal, regional and occupation sources, on the port administration's published accounts for 2024, on Russian military Telegram channels for the reporting of the June strikes, and on the occupation administration's own announcements about the reconstruction project, the Maritime Council and the passenger route. Figures are presented as those sources' claims rather than as independently verified fact, consistent with the Centre's methodology. The underlying monitoring is held in the hub's private repository under its closed-monitoring policy. For the port's traffic and ownership structure while it was operating, see Shadow Fleet and Sanctions Evasion at Mariupol Port; for the budget context, Mariupol's 2026 Budget Amendment.
Corrections are reviewed by the research team and incorporated into the next update.