Battle of Enerhodar
2022 siege
On 4 March 2022, a military engagement took place between the Russian Armed Forces and the Armed Forces of Ukraine over the city of Enerhodar in Zaporizhzhia Oblast, on the southern front of the Russian invasion of Ukraine. Enerhodar is the location of the Zaporizhzhia Nuclear Power Plant, which generates nearly half of the country's electricity derived from nuclear power and more than a fifth of total electricity generated in Ukraine, as well as a nearby thermal power station.
After attacking protesting civilians on 3 March, Russian forces engaged Ukrainian forces at the nuclear power plant and took control of it, seizing Enerhodar the same day.
Background
On 28 February, the Russian Ministry of Defense announced that its forces had captured the city of Enerhodar and the Zaporizhzhia Nuclear Power Plant, though this was denied by the city's mayor, Dmytro Orlov and Energoatom, the Ukrainian state enterprise which operates the plant. Local citizens later barricaded the road to the plant and the entrance to the city, forcing the Russian forces to turn back.
On 1 March, Ukrainian officials stated that Russian forces had surrounded the city, with a Russian convoy heading into Enerhodar around 2:00 pm. According to Orlov, the city had difficulties obtaining food. In the evening, a protest by local residents blocked Russian forces from entering the city.
In the morning of 2 March, Orlov stated that Russian troops were again approaching the city. Protestors again blocked the roads; protestors carried Ukrainian flags and used garbage trucks as part of the blockade.
“Battle of Enerhodar” enters the record as 2022 siege. Crown Archives preserves that source wording while asking what Battle, Enerhodar and siege can confirm, complicate or overturn.
Why this record matters
“Battle of Enerhodar” is worth following because a concise public description often conceals a longer documentary argument. Here, Battle, Enerhodar and siege provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Aug 21, 2026. The linked authority identifier is Q111037776. Authority coordinates are 47.499, 34.656. None of the 1 selected statements returned an explicit reference. The first chronological checks are 2022.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Battle of Enerhodar”, its source revision and the description used here.
- Expand the search: follow Battle of Enerhodar primary sources, Battle of Enerhodar archive and Battle research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Battle of Enerhodar”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Battle of Enerhodar” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.