Battle Analysis
In depth | Defending the Pokrovsk Axis — how long can drones hold ground the supply line cannot reach?
· 2024-12-07 – 2025-12-10
Overview
Part 1: Defending the Pokrovsk Axis (December 2024 – December 2025) told the year as a story; this piece looks at the battalion-level decisions inside it. A defence built on drones instead of infantry holds ground only while supplies and people can still reach it. Ukrainian drones stalled the Russian advance from late 2024 into summer 2025 [1][2]; Russia then attacked what fed the defence: roads, drone crews and command posts [2][3]. Below, terrain and weather are re-read through data, and the scenario's phases are taken in turn.
Photo 1. A yard in Pokrovsk, 8 January 2025. The town was a supply hub with civilians still living in it — Photo: Donetsk Regional Military Administration, CC BY 4.0, via Wikimedia Commons
Strategic and operational context
After frontal assaults failed in spring 2024, Russian forces tried to envelop Pokrovsk [2]. RUSI put the Russian grouping in Donetsk and Luhansk at about 230,000 troops, aiming first to isolate and reduce the town [16, p. 4]. For Ukraine the town was the logistics hub of the northern Donbas [14][18], and holding it bought time for the "fortress belt" from Kostiantynivka to Sloviansk [3]. The odds were poor where it mattered: RUSI found that the force ratio between combat units in a given sector ran from 1:2 to 1:6 [16, p. 5].
Terrain and weather in detail (OAKOC)
Figure 1. The south-western approaches and the closing corridor (sketch; battalion layout is the scenario composite; to 10 December 2025 only). Places from OSM [27], elevations from Open-Meteo [26] — Own work, after sources 1–15 and 19
Observation. A gentle plateau: central Pokrovsk about 193 m, Shevchenko 184 m, Pishchane 146 m [26]. View came from the air: RUSI describes near-total transparency within 3 km of the line, thinning out to 15 km [16, p. 15].
Avenues of approach. From Selydove, 17 km south-south-east, Russian forces swung west toward Shevchenko and Pishchane, both 7 km out [13]; Kotlyne lies 10 km west (from OSM coordinates [27]). In summer a second approach opened along the H-32 toward Rodynske, 9 km north [14].
Key terrain. The roads west to Pavlohrad, north to Dobropillia and north-east through Rodynske. Control of movement on them decided whether Pokrovsk worked as a hub [2][8].
Obstacles. Mine works, slag heaps and apartment blocks, and the Vovcha bridges, two of three claimed destroyed by Russia in early November [3].
Cover and concealment. Windbreak tree lines cut the fields into a grid; Russian teams of two or three, sometimes single soldiers, moved along them [12]. Weather set how much of the fields could be watched. Using ERA5 reanalysis as a proxy (Figure 2), only 3 of 17 days in late October had more than 6 hours at 95% relative humidity or more, the conditions of mist and fog; from 5 November to 2 December, 21 of 28 days had at least 8 [25]. Milbloggers claimed advances "in heavy fog" around 12 November [8], and wet weather hampered light FPVs [3]. Daylight fell below 8½ hours by December [24].
Organisation and command relationships
Company-level dispositions are not public; the battalion rows follow the scenario and RUSI's description of typical positions.
| Side |
Echelon |
Unit / element |
Role and notes |
Source |
| Ukraine |
Operational |
Khortytsia (later Dnipro) group of forces |
Sector command |
[6][13] |
| Ukraine |
Corps |
7th Rapid Response Corps, Air Assault Forces |
Held the town; announced the December withdrawal |
[9][11][12] |
| Ukraine |
Brigade |
68th Jaeger Brigade |
Southern edge of town; short of vehicles by October |
[12] |
| Ukraine |
Regiment |
425th Assault Regiment "Skelia" |
Cleared a late-July breach in the south-west |
[12] |
| Ukraine |
Brigade |
38th Separate Marine Brigade |
Myrnohrad; "almost surrounded" on 4 December |
[9] |
| Ukraine |
Special |
Military-intelligence special forces |
Helicopter insertion c. 31 October (at least 10 seen) |
[3][7] |
| Ukraine |
Battalion |
Infantry battalion (scenario) |
Under-strength companies, one platoon reserve (est.) |
scenario |
| Ukraine |
Company |
Rifle companies |
Fireteams of 2–3, c. 50 m apart; company c. 3 km deep, battalion c. 7 km (typical) |
[16, p. 9] |
| Ukraine |
Drones |
Battalion drone company, brigade drone battalion |
Watch and strike the fields |
[16, p. 10] |
| Russia |
Army |
8th Combined Arms Army (part) |
Elements moved toward Kostiantynivka, early 2025 |
[1] |
| Russia |
Army / division |
51st Combined Arms Army; 150th Motor Rifle Division |
Around the August penetration |
[5] |
| Russia |
Brigade |
5th, 110th, 132nd Motor Rifle Brigades |
Inside the Dobropillia penetration |
[5] |
| Russia |
Division |
76th Air Assault Division |
Assault through Pokrovsk in December (Ukrainian claim) |
[10] |
| Russia |
Specialist |
Rubikon Center for Advanced Unmanned Technologies |
Hunts logistics and drone crews 10–20 km deep |
[2][19] |
| Russia |
Special |
Spetsnaz |
First, infiltration phase |
[2] |
The telling difference is depth: the battalion defended about 7 km with sensors and fireteams [16, p. 9]; Rubikon worked 10–20 km into the rear against drone crews and logistics [19].
Month-by-month account
7–16 December 2024: the swing west
On 16 December the group spokesman said Russian units near Pishchane had been pushed back to the tree line and that the attackers were bypassing the town from the flanks [13].
January – mid-February 2025: the slowdown
On 15 February ISW judged the advance south and south-west had "significantly slowed", citing degraded units and Ukrainian drones that a Russian milblogger said made rotation and resupply "impossible" [1]. Ukrainian counterattacks near Kotlyne and Pishchane threatened the salient, and 8th Army elements reportedly moved toward Kostiantynivka [1]. CSIS later measured the advance from Avdiivka through April 2025 at about 60 km, or 135 m a day [17].
July: the roads become the front
ISW dates Russian air interdiction effects to July [2][8]: longer-range FPVs and "waiter" drones parked beside the roads [2]. Fibre-optic drones could not be jammed, and Russian drones covered every road into town [3][12]. A late-July breach was cleared by the 425th Regiment [12].
August: the north-eastern wedge
UK Defence Intelligence reported on 2 August an advance west along the H-32 toward Rodynske, on the main northern supply route [14]. On 11 August small groups were reported 9–15 km deep toward Dobropillia; the sector command said infiltration was not control [6]. ISW called it not yet an operational breakthrough [4], and by 18 August counterattacks had retaken villages at the base of the wedge [5].
September – October: creep into the town
Around 20 October the 7th Corps acknowledged a penetration to the railway [12]. On 29 October Ukrainian commanders put Russian strength in town at about 200; a drone unit claimed up to 300 a day were entering in threes [3].
31 October – 12 November: insertion and the hub
Around 31 October special forces were landed by helicopter; Russia claimed all 11 were eliminated, Ukraine denied it, and the footage was unverified [7]. Ukraine's commander-in-chief said there was no encirclement [7]. On 4 November ISW assessed that Russia had denied Ukraine the use of Pokrovsk as a logistics hub [2], and on 12 November confirmed Russian control of about 46% of Pokrovsk and 10% of Myrnohrad [8].
28 November – 10 December: the corridor
The corps commander described supply by ground robot, heavy drones and netted corridors [11]. On 3 December UK Defence Intelligence called Russia's claim of full control "almost certainly inaccurate" [15]. On 8 December the 7th Corps announced an "organised manoeuvre" from Lysivka and Sukhyi Yar to save lives, improve logistics and level the line [9]; on 10 December ISW judged both towns would very likely fall, at greater cost [10].
Decision points in depth
Headings follow the training scenario; p3x, p5x and p7x are what-if phases (Figure 2).
Figure 2. Decision points and the autumn weather. Hours at 95% relative humidity or more are a proxy for mist and fog, not an observation [25]; decision dates follow the training scenario — Own work
p1 A thin line (10 December 2024)
Knew: worn Russian units dependent on a few tracks (B2); drones catch most teams by day, not in fog (A2); a rumoured armoured attack (D5). Options: continuous trench line, strongpoints plus drones, counterattack south, or fall back. Decision: strongpoints and drones [1]; RUSI notes sections covering 70–200 m and engagement 10–15 km out [16, p. 9]. Otherwise: a thin continuous line offers what the Russian method exploits, positions mapped and then struck [16, p. 8].
p2 Kotlyne and Pishchane (early February 2025)
Knew: a squad at most outside Pishchane (B2); Russian relief could not cross the fields (B3). Options: isolate by drone, a small local counterattack, a battalion push, or rotation. Decision: local counterattacks [1], as FM 3-90 expects of lower-echelon reserves [20, para 9-10]. Otherwise: a battalion push would have given up the advantage that was stopping the Russians.
p3 The last few kilometres (July 2025)
Knew: a specialist drone unit hunting vehicles (B2); a few ground robots (A2); a rumour about 0400 (E5). Options: night truck runs, an armoured convoy with jammers, small loads by robot and on foot, or shorter routes. Decision: robots, heavy drones, buggies and netted corridors [11], though RUSI warned UGVs were unreliable [16, p. 17]. Otherwise: a convoy is the target the interdiction was built to find, and jammers do not stop fibre-optic drones [3].
p3x Supply cut (what-if)
Situation: road cut, one day of water forward. Recommended: small loads along an unwatched tree-line path and rationing. Ukrainian brigades took about half their casualties in the rear in such movement [16, p. 17].
p4 The wedge to the north-east (12 August 2025)
Knew: small groups, no follow-on (B2); corps reserves coming (A2); a social-media map showing Dobropillia lost (F6). Options: keep the reserve, release a platoon and some drone crews, send the whole drone company, or a spoiling attack. Decision: reserves cut the wedge at its base [5]; extending flanks against envelopment is a listed reserve task [20, para 9-11]. Otherwise: the whole drone company would have left the battalion's fields blind.
p5 Infiltrators in the rear (late October 2025)
Knew: teams near the supply route and launch sites (B3); a claim of 200 in town (C4); special forces promised (C2). Options: leave it to each position, harden crews and the command post and hunt in the rear, counterattack forward, or withdraw. Decision: rear hunting and protection of drone crews and command posts [2][3], the very targets FM 3-90 lists for infiltrators [20, para 2-83]. Otherwise: a forward counterattack would have hit empty fields.
p5x The command post is exposed (what-if)
Situation: contact across the street at 0300, jamming, half the drone screens dark. Recommended: move before first light to pre-planned underground alternates with satellite terminals. FM 3-90 asks for decoys and dummy positions for command posts [20, para 8-113].
Photo 2. A fibre-optic FPV drone during Ukrainian testing, February 2025. The spool pays out the cable that makes it immune to jamming; RUSI gives such drones about 10 km of range [16, p. 10]. Not taken at Pokrovsk — Photo: ArmyInform, CC BY 4.0, via Wikimedia Commons
p6 Special forces arrive (early November 2025)
Knew: special forces clearing factories to the north-west (B2); a Russian claim that all had died (F6); three crossing points used by Russian teams (B3). Options: drones over the special forces while holding the corridor, a rifle company into town, a liaison officer, or all fires on the crossings. Decision: composite; the reported aim was to reopen logistics lines [7]. Otherwise: a company in town would have left the corridor open.
p7 Avoid encirclement (early December 2025)
Knew: two positions supplied once in three days (A2); two western tree lines lightly watched (B3); a rumour of full encirclement (E5). Options: staged night withdrawal, hold everything, attack the northern pincer, or one vehicle move. Decision: the corps left the Lysivka–Sukhyi Yar area [9], to preserve the force and shorten supply lines as FM 3-90 allows [20, para 11-1]. Otherwise: one vehicle move was the convoy the drones had hunted since July.
p7x The closing corridor (what-if)
Situation: a corridor a few hundred metres wide, fog returning. Recommended: small groups along tree lines, the wounded on robots. Withdrawals should move when the enemy cannot observe [20, para 11-73]; in December fog was the only such condition left.
Figure 3. Manoeuvre by phase (18-second loop; reduced motion shows only the final situation). Positions sketched and partly estimated — Own work
Doctrine re-read
Strong points (FM 3-90, paras A-68, A-69). Doctrine means a heavily fortified, all-round company or battalion position [20]. Pokrovsk's were fireteams spread over hundreds of metres [16, p. 9], observation posts tied to a fire system; when fog blinded the system, they were too small to stand alone.
The reserve (ch. 9, paras 9-10 to 9-12). Plans should succeed without the reserve, and every echelon down to battalion keeps one [20]. The battalion used it as written at p2 and lent part of it upward at p4; at p5 little was left to hunt infiltrators.
Infiltration (ch. 2, paras 2-82 to 2-84). The manual treats infiltration as a supporting manoeuvre [20]; here a three-phase method (special forces, assault units, small groups) [2] made it the main effort, paid for in heavy losses.
Withdrawal (ch. 11, paras 11-1, 11-71 to 11-82). A retrograde needs higher approval [20][21], and commanders prefer to withdraw before pressure builds [20, para 11-82]. A Modern War Institute essay notes FM 3-0 gives retrograde one paragraph [22]; at Pokrovsk, planning the withdrawal was part of holding.
Source criticism
Rate of advance. CSIS gave about 60 km at 135 m a day for February 2024–April 2025 [17], then just under 50 km at 70 m a day for February 2024–early January 2026 [18]; Al Jazeera gives 39 km from Avdiivka [3]. A longer period cannot have a shorter distance, so the measures differ. CSIS's later brief states its method, the straight-line shift of the front [18]; the 39 km is town-to-town. Quote the later figure, with its method.
Infiltration. About 200 Russians in town on 29 October (Ukrainian commanders), up to 300 a day (a drone unit) [3], nearly 100 three-person teams a day (relayed by ISW) [2]. The flow figures agree but are unverifiable claims by one side, and they do not fit a stock of 200.
Control. Milbloggers claimed "firm control" in mid-November; ISW confirmed 46% [8]. A Russian claim of full control on 2 December was rejected by UK Defence Intelligence [15]. ISW counts only geolocated evidence: it lags but does not invent.
The Dobropillia wedge. DeepState mapped 9–15 km; the sector command denied any loss of control [6]. One measured where groups were seen, the other who held ground; ISW's "penetration, not breakthrough" reconciles them [4].
The insertion. Russia claimed 11 eliminated, Reuters saw at least 10 on video, Ukraine denied the claim, and date and place are unverified [7].
Lessons
- A drone defence depends on weather. Plan the fog-day fallback; artillery still held the front in bad weather [16, p. 11].
- Protect what the infiltrator wants. Drone crews, command posts and supply nodes need alternates and guards early.
- Logistics is a target set. Many small loads beat one convoy.
- Keep something back. A reserve lent upward is missing when the rear fills with infiltrators.
- Fix the withdrawal trigger in advance, with routes and order of movement.
Unresolved questions
- How much supply the interdiction actually stopped.
- The real size of the infiltration.
- What the special forces achieved, and where they landed.
- Ukrainian losses, which were not disclosed.
- Battalion-level decisions here are composites.
Further reading and viewing
▶Current Time report on Russian drones targeting Ukrainian supply routes near PokrovskVideo: Battle for Pokrovsk update, Russian drones hunting Ukrainian supply routes · Radio Free Europe/Radio Liberty (Current Time), 2025
- The report page for the video above [23]; RUSI, Tactical Developments During the Third Year of the Russo–Ukrainian War (2025) [16]; US Army FM 3-90 Tactics (2023) [20].
- Command the battalion yourself in the training scenario "Pokrovsk Axis Defence".
Sources
- Yuri Zoria, "ISW: Russian advance near Donetsk's Pokrovsk slows as focus may shift to Kostiantynivka in 2025", Euromaidan Press, 2025-02-16 (relaying ISW, 15 Feb 2025). https://euromaidanpress.com/2025/02/16/isw-russian-advance-near-donetsks-pokrovsk-slows-as-focus-may-shift-to-kostiantynivka-in-2025/ (accessed 2026-10-14)
- Euromaidan Press, "ISW: Russia took 21 months to reach Pokrovsk using air interdiction and drone suppression", 2025-11-05 (relaying ISW, 4 Nov 2025). https://euromaidanpress.com/?p=372311 (accessed 2026-10-14)
- John T. Psaropoulos, "Russia infiltrates Pokrovsk with new tactics that test Ukraine's drones", Al Jazeera, 2025-11-06. https://www.aljazeera.com/news/2025/11/6/russia-infiltrates-pokrovsk-with-new-tactics-that-test-ukraines-drones (accessed 2026-10-14)
- Yuri Zoria, "ISW: Russia's Dobropillia push isn't an operational-level breakthrough — yet", Euromaidan Press, 2025-08-12. https://euromaidanpress.com/2025/08/12/isw-russias-dobropillia-push-isnt-an-operational-level-breakthrough-yet/ (accessed 2026-10-14)
- Yuri Zoria, "ISW: Russia's advance near Dobropillia is fracturing under Ukrainian counterattacks", Euromaidan Press, 2025-08-19. https://euromaidanpress.com/2025/08/19/isw-russias-advance-near-dobropillia-is-fracturing-under-ukrainian-counterattacks/ (accessed 2026-10-14)
- Yuri Zoria, "Dnipro command flatly denies DeepState report of Russian control near Donetsk's Dobropillia", Euromaidan Press, 2025-08-12. https://euromaidanpress.com/2025/08/12/dnipro-command-flatly-denies-deepstate-report-of-russian-control-near-donetsks-dobropillia/ (accessed 2026-10-14)
- Tania Myronyshena, report on the military-intelligence special forces raid in Pokrovsk, the Russian claim and the Ukrainian denial, Kyiv Independent, 2025-11-01. https://kyivindependent.com/ukraines-hur-launches-special-forces-raid-in-embattled-pokrovsk-media-report/ (accessed 2026-10-14)
- Yuri Zoria, "ISW: Russian milbloggers declare Pokrovsk 'almost taken' — ISW says evidence shows only 46% control", Euromaidan Press, 2025-11-13. https://euromaidanpress.com/2025/11/13/isw-russian-milbloggers-declare-pokrovsk-almost-taken-isw-says-evidence-shows-only-46-control/ (accessed 2026-10-14)
- LIGA.net, "Defenders retreated near Pokrovsk and Myrnohrad, leveling the front – map", 2025-12-08. https://news.liga.net/en/politics/news/defenders-retreated-near-pokrovsk-and-myrnohrad-leveling-the-front-map (accessed 2026-10-14)
- Benjamin Murdoch, "ISW: Pokrovsk, Myrnohrad will likely fall – but Russia will pay in time and blood", Euromaidan Press, 2025-12-11. https://euromaidanpress.com/?p=379911 (accessed 2026-10-14)
- TSN, "Ukrainian units may enter task zone: 7th Rapid Response Corps commander discusses logistics in Pokrovsk", 2025-11-28. https://tsn.ua/en/ato/ukrainian-units-may-enter-task-zone-7th-rapid-response-corps-commander-discusses-logistics-in-pokrovsk-2966393.html (accessed 2026-10-14)
- Francis Farrell, "Analysis: Pokrovsk on the brink as Russian troops, drones infiltrate deeper into Ukraine's fortress city", Kyiv Independent, 2025-10-22. https://kyivindependent.com/analysis-pokrovsk-on-the-brink-as-russian-troops-drones-infiltrate-deeper-into-ukraines-fortress-city/ (accessed 2026-10-14)
- Espreso Global, "Ukrainian troops repel Russian forces near Pishchane, close to Pokrovsk", 2024-12-16. https://global.espreso.tv/russia-ukraine-war-ukrainian-troops-repel-russian-forces-near-pishchane-close-to-pokrovsk (accessed 2026-10-14)
- Khrystyna Bondarieva, "UK Defence Intelligence analyses situation around Pokrovsk, Donetsk Oblast", Ukrainska Pravda, 2025-08-02 (UK MoD claim). https://www.pravda.com.ua/eng/news/2025/08/02/7524525/ (accessed 2026-10-14)
- Kyiv Post, "British Defence Intelligence Update Ukraine 3 December 2025" (UK MoD claim), 2025-12-03. https://www.kyivpost.com/amp/post/65569 (accessed 2026-10-14)
- Jack Watling and Nick Reynolds, Tactical Developments During the Third Year of the Russo–Ukrainian War, RUSI, 2025-02-14 (pp. 4, 5, 8–11, 15, 17). https://static.rusi.org/tactical-developments-third-year-russo-ukrainian-war-february-2205.pdf (accessed 2026-10-14)
- Seth G. Jones and Riley McCabe, "Russia's Battlefield Woes in Ukraine", CSIS, 2025-06-03. https://www.csis.org/analysis/russias-battlefield-woes-ukraine (accessed 2026-10-14)
- Seth G. Jones and Riley McCabe, "Russia's Grinding War in Ukraine", CSIS, 2026-01-27. https://www.csis.org/analysis/russias-grinding-war-ukraine (accessed 2026-10-14)
- Rochan Consulting, "Impressions from the field research trip to Ukraine – October 2025", undated (late 2025). https://rochan-consulting.com/impressions-from-the-field-research-trip-to-ukraine-october-2025/ (accessed 2026-10-14)
- Headquarters, Department of the Army, FM 3-90 Tactics, 2023-05-01 (paras 2-82 to 2-84, 8-113, 9-10 to 9-12, 11-1, 11-71 to 11-82, A-68, A-69). https://irp.fas.org/doddir/army/fm3-90.pdf (accessed 2026-10-14)
- James J. Smith, "Retrograde operations: planning and execution", Army Sustainment (army.mil), 2014-03-04 (citing ADRP 3-90). https://www.army.mil/article-amp/120749/retrograde_operations_planning_and_execution (accessed 2026-10-14)
- Timothy Heck and Walker Mills, "No Retreat? The Flaw in the US Military's Preparation for Large-Scale Combat Operations", Modern War Institute at West Point, 2023-02-07. https://mwi.westpoint.edu/no-retreat-the-flaw-in-the-us-militarys-preparation-for-large-scale-combat-operations/ (accessed 2026-10-14)
- Current Time (RFE/RL), "Battle for Pokrovsk: Russian Drones Hunt Ukrainian Supply Routes", 2025-12-17. https://www.rferl.org/a/pokrovsk-battle-update-russian-drones-target-ukrainian-logistics/33624838.html (accessed 2026-10-14)
- Open-Meteo, Historical Weather API (ERA5 reanalysis), Pokrovsk grid cell, daily weather, precipitation, sunrise and sunset, 1 Oct–10 Dec 2025. https://archive-api.open-meteo.com/v1/archive?latitude=48.28&longitude=37.18&start_date=2025-10-01&end_date=2025-12-10&daily=weather_code,temperature_2m_max,temperature_2m_min,precipitation_sum,sunrise,sunset&timezone=Europe%2FKyiv (accessed 2026-10-14)
- Open-Meteo, Historical Weather API (ERA5 reanalysis), Pokrovsk grid cell, hourly relative humidity and low cloud, 15 Oct–10 Dec 2025. https://archive-api.open-meteo.com/v1/archive?latitude=48.28&longitude=37.18&start_date=2025-10-15&end_date=2025-12-10&hourly=relative_humidity_2m,cloud_cover_low&timezone=Europe%2FKyiv (accessed 2026-10-14)
- Open-Meteo, Elevation API, Pokrovsk, Myrnohrad, Shevchenko, Pishchane, Kotlyne, Udachne, Rodynske, Selydove, Lysivka. https://api.open-meteo.com/v1/elevation?latitude=48.2771,48.3079,48.2219,48.2332,48.2553,48.2394,48.3539,48.1501,48.2195&longitude=37.1772,37.2591,37.1421,37.1080,37.0501,36.9827,37.2033,37.3018,37.2706 (accessed 2026-10-14)
- OpenStreetMap Nominatim, place search for Pokrovsk and surrounding settlements. https://nominatim.openstreetmap.org/search?q=Pokrovsk&format=json&limit=3&countrycodes=ua (accessed 2026-10-14)
- Wikimedia Commons, File:Pokrovsk during the war (2025-01-08).webp (Donetsk Regional Military Administration, CC BY 4.0). https://commons.wikimedia.org/wiki/File:Pokrovsk_during_the_war_(2025-01-08).webp (accessed 2026-10-14)
- Wikimedia Commons, File:UA fiber-optic FPV drone 01.webp (ArmyInform, CC BY 4.0). https://commons.wikimedia.org/wiki/File:UA_fiber-optic_FPV_drone_01.webp (accessed 2026-10-14)