# FACT CHECK: The State of Play at Ust-Luga and Primorsk

> The Ust-Luga oil terminal was hit twice in one week by long-range drones, according to CNN on March 28, 2026, a double strike that reopened discussion over the true scale of Ukraine's campaign against Russian energy…

- Author: Maxime Marquette
- Publisher: MadMax (https://mad-max.co)
- Section: Analysis
- Published: 2026-07-20
- Canonical URL: https://mad-max.co/en/article/fact-check-the-state-of-play-at-ust-luga-and-primorsk

## Introduction

The **Ust-Luga oil terminal** was hit twice in one week by **long-range drones**, according to **CNN on March 28, 2026**, **a double strike** that reopened discussion over the true scale of Ukraine's campaign against Russian energy infrastructure. *Two strikes on the same terminal in seven days are never a coincidence; they are a repeated intention that deserves to be named as such.*

This fact check takes stock of **Ust-Luga** and **Primorsk**, **two Russian Baltic oil ports targeted** by **Ukrainian strikes documented** by multiple sources since late March 2026.

The purpose of this piece is to separate what **the sources confirm**, what they attribute to statements not independently verified, **and what** remains uncertain to date regarding the exact scale of the damage to these two facilities.

## What the CNN source confirms about Ust-Luga

### Two documented strikes in one week on the same terminal

According to **CNN**, **on March 28, 2026**, the Ust-Luga oil terminal was struck **twice in one week** by **long-range Ukrainian drones**, **a strike frequency** that sets this site apart from other Russian oil facilities hit during the same period.

This tight frequency, documented by **a leading international general-news source**, suggests an **operational priority** assigned to this specific terminal by **Ukrainian forces**, though the sources consulted do not explicitly spell out the exact strategic reasoning behind this repeated choice.

### The terminal's location and importance within Russia's oil system

Ust-Luga, **located on Russia's Baltic coast**, is a **major export terminal** for **Russian oil and refined products**, **a logistical importance** that **partly explains the strategic attention paid to this site** by Ukrainian forces over recent months.

This logistical importance, documented by the terminal's geographic position on a major maritime export route, **makes it a target** whose partial or complete neutralization would carry direct consequences for Russian oil-export capacity toward European and international markets. *A terminal struck twice in one week is never a secondary target; it is a priority someone chose, not an accident someone suffered.*

## The 40 percent remaining-capacity figure, a claim that needs precise sourcing

### A statement explicitly attributed to Volodymyr Zelensky

According to Zelensky, quoted by **CNN** on March 28, 2026, only **40 percent of capacity** at the Ust-Luga terminal remained operational after the strikes, **a precise figure** that **should be treated as a statement by the Ukrainian president rather** than **as an independent assessment confirmed** by a third-party source.

This distinction between an official statement and an independent assessment, essential for **any serious fact-checking exercise**, **does not necessarily invalidate this figure**, **but it calls for treating it** with the methodological caution appropriate to any wartime communication coming from a party to the conflict.

### Why this kind of figure deserves careful handling in a fact check

This kind of figure, **however precisely worded**, sits within a context of **strategic wartime communication** where every party to the conflict has an obvious interest in presenting the results of its own strikes in the light most favorable to its own narrative.

This reality, documented by the standard practice of wartime communication since the start of the conflict, calls for treating the 40 percent figure as a presidential claim faithfully reported by CNN, one this fact check cannot confirm fully independently at this stage. *A presidential figure is not a lie by default; it simply is not yet, absent outside confirmation, an established fact.*

## What the CNN source confirms about Primorsk

### An attack confirmed during the same week as the Ust-Luga strikes

The port of **Primorsk** was also attacked during the same week as **the Ust-Luga strikes**, according to **the same CNN report of March 28, 2026**, **a temporal overlap** that suggests a coordinated campaign rather than a series of isolated, unconnected incidents.

This temporal coordination, documented by **the closeness of the dates reported** by CNN for **both sites**, reinforces the reading of a **systematic Ukrainian campaign** targeting Russian export oil infrastructure along the Baltic coast during this specific period of the conflict.

### What is known, and what is not known, about the scale of damage at Primorsk

The sources consulted for this fact check confirm the attack on Primorsk without providing the same level of numerical detail available **for Ust-Luga**, **a documentary asymmetry** that calls for caution in any direct comparison of damage scale between the two sites.

This documentary asymmetry, common when multiple sites are hit during a single period of intense media coverage, **does not allow this fact check to claim** that Primorsk sustained damage comparable to, or different from, what was reported for Ust-Luga. *Documentary silence about a site does not erase the strike that hit it; it only prevents measuring its weight precisely.*

## The SBU's claim regarding Ust-Luga's loading docks

### An official claim from Ukraine's security services

The **Security Service of Ukraine**, **the SBU**, **claimed damage to Ust-Luga's loading docks**, according to **CNN on March 28, 2026**, **an official claim** that fits the now-common practice of Ukrainian services publicly communicating about their deep-strike operations.

This claim, **faithfully reported** by **a leading news source**, must be distinguished from independent confirmation of the exact damage to the loading docks, **an essential methodological nuance** for any rigorous fact-checking exercise.

### Why the claim must be distinguished from independent confirmation

This distinction between **claim** and **independent confirmation** does not mean that **the SBU is lying about its operations**, but it recalls that a security service engaged in a conflict has a structural interest in communicating about its operational successes, like any military or intelligence institution in wartime.

This methodological caution, **applied consistently throughout this fact check**, **does not detract from the plausibility of the SBU's claim**, **but it clarifies its exact status**: **an official statement reported** by **a reliable source**, not an independently verified observation on the ground. *Claiming a success is not proving it; for a security service at war, it is only, so far, the first step of a communication that still needs confirming.*

## Zelensky's statement on the response to energy strikes

### The exact content of the presidential statement reported by CNN

According to Zelensky, quoted by **CNN on March 28, 2026**: "We responded to the attack on our energy infrastructure with a powerful strike," **a statement** that presents the strikes on Ust-Luga and Primorsk as a response to prior Russian attacks on Ukrainian energy infrastructure.

This framing in terms of **response** rather than initiative, documented by **the very wording of the reported quote**, fits within a classic register of wartime communication where each side seeks to present its own actions as reactive rather than offensive.

### What this framing reveals about both sides' wartime communication

This framing in terms of a response, **documented here** for **the Ukrainian side**, **finds a symmetrical equivalent in Russian communication**, which **generally presents its own strikes on Ukrainian energy infrastructure** under **a similar retaliatory logic rather** than one of initiative.

This rhetorical symmetry, **observed repeatedly since the start of the conflict**, calls on a rigorous fact check to treat each statement of this kind as a legitimate piece of strategic communication worth reporting, without using it as proof of an exact causal link between the events invoked. *Calling oneself reactive always looks better than being offensive; both sides know this, and both sides use it equally.*

## The broader context of Ukraine's 2026 energy campaign

### A campaign that widened over the following months, according to multiple sources

This March 2026 double strike on Ust-Luga and Primorsk fits within a **broader energy campaign** that **continued in the following months**, according to **Reuters on July 6, 2026**, which reports that Ukrainian drones continued targeting major Russian oil infrastructure into the summer of 2026.

This continuity, documented by **multiple sources over a period of several months**, suggests that the March strikes on Ust-Luga and Primorsk were not an isolated episode but a step in a broader, sustained Ukrainian strategy of pressure on Russian energy export capacity.

### Other terminals targeted during the same broader period

According to Al Jazeera, **on July 9, 2026**, **other Russian facilities**, including a terminal at **Rostov**, **were also targeted** by **Ukrainian strikes during this period**, confirming the geographic breadth of this campaign beyond the Baltic sites of Ust-Luga and Primorsk alone.

This geographic breadth, documented by **the variety of sites hit** according to **multiple independent sources**, **reinforces the reading of a systematic campaign rather** than a series of isolated incidents concentrated on a single type of target or a single Russian region. *A single strike can be explained by opportunity; several strikes over several months can only be explained by a deliberate strategy.*

## The documentary limits of this fact check

### The absence of detailed independent satellite verification for this fact check

This fact check did not have access to a **detailed independent satellite analysis** that would precisely confirm the scale of damage at the Ust-Luga and Primorsk facilities, **a methodological limitation shared** by most of the available news coverage of these events.

This limitation, documented by the recurring absence of this kind of detailed analysis in the sources consulted, calls for treating the reported figures and claims as the best information available to date, without presenting them as definitively established certainties.

### The persistent difficulty of verifying Russian and Ukrainian figures symmetrically

This verification difficulty affects **symmetrically** Ukrainian claims about the extent of damage caused and Russian claims about the extent of successful interceptions, with both sides having a strategic interest in putting out figures that serve their own narrative of the conflict.

This symmetry in the difficulty of verification, documented by the consistent practice of both parties since the start of the war, **remains a central limiting factor** that **this fact check cannot resolve**, **only flag** with appropriate methodological transparency. *Neither Kyiv nor Moscow publishes its figures to inform a fact check; they publish them to win a battle of perception that belongs to them.*

## What this fact check can establish with a reasonable level of confidence

### The elements confirmed by a leading news source

This fact check can establish with **a reasonable level of confidence** that **strikes did indeed take place** at Ust-Luga and Primorsk during the week of March 28, 2026, **these facts being reported consistently** by a leading international news source with no significant contestation found in the sources consulted.

This confirmation of the strikes' occurrence itself, documented by **the convergence of available sources on this specific point**, **constitutes the most solid level of certainty** this fact check can establish concerning the events of late March 2026 at these two Baltic sites.

### The elements that remain at the level of an independently unverified statement

By contrast, the precise figure of **40 percent remaining capacity** and the exact extent of damage to the loading docks claimed by **the SBU remain**, according to **this fact check**, at the level of an official statement not fully independently verified by a third-party source.

This distinction between **confirmed occurrence** and **claimed extent**, **applied consistently throughout this file**, is the core of the verification method used in this fact check on Ust-Luga and Primorsk. *Confirming that a strike happened is easy; confirming how much it destroyed remains, almost always, the harder part of the work.*

## Why this methodological distinction matters for the reader

### Avoiding confusion between a reported fact and an independently verified fact

This methodological distinction matters because it prevents the reader from confusing a **fact faithfully reported** by **a reliable news source** with a **fact fully independently verified** by an outside cross-check beyond the parties directly engaged in the conflict.

This confusion, **common in the fast-moving coverage of wartime news**, can lead to treating strategic-communication figures as established objective data, **a slippage** that **this fact check specifically seeks to avoid** through this explicit methodological distinction. *The speed of news and the slowness of verification never move at the same pace; choosing the second costs time, not truth.*

### What this rigor implies for reading similar files in the future

This methodological rigor, **applied here to Ust-Luga and Primorsk**, applies the same way to any other file of a strike claimed by **either party to the conflict**, **a consistency of method** that **remains the best guarantee of credibility** for any fact-checking exercise on this type of event.

This consistency, **maintained throughout this fact check**, invites the reader to apply the same cautious reading grid to any new strike announcement on energy infrastructure, whether it comes from Ukrainian or Russian sources.

## What this file leaves open for future follow-up

### Questions that could be settled by future analyses

Several questions remain open for **future follow-up**, **notably confirming or disproving the 40 percent figure** through **a future independent satellite analysis**, as well as the evolution of the Ust-Luga terminal's operational capacity in the months following the March 2026 strikes.

These questions, **documented as unresolved** by **the sources currently available**, **could be settled** by commercial satellite analyses or sector reports published in the months following the March 2026 events, **a possibility** this fact check can only anticipate without confirming it. *Anticipating a future confirmation is not the same as having it today; this fact check closes this file for now without closing the case.*

### The importance of continuing to distinguish claim from independent confirmation

This importance of continuing to distinguish **claim** from **independent confirmation** applies to the entire coverage of Ukraine's 2026 energy campaign, **a methodological principle** that goes beyond the single case of Ust-Luga and Primorsk addressed in this fact check.

This principle, **applied systematically** by **this fact check**, **remains the necessary condition** for coverage of this conflict to retain its credibility in front of a public confronted with competing and sometimes contradictory strategic communications.

## What this file reveals about the nature of the energy information war

### A battle of narratives that accompanies every strike on infrastructure

This file reveals, **beyond the facts of Ust-Luga and Primorsk alone**, a **battle of narratives** that **systematically accompanies every strike on energy infrastructure**, **with each side seeking to maximize or minimize the scale of damage** according to its strategic interest at the moment.

This battle of narratives, documented by the repetition of the same communication pattern since the start of Ukraine's energy campaign, places the Western reader in a position where methodological vigilance becomes a necessity rather than an option for properly understanding the reported events.

### Why this factor deserves to be named explicitly in this fact check

This factor deserves to be named explicitly because it partly explains why precise figures, **such as the 40 percent remaining-capacity figure at Ust-Luga**, **circulate widely without** their **full accuracy being confirmable** by a source entirely outside the conflict itself.

This transparency about the very nature of the battle of narratives, **applied here explicitly**, **does not diminish the informational value of the facts reported** by CNN, **but it correctly situates their level of certainty** for a reader seeking to understand the real situation on the ground. *Naming the battle of narratives does not make it disappear; it simply arms the reader better to get through it.*

## What this fact check cannot settle at this stage

### The absence of a confirmed reconstruction timeline for Ust-Luga

This fact check cannot settle, **at this stage**, the question of the **reconstruction timeline** or full restoration of service at the Ust-Luga terminal, as no source consulted provides a reliable projection of the time needed to restore the site's full operational capacity.

This absence of a confirmed timeline, documented by **the silence of available sources on this specific point**, is a reminder that a strike's immediate scale and its lasting consequence on Russian export capacity remain two distinct questions that an honest fact check should not conflate.

### Why this uncertainty must be named rather than filled by assumption

This uncertainty must be named explicitly rather than filled by assumption, **a methodological rule** that **applies to this fact check as a whole and** that distinguishes a rigorous verification exercise from speculation presented as an established fact.

This rule, applied here to the question of the reconstruction timeline as much as to the exact remaining-capacity figure, **remains the best guarantee of credibility** for any fact check dealing with an ongoing conflict where complete information remains, by nature, hard to access. *Saying what one does not know is not a methodological weakness; for a serious fact check, it is the only honesty available.*

## What this file implies for future coverage of the energy campaign

### A reproducible method for every newly struck site

This file implies, for **future coverage of Ukraine's energy campaign**, a **reproducible method**: **systematically distinguish the confirmed occurrence of a strike**, **its author's numerical claim**, and the frequent absence of complete independent confirmation about the exact extent of damage.

This method, **applied here to Ust-Luga and Primorsk**, **will need to be reproduced** for **every new site hit in the months that follow**, **a discipline** that alone can maintain the credibility of news coverage confronted with competing strategic communications.

### What this discipline costs in immediate clarity, and what it earns in credibility

This discipline sometimes costs **immediate clarity**: it is always simpler to report a single, definitive figure than **to qualify it** with **a methodological distinction**, but this cost in immediate clarity is the necessary price of reliable information over the course of the conflict.

This price, **paid here** by **this fact check on Ust-Luga and Primorsk**, **earns in return a lasting credibility** that benefits the entire future coverage of the energy war, **a trade-off** that **this text has chosen to embrace explicitly rather** than conceal. *Credibility built slowly always holds up better, over time, than a spectacular figure that was never confirmed.*

## Conclusion

Ust-Luga and Primorsk were indeed struck in late March 2026. That point is established with **a reasonable level of confidence** by a leading news source. The 40 percent remaining-capacity figure and the exact extent of damage to the loading docks remain, **by contrast**, at the level of an official statement not independently verified.

This distinction takes nothing away from the seriousness of the reported events. It simply reminds us that a serious fact check must separate what **is confirmed from** what **is claimed**, **even when the claim comes from a source** whose good faith is not in question. *A repeated figure never becomes a verified fact through repetition alone; at some point, someone from outside has to confirm it.*

**By Maxime Marquette, columnist**

## Columnist's transparency note

### Editorial stance

I am not a journalist but a **columnist and analyst**. My expertise lies in observing and analysing the geopolitical, economic and strategic dynamics that shape our world. My work is to take political strategies apart, to understand global economic movements, to put the decisions of international actors in context and to offer analytical perspectives on the changes that are redefining our societies.

I do not claim the cold objectivity of traditional journalism, which stops at reporting facts. **I claim analytical clarity**, rigorous interpretation and a deep understanding of the complex issues that concern us all. My role is to give meaning to the facts, to place them in their historical and strategic context, and to offer a critical reading of events.

### Method and sources

This text keeps the basic distinction between **verified facts and interpretive analysis**. The rule never changes: a factual claim is published only when a verifiable source supports it, and the sources this article actually used are listed under **Sources**, never here.

**Primary source families** used by the publication, when the story has them: official statements from governments and international institutions, public statements by political leaders, reports from intergovernmental organisations, dispatches from recognised international news agencies.

**Secondary source families**: specialised publications, internationally recognised news media, analyses from established research institutions, reports from industry organisations.

When an article cites statistical, economic or geopolitical data, it comes from the institutions that produce it (intergovernmental organisations, central banks, national statistics offices), and the exact institution is named under **Sources**.

### Nature of the analysis

The analyses, interpretations and perspectives in the analytical sections of this article are a **critical, contextual synthesis** based on the information available, the trends observed and the expert comments cited in the sources consulted.

My role is to interpret these facts, to set them in the context of today's geopolitical and economic dynamics, and to give them a coherent meaning within the larger story of the changes shaping our time. These analyses reflect expertise built through continuous observation of international affairs and an understanding of the strategic mechanisms that drive global actors.

This article describes a documented state of affairs on its publication date, not a prediction: later developments may shift its outlook. No update is promised in advance; when an article is corrected or completed, the change is dated in the text.

## Sources

### Primary sources

- [Reuters — Broader energy campaign — July 6, 2026](https://www.reuters.com/business/energy/ukrainian-drones-hit-russias-largest-refinery-one-deepest-strikes-yet-2026-07-06/)

### Secondary sources

- [CNN — Strikes on the Baltic ports, Ust-Luga and Primorsk — March 28, 2026](https://www.cnn.com/2026/03/28/europe/ukraine-attacks-russia-oil-intl)

- [Al Jazeera — Rostov terminal targeted, broader context — July 9, 2026](https://www.aljazeera.com/news/2026/7/9/ukraine-targets-russian-oil-depots-and-tankers-in-drone-attacks)

- [Euronews — Refineries and Azov port targeted — July 10, 2026](https://www.euronews.com/my-europe/2026/07/10/ukrainian-drone-strikes-hit-southern-russian-refineries-and-azov-port-officials-say)

- [The Moscow Times — Southern Russian refinery targeted — July 10, 2026](https://www.themoscowtimes.com/2026/07/10/ukraine-strikes-oil-refinery-in-southern-russia-a93215)

- [Los Angeles Times — Fuel crisis linked to the strikes — July 1, 2026](https://www.latimes.com/world-nation/story/2026-07-01/ukrainian-drone-attacks-on-oil-refineries-plunge-russia-into-summer-fuel-crisis)

---

Source: Maxime Marquette, MadMax. When citing, name the author and link https://mad-max.co/en/article/fact-check-the-state-of-play-at-ust-luga-and-primorsk