Arkas Line has pulled Novorossiysk from its Russia Express Service (REX) and made St. Petersburg the loop's Russian gateway, restoring the carrier's coverage of Russian ports through the Baltic, according to DynaLiners.

The redirection is the operational aftermath of a single casualty. Arkas suspended the service after the FESCO-operated containership FESCO Yanina sank near Novorossiysk in August, and the revised rotation published by DynaLiners confirms the Black Sea call has not returned.

Under the new configuration, the REX port sequence runs:

• Alexandria – Mersin – St. Petersburg – Alexandria.

The shift moves the Russia Express Service away from the Black Sea entirely while keeping the trade linkage between Russia, Türkiye and Egypt alive — now through a Baltic entry point roughly a sea-voyage away from the service's previous Russian call.

What has changed on the water?

The service is small by mainline standards. Two container ships operate the loop, with an average capacity of approximately 1,200 TEU each, sailing at intervals of two to three weeks.

For context, 1,200 TEU is a feeder-scale vessel — well under a tenth of the capacity of the 18,000-plus-TEU units deployed on Asia–Europe trades. A fortnightly-to-triweekly frequency on a three-port loop means shippers moving cargo between Türkiye, Egypt and Russia on REX now face a materially different routing.

Cargo that previously discharged at Novorossiysk, on Russia's Black Sea coast, must now move through St. Petersburg in the Baltic. That single substitution stretches the ocean leg considerably and changes the inland distribution picture for Russian consignees from southern to northwestern corridors.

Why the suspension happened

The trigger was the loss of the FESCO Yanina. The FESCO-operated ship sank near Novorossiysk in August, and Arkas responded by suspending the REX service altogether rather than seeking an immediate substitute Black Sea call.

That decision now looks structural. By rewriting the rotation to omit Novorossiysk rather than pausing and reverting, Arkas has effectively repositioned its Russia exposure to the Baltic.

DynaLiners is the source for the revised port sequence and the fleet details; Arkas itself has not, in the material available, elaborated on the commercial reasoning behind the gateway choice or on how long the new configuration will hold.

What it means for shippers and forwarders

The immediate consequences fall on three groups:

• Russian importers and exporters using the Türkiye–Egypt–Russia corridor must plan for Baltic discharge at St. Petersburg instead of Black Sea entry at Novorossiysk, with knock-on effects on inland transport costs and transit times.
• Shippers on the Alexandria and Mersin legs keep their direct connections, but on a two-to-three-week sailing interval — capacity that will constrain anyone needing weekly coverage.
• Competitors serving Novorossiysk, including FESCO's own services, face one fewer caller at the Black Sea hub, which may tighten slot availability on remaining loops.

A caution is warranted on scale. Two ships of roughly 1,200 TEU on a two-to-three-week frequency is a modest commitment, and the reported figures are averages rather than fixed capacities. The service's durability in its new form — and whether Arkas restores a Black Sea leg later — remains an open question the carrier has not addressed publicly.

What comes next

The tighter variable to watch is whether the Baltic gateway holds. If Arkas keeps REX on the Alexandria–Mersin–St. Petersburg routing, the Türkiye–Egypt–Russia trade will have quietly migrated from the Black Sea to the Baltic; if Novorossiysk returns to a future rotation, the change will read as a temporary casualty-driven workaround rather than a strategic repositioning.