Russian Navy Frigates. Four Years of War at Sea

The lead frigate of the 11356R series joined the Black Sea Fleet on 11 March 2016. Hull number 494, home port — Sevastopol, 30th Surface Ships Division. The first five years of service were a standard story for a new ship: rotations to the Mediterranean, exercises, flag-showing. In May–June 2020 Grigorovich completed the longest voyage in Black Sea Fleet history — over 24,000 nautical miles in 134 days across the Atlantic, through Suez, and into the Indian Ocean. In February 2021 it participated in the multinational exercise Aman-2021 at Karachi, after which it was the first Russian warship in modern history to call at Port Sudan.

In 2021 the ship transited the Bosphorus southbound — for another rotation to the permanent Russian Navy squadron in the Mediterranean. This proved to be Grigorovichʼs last passage through the Turkish straits. Eight months later, 27 February 2022, Turkey invoked Article 19 of the Montreux Convention, classifying the Russian invasion as a war and closing the Bosphorus and Dardanelles to warships of the belligerents. Grigorovich was left outside the Black Sea — with no way to return to its home base.

From this point, the shipʼs entire subsequent trajectory was determined by geography, not tactics. Its new anchor point was the Russian naval base at Tartus, Syria. From there Grigorovich performed the duties of the permanent squadron: patrols of the eastern Mediterranean, rotations, calls at Latakia. In April 2023 the ship went for repairs via Gibraltar, the Bay of Biscay, the English Channel, and the North Sea — to the Baltic shipyard Yantar in Kaliningrad. The Royal Navy deployed the Type-23 HMS Defender for shadowing escort. In November of the same year Grigorovich completed the same route in reverse — back to Tartus, this time escorted by HMS Richmond.

The Russian presence at Tartus had been sustained by the Assad regime. 27 November 2024, the Hayat Tahrir al-Sham coalition and allied factions launched an offensive from northern Syria; eleven days later — 8 December — Damascus fell, and Assad flew to Moscow. Tartus and Hmeimim air base came under threat of seizure. Satellite imagery from Planet Labs, published by OSINT analyst MT Anderson, captured the sequence: 30 November – 1 December, Russian ships still at their berths; 3 December — the harbour already empty, the squadron had moved to the outer roadstead. On 8 December HUR MO confirmed: Grigorovich had left Tartus escorted by the cargo vessel Inzhener Trubin.[1]

After leaving Tartus the ship transferred to the Baltic Sea. Turkey will not permit a return to the Black Sea, so the new operational area became the Atlantic, the North Sea, and the Baltic. Here Grigorovich remains the only surface Caliber carrier of the Black Sea Fleet operating outside the Black Sea — and it is this that gave rise to its most significant episode of 2026.

That morning Leningrad Oblast suffered the largest drone attack since the start of the war — Governor Alexander Drozdenko reported strikes on “industrial and military facilities,” and the Russian Ministry of Defence claimed the destruction of 51 UAVs over the region. Pulkovo airport halted operations. The main naval parade in St. Petersburg, held annually since 2017, was cancelled in advance — officially for security reasons. It was the first cancellation in eight years.

Admiral Grigorovich, which had transferred to the Baltic after leaving Tartus, was at Kronstadt following 20 months of operational deployment in the Mediterranean. According to Russian media, the frigate participated in repelling the attack alongside ground-based air defences and the forces of the Leningrad Naval Base. That evening Vladimir Putin arrived in Kronstadt and boarded the ship.

The President spoke with the crew over tea, thanking them for “successfully repelling the drone attack.” Aksionov reported that during the shipʼs operational deployment it had covered over 87,000 nautical miles. This was followed by a public promotion of the commander:

This was the episode Russian state media made the centrepiece of Navy Day 2025. Instead of the traditional parade — the President on a warshipʼs deck, a commander, a repelled attack, and a live promotion.

The Telegraph published footage taken from the auxiliary vessel RFA Tideforce: Admiral Grigorovich was transiting the English Channel precisely between two sanctioned tankers. Universal, sailing under the Russian flag, had departed from Vysotsk; Enigma, flying the Cameroonian flag, had loaded at Ust-Luga. The British Type-23 frigate HMS Richmond was escorting the Russians in the North Sea. None of the vessels were stopped.[2]

A month earlier, Prime Minister Keir Starmer had publicly stated his intention to “push harder on the shadow fleet.” Grigorovichʼs passage between the two tankers in a combat escort configuration was the first recorded instance of Moscow deploying a warship in such an arrangement. The Kremlin officially characterised the operation as “protecting Russian shipping from piracy” in international waters.

Throughout spring 2026, the Russian military frigate Admiral Grigorovich continued to appear off the British coast and escort tankers of Russiaʼs so-called shadow fleet, despite Londonʼs promises to increase pressure on Russian shipping. According to British media, since April Admiral Grigorovich has escorted more than a dozen Russian tankers, auxiliary vessels, and one submarine through the waters around Great Britain.

Grigorovich remains in service — it is the only one of the three Project 11356R frigates that had not been struck in combat by May 2026. The paradox is that the price of this intact condition is the complete inability to fulfil its primary purpose — missile strikes against Ukrainian targets from the Black Sea.

The second frigate of the series joined the Black Sea Fleet on 7 June 2016 with hull number 490. Named after Nikolai von Essen — an admiral of the Imperial Russian Navy and commander of the Baltic Fleet during the First World War. Before the full-scale invasion Essen was based primarily at Sevastopol and performed routine Mediterranean rotation duties. The most notable combat episode before 2022 were Caliber launches against ISIS positions in Syria in September 2017 — the first confirmed combat launches of cruise missiles from a ship of this series.

On the first day of the full-scale invasion, Essen together with the cruiser Moskva approached Snake Island (Odesa Oblast). An ultimatum was transmitted over radio demanding the garrison lay down its arms. The recording, published by the State Border Guard Service of Ukraine, became one of the iconic artefacts of the war:

Ukrainian Wikipedia and official Ukrainian Navy materials indicate the ultimatum was read from Admiral Essen, not from the cruiser Moskva. Both ships took part in the seizure of the island — 13 Ukrainian border guards and naval personnel were taken captive, later exchanged.

On 29 March 2022 a Russian cruise missile struck the Mykolaiv Regional Military Administration building. The impact punched through the structure and several floors collapsed. 37 people were killed and over 30 wounded. Five months later the Ukrainian monitoring organisation Truth Hounds published an investigation attributing the strike to a specific ship — Admiral Essen. The team identified not only the ship but the officers who directly executed the launch: frigate commander Captain 2nd rank Alexander Smirnov and the commander of the missile-artillery combat unit, Senior Lieutenant Anatoly Peretyatko.[3]

In early April 2022, Admiral Essen as part of a Russian naval group approached the Ukrainian coastline off Tendra Spit. The Ukrainian Navy fired a Neptune anti-ship missile. This was the first-ever combat use of the Neptune — the system that, eleven days later on 14 April, would sink the cruiser Moskva.

The missile did not strike the hull directly. The explosion occurred near the ship, damaging weapon systems; there were several killed aboard. Essen urgently returned to Sevastopol for repairs. The first official confirmation came in February 2023 from Captain 1st rank Stepan Yakimyak. The full reconstruction of the episode appeared in an interview given by the Commander of the Ukrainian Navy, Vice Admiral Oleksiy Neizhpapa, to Ukrainska Pravda:[4]

On 19 June 2023 a Planet Labs satellite image captured Admiral Essen at Sevastopol with new paintwork: dark patches on the bow and stern of the hull. Essen became the first ship of the 11356R series to receive such camouflage.[5] As events in 2026 would show, the camouflage did not save it.

In autumn 2023 Sevastopol ceased to be a safe base. On 13 September, Storm Shadow cruise missiles struck the large landing ship Minsk and the diesel submarine Rostov-on-Don at the Sevastopol Maritime Plant. On 22 September — a Storm Shadow strike on the Black Sea Fleet headquarters. Planet Labs imagery from 1–3 October 2023, published by MT Anderson, records the arrival of two frigates at Novorossiysk port — Admiral Essen and Admiral Makarov. This was the largest change of basing in the Black Sea Fleet during the full-scale war.

In the night of 2 March 2026, Ukraineʼs Security Forces and Defence Forces conducted a combined strike against the Novorossiysk naval base. Admiral Essen took a hit to the midship superstructure; secondary detonations followed. Confirmed damage to the PK-10 decoy system, TK-25 EW system, MR-90 and Fregat-M2M radars. A fire on deck burned for approximately 18 hours.[6]

In the night of 6 April, Ukraineʼs Security Forces and Defence Forces struck the Sheskharis terminal and ships directly in the Novorossiysk naval base. According to OSINT analysis by CyberBoroshno based on satellite imagery taken on 7 April, Admiral Essen was struck in the bow section — in the area of the 100mm A-190 gun mount. In the same zone below the waterline sits the MHK-335M Platina hydroacoustic complex: damage to it would deprive the ship of submarine detection capability. The OSINT identification of Essen — as opposed to the neighbouring Makarov — was based on a distinctive feature: the radar antennas on Essen are painted white, while those on Makarov are grey.

In the night of 23 May 2026, the 1st Separate Centre of the Unmanned Systems Forces delivered the fourth confirmed strike against Admiral Essen at Novorossiysk. Several kamikaze drones attacked the frigate in the hull near deck level; the ship attempted to intercept them with its Osa-M surface-to-air missile system. The operation was part of the UAS Forcesʼ 48-hour massed “Birds” raid on Novorossiysk port — alongside strikes on the Sheskharis oil terminal and the Grushova Balka oil storage facility. UAS Forces Commander Robert ʼMagyarʼ Brovdi personally confirmed the strike: “You are doomed to sink, there is nowhere to hide.”[12]

In the night of 12 August 2026, Ukraineʼs Defence Forces conducted what President Volodymyr Zelensky called a “unique operation” against the Novorossiysk naval base — “the last main stronghold of the Russian fleet in the Black Sea”, more than 300 km from the front line. The strike package combined “Palianytsia” jet-powered drones, Neptune missiles, and naval unmanned systems; confirmed hits were recorded on air-defence positions, berths, and port infrastructure.[13]

According to the General Staff of the Armed Forces of Ukraine, four ships sustained damage of varying severity: both 11356R-class frigates — Admiral Essen and Admiral Makarov — the Project 21631 “Buyan-M” missile corvette, and the Project 22160 patrol ship “Vasily Bykov.”[14] Ukraineʼs Defence Intelligence (HUR) specified that the operation was a joint deep-strike effort: operators from HURʼs Active Actions Department and Unmanned Systems Department, the SBU, the Navy, and the State Border Guard Service worked together with the General Staff. Beyond the ships, the strike also hit the “Grushovaya” oil depot, the Sheskharis oil-loading terminal, and a 30N6E radar from an S-300 air-defence battery.[15]

The Telegram channel Exilenova+, which had previously attributed the April 2026 damage to Makarov, published a broader breakdown identifying additional targets not named in the official HUR and General Staff statements: a Project 266M-class minesweeper showing signs of fire, infrastructure of the 4th Submarine Brigade, the Project 22160 patrol ship “Vasily Bykov” fitted with a Tor-M2KM air-defence system, the Project 20360OS “Viktor Cherokov,” the Project 864 support vessel “Priazovye,” and an unidentified cargo ship.

On the night of 8–9 September 2026, Ukraineʼs Defence Forces struck the Novorossiysk naval base once more. Ukraineʼs Defence Intelligence (HUR) reported that operators of its Active Actions Department, working within a joint deep-strike operation, hit the baseʼs infrastructure and the frigate Admiral Essen. A fire broke out on the shipʼs deck superstructure.[23] The same day the Ukrainian Navy named the weapon — a Neptune missile —[24] and a day later specified that it was the extended-range variant, the “Long Neptune.”[26]

According to an analysis by Defense Express, the missile struck the forward part of the superstructure, destroying the bridge and a number of control stations for the shipʼs combat systems and machinery.[29] The first combat launch of a Neptune in this war was aimed at this same frigate — in early April 2022, at sea off the Tendra Spit, where the missile detonated close alongside rather than striking the hull (see above). Eleven days after that launch, two Neptunes sank the cruiser Moskva. Four years on, the extended-range variant of the same missile reached Essen at its pier: the Neptune-D system, firing RK360L missiles with a range of up to 1,000 km and a 260 kg warhead, whose use President Volodymyr Zelensky confirmed in late 2025.

The frigate was not the only target along the Krasnodar Krai coast that night. Unmanned Systems Forces commander Robert “Madyar” Brovdi reported that a Su-33 carrier-based fighter and an Mi-8 helicopter had been destroyed near Anapa, and that two radars — a Kasta-2E2 and a 92N6 from an S-300/S-400 battery — had been hit in the Gelendzhik area. In Novorossiysk itself the fuel oil terminal was burning; it handles roughly 20 million tonnes of petroleum products a year.[25]

Sources differ on which other ships were hit. After analysing additional data, Ukraineʼs General Staff named at least three damaged vessels;[27] the OSINT project Exilenova+, working from satellite imagery, also named three — but not the same ones.[28] Essen is the only ship on both lists.

The General Staff says “at least,” so its list is not exhaustive, while Exilenova+ shows only what is visible from orbit. Hits on Makarov and the Buyan-M have not been officially confirmed; for Makarov, see its section below.

Russia reported no strike on the ships. Novorossiysk mayor Andrey Kravchenko initially attributed the fires to falling debris; Krasnodar Krai governor Veniamin Kondratyev later claimed four people had been killed, among them a child, and 29 injured in the townʼs residential areas.

The third and last frigate of the 11356R series joined the Black Sea Fleet on 27 December 2017 with hull number 499. Before the full-scale invasion Makarov was on routine service at Sevastopol. That changed on 14 April 2022 — the day Moskva sank in the Black Sea.

On 14 April 2022 two Ukrainian Neptune missiles struck the cruiser Moskva — flagship of the Black Sea Fleet. The cruiser sank; among the dead was commanding officer Anton Kuprin — who until 2020 had commanded Makarov itself, and before that Essen. The flagship status passed to Admiral Makarov — by residual default. Among the BSFʼs combat-ready ships it was the most capable and newest vessel with long-range missile armament: 8 Caliber launch cells.

The de facto flagship was at that point actually commanded by Captain 2nd Rank Serhiy Romanenko, who had taken over the ship back in the autumn of 2020 — he is the one who gave the orders for the warʼs first missile strikes.[17] More on him in the biography card below.

At 07:57 on 18 October 2022 Admiral Makarov carried out a precision strike with two sea-launched 3M-14T Caliber cruise missiles against the Prydniprovska thermal power station in Dnipropetrovsk Oblast. The strike caused major damage to the plantʼs buildings, property and equipment, and damaged nearby homes and cars[21]. In April 2026 the SBU filed a notice of suspicion in absentia against Captain 1st rank Volodymyr Kuzmin — commander of the 30th Surface Ships Division of the BSF. Following the strike, the Kremlin promoted Kuzmin to the rank of rear admiral.[7] Then, on 28 August 2026, the SBU and the Prosecutor Generalʼs Office announced suspicions against two more figures in the same strike under Part 1, Art. 438 of Ukraineʼs Criminal Code (war crimes). The investigation divides their roles as follows: Captain 1st rank Oleh Kniazev, chief of staff and first deputy commander of the 30th Surface Ships Division, organised the attack and controlled its execution from the flagship command post; Captain 2nd rank Serhiy Romanenko directed the launch[21]. Three officers of the 30th Division are now under suspicion over this single strike.

At 4:20 a.m. on 29 October 2022, a combined force of 9 aerial and 7 naval unmanned vehicles attacked Black Sea Fleet ships at Sevastopol. This was the first joint operation in history by the Ukrainian Navy and SBU using exclusively unmanned systems. Three naval drones headed for the outer roadstead where Admiral Makarov was anchored. The defence was directed personally by Captain 3rd Rank Denys Kudashkin — from which post is not established in open sources.[18]

The Russian side officially acknowledged damage to the minesweeper Ivan Golubets, but made no statement about a strike on Makarov. OSINT analyst Benjamin Pittet published imagery of Sevastopol Bay showing the frigate under tow in open water.[8]

Planet Labs imagery from 1–3 October 2023, published by MT Anderson, recorded the arrival of Admiral Makarov and Admiral Essen at Novorossiysk port.

In the night of 2 March 2026, Ukraineʼs Security Forces and Defence Forces conducted a combined strike against Novorossiysk. Among the ships struck were Admiral Essen and Admiral Makarov. However, notwithstanding official statements regarding damage to Makarov, corroborating evidence from satellite imagery and other open sources could not be confirmed.

Less than a month later, in the night of 6 April, operators of the 1st Separate Centre of the Unmanned Systems Forces struck the Sheskharis terminal at Novorossiysk. According to Exilenova+ assessment, the frigate was struck at least twice: the first hit — in the area of the UKSK 3S14 vertical launch cells; the second — on port infrastructure nearby. Admiral Makarov attempted to defend itself — Shtil-1 SAM launches were fired from the ship. They did not stop the drones.[9]

In the night of 12 August 2026, Makarov sustained another confirmed hit — this time as part of a large joint deep-strike operation by Ukraineʼs Defence Intelligence (HUR), the SBU, the Navy, and the Defence Forces, alongside Essen, the patrol ship “Vasily Bykov,” and the “Buyan-M” missile corvette. President Zelensky called the operation “unique” given the targetʼs distance — more than 300 km from the front line. A full account of the operation appears in the Admiral Essen section above.[13]

After the 9 September strike, the OSINT project Exilenova+ reported that Makarov had taken a repeat hit to its superstructure.[28] This has not been officially confirmed: Ukraineʼs General Staff does not list Makarov among the ships hit that night,[27] and according to Defense Express the extent of its damage is yet to be established.[29] A full account of the operation appears in the Admiral Essen section.

The lead ship of the series, flagship of the Caspian Flotilla since 2003 — as per official Russian media. Armament: Uran anti-ship system with Kh-35 missiles (two quad-tube KT-184 launchers, 8 missiles total; in the Kh-35U variant range increases to 260 km). Kh-35 missiles are anti-ship missiles with a 145 kg warhead, designed to strike surface targets. They are poorly suited for attacks against land infrastructure, and their range does not allow reaching Ukraine from the Caspian. Tatarstan physically cannot be a source of missile strikes against Ukraine. RIA Novosti in November 2022 incorrectly referred to Tatarstan as a Caliber carrier — a common misconception in Russian media.

The attack was carried out by ultralight A-22 Flying Fox drones that covered approximately 1,500 kilometres. According to HUR MO sources, at least two objects in Kaspiysk port were struck, identified as Tatarstan and Dagestan. ISW noted that imagery did not allow unambiguous identification of damage specifically to the frigates — one vessel of the Gepard class was visible, along with three Buyany, two Buyan-Ms and a Tarantul-class boat.[11] Governor Melikov reported only the “destruction of a UAV by air defences”; Makhachkala airport was suspended. The fact that within a month Tatarstan had departed on an extended voyage calling at Aktau allows the damage to be assessed as non-critical.

As part of a naval strike group, Tatarstan conducted live-fire exercises against surface and air targets. Separately, the destruction of unmanned surface boats using heavy-calibre machine guns was practised — a direct acknowledgement that the flotilla is deliberately preparing for further Ukrainian naval drone strikes.

On the night of 10–11 September 2026 Kaspiysk came under attack. Around 05:30 local residents’ footage of explosions and fire glow over the port began circulating on OSINT channels.[30] That evening the Exilenova+ project published a satellite image and reported that Tatarstan — “the lead ship of the Caspian Flotilla, Project 11661K Gepard, armed with Uran anti-ship missiles and the Osa-MA air defence system” — had “probably” been hit in Kaspiysk.[31] That is the only source for this episode.[34]

The image does not allow the report to be checked. No fire blackening or damaged equipment is visible.[33] Identifying this ship as Tatarstan, or establishing from the image that a strike took place at all, is difficult.

President Volodymyr Zelensky listed the targets of that night’s long-range strikes the same day — Dagestan among them, alongside Udmurtia and the Tula, Nizhny Novgorod, Perm and Samara regions.[32] Russia’s Defence Ministry claimed 777 Ukrainian drones had been launched overnight and also named Dagestan among the regions hit.[33] No one mentioned the ship. Neither General Staff report, for 10 or for 11 September, mentions the Caspian.

Laid down in 1991, launched on 1 April 2011. 17 September 2012 — a successful test launch of the 3M14 long-range cruise missile from Dagestan: the first such launch from a surface ship in Russian Navy history.

ArmamentWhat Makes Dagestan Unique

Dagestan is the first Russian Navy ship equipped with the UKSK 3S14 vertical launch system for 8 missiles. The UKSK can employ:

• 3M14 — long-range cruise missile for strikes against land targets. These are the missiles used against Ukraine.
• 3M54 — anti-ship missile with a supersonic terminal stage.
• 91R — anti-submarine rocket-torpedo.

Putinʼs birthday. That night, Dagestan and three Buyan-Ms fired 26 Caliber-NK cruise missiles at 11 ISIS targets in Syria. The missiles flew over 1,500 km above Iran and Iraq. This was the first strike in Russian Navy history against a real adversary using surface ship-fired long-range cruise missiles.

Following the terrorist attack against the Russian airliner over Sinai, the same strike group — Dagestan and three Buyan-Ms — fired 18 Caliber-NK missiles at 7 targets in the provinces of Raqqa, Idlib, and Aleppo.

British military intelligence and Ukrainian Navy spokesman Dmytro Pletenchuk confirmed the use of the Caspian Flotilla for strikes against Ukraine in 2022 and sporadically in 2023–2024. Defense Express assessed the most likely period of active launches as April–May 2024. The first documented video confirmation of Calibers flying over the Caspian appeared on 8 July 2024 — the day of the strike on Kyivʼs Okhmatdyt hospital; on the same day a missile that went off course fell and exploded in Kalmykia. Whether Dagestan specifically launched has not been publicly confirmed, but it is the only frigate in the flotilla technically capable of doing so.

The first and only documented Ukrainian UAV attack in which Dagestan figured among the probable targets. OSINT researcher MT_Anderson published imagery showing the dispersal of the Caspian Flotilla — “the surviving ships were scattered across the sea.”