UAF Strikes Russian C2 and Logistics as Russian Forces Surge KABs and Prepare Strategic Bomber Fleet
At a glance
Counts of the stored claim records and follow-up, not a summary of the narrative. How to read these labels
- Coverage window
- Not stored for this report.
- Follow-up investigation
- None stored for this report.
- Claim records by status
- This report has no claim records.
- Claim records by confidence
- This report has no claim records.
- SAR measurements
- None supplied to this report. No SAR measurements for this period does not mean that monitored sites were unchanged.
- Frontline map data
- Age of the map data is not available.
Read with these limits in mind
- This report is machine-generated from open sources and may contain errors.
- A source’s publication time is not the time of the event it describes.
- Frontline map data can lag the reporting period; map dates do not establish when territory changed.
- No SAR measurements for this period does not mean that monitored sites were unchanged.
Intelligence Summary
Analyst briefMachine-generated narrative. Labels inside it are written by the model. How to read these labels
Strategic Overview
Russian Ministry of Defense (MoD) sources claim the 36th Brigade has advanced into the Dnipropetrovsk region, indicating an effort to outflank western Donetsk defensive lines.
Ukrainian Armed Forces (UAF) continue to execute a successful deep interdiction campaign, neutralizing key Russian Ground-Based Robotic Systems (GRS), fuel infrastructure, and Electronic Warfare (EW) nodes. The introduction of potential novel assets targeting Russian fiber-optic command and control (C2) infrastructure suggests a tactical shift toward degrading hard-wired Russian communications. Meanwhile, the Kremlin is leveraging Middle Eastern instability in its information operations, while direct logistical impacts are observed via Aeroflot's suspension of UAE flight routes.
Operational Updates
- Eastern Sector (Donetsk/Luhansk): UAF Special Operations Forces (SSO) and HIMARS successfully destroyed a fuel depot in Makiivka, an EW station in Donetsk, and a GRS assembly point belonging to the 1st Separate Motorized Rifle Brigade. Russian leadership highlighted a 68-day solo holdout by a Russian soldier near Grishina on the Pokrovsk axis, indicating severe frontline friction and isolation. Weather in Pokrovsk is 11.7°C, clear (Code 0), with 2.1 m/s winds, providing optimal visibility for deep-strike munitions.
- Southern Sector (Zaporizhzhia/Dnipropetrovsk/Kherson): The Russian MoD claims assault detachments of the 36th Brigade (29th Army, Vostok Group) captured a stronghold within the Dnipropetrovsk region administrative borders. Russian forces launched widespread KAB strikes targeting Zaporizhzhia and Dnipropetrovsk. In the Orikhiv axis, elements of the Russian 71st Regiment are employing TM-62 anti-tank mines for bunker clearing. Weather in Zaporizhzhia (Orikhiv) is 13.2°C, clear, with 1.9 m/s winds.
- Northeastern Sector (Kharkiv/Sumy/Bryansk): A missile alert was triggered in Bryansk Oblast following UAF cross-border pressure. Russian forces conducted targeted strikes against UAF troop concentrations in Sumy Oblast. In Kharkiv, Russian "Akhmat" Spetsnaz and the 245th Motorized Rifle Regiment destroyed a UAF 2S1 Gvozdika using FPV drones. Weather in Kharkiv (Vovchansk) is 10.2°C, clear, with 2.0 m/s winds.
Equipment & Losses
- Confirmed Loss (Russian): Fuel depot in Makiivka; EW station in Donetsk; GRS assembly point in Donetsk; vehicle/infantry column near Oleksandrivka (Zaporizhzhia sector) via HIMARS strike.
- Confirmed Loss (UAF): Su-27 airframe and the Commander of the 39th Tactical Aviation Brigade (Russian MoD claim, corroborating previous UAF reports).
- Unconfirmed Loss (Russian): 35 intercepted UAVs claimed by Russian MoD; damage to fiber-optic C2 infrastructure via novel directed-energy/kinetic UAF drone; Topchiev Institute of Petrochemical Synthesis (TIPS) in Moscow damaged by explosion.
- Procurement/Transfers: Germany to transfer 35 Patriot missiles to Kyiv. SBU charged IRGC Brigadier General Abdollah Mehrabi for Shahed-136 technology transfers.
Confidence Check
- HIGH: UAF HIMARS/SSO strikes in Donetsk and Zaporizhzhia; Russian KAB aviation surge; SAR anomalies at strategic airbases; arrest of Alexei Khvorostyanko in Moscow.
- MEDIUM: Russian tactical advance into Dnipropetrovsk administrative territory; Hungarian legislative seizure of Oschadbank assets.
- LOW: UAF deployment of directed-energy weapons (DEW) against fiber-optic lines; Russian mass-interception of 35 UAVs.
The Bottom Line
The UAF is demonstrating operational precision by systematically degrading Russian automated sustainment (GRS) and C2 networks. However, the Russian operational tempo is accelerating, evidenced by the KAB surge and mechanized probes across the Dnipropetrovsk border.
Legacy provenance
This archived report predates claim-level evidence records. Treat its confidence labels as editorial assessments rather than independently verifiable citations.
Frontline context
Territorial control and recent changes shown by DeepState.
Against the previous report from 09 Mar 2026, 15:02 UTC, bright red is newly marked Russian-occupied and green is no longer marked occupied. For the infiltration area, yellow is this report and cyan is the previous report.
Report Visuals
3 visualsGeospatial Analysis
6 locations identified
Historical reconstruction from source editions available by report time.
Places and data export
Coordinates come from geocoding place names found in the report. They locate the named place, not the event described there. Latitude and longitude are WGS 84 decimal degrees.
Show 6 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Makiivka | Ukraine | 48.0459557, 37.9666901 | |
| AB Olenya | Russia | 69.214167, 33.37 | |
| Orikhiv | Ukraine | 47.5658802, 35.7876745 | |
| Dnipropetrovsk | Ukraine | 48.464717, 35.046183 | |
| Donetsk | Ukraine | 48.015883, 37.80285 | |
| Vovchansk | Ukraine | 50.284234, 36.9329429 |
How to read the labels
Labels on this page come from three separate mechanisms. A label from one does not mean the same as a similar word from another.
1. In the narrative
Machine-generated narrative. Labels inside it are written by the model.
- Unconfirmed:
- Written by the model. Its instruction is to mark claims that rest on a single source.
- Confidence: HIGH / MEDIUM / LOW
- Written by the model. The report stores no definition of these levels, and they are not computed from the claim records. Do not read them as the record confidence above.
2. On claim records: confidence
Record confidence is a threshold on a number stored with the source observation. It is not a probability that the event happened. The follow-up investigation may lower it and never raises it.
- HIGH confidence
- The status is Independently corroborated, Geolocated or Imagery corroborated, and the stored confidence of the supporting observation is at least 0.75.
- MEDIUM confidence
- The stored confidence of the supporting observation is at least 0.5 and the rule for HIGH is not met.
- LOW confidence
- The stored confidence of the supporting observation is below 0.5.
2. On claim records: status
Machine-selected records from the source ledger, labelled by fixed rules. They are a separate selection and are not a list of the sources behind the narrative above.
- Single-source claim
- One retained source observation supports the record, from a sender that is not on the list of official bodies.
- Official claim
- One retained source observation, from a sender whose name matches a keyword list of official bodies. It says who made the claim, not that the claim is verified.
- Multiple reports, same origin
- Several retained observations that do not meet the rule for independent corroboration. They are treated as one origin.
- Independently corroborated
- At least two distinct source documents from at least two differently named senders. The rule compares sender names and document fingerprints. It does not establish that the senders had separate access to the event, and a repost under another name can satisfy it.
- Geolocated
- One retained observation carrying coordinates with a geolocation confidence of at least 0.5. It concerns the location only, not the cause or the outcome.
- Imagery corroborated
- Imagery supports the observation. It does not by itself establish cause or intent.
- Analyst assessment
- A Nightwatch assessment rather than a directly observed fact.
- Contested
- Set by the follow-up investigation: material source accounts remain in conflict.
- Corrected
- Set by the follow-up investigation: the record was changed after the investigation reached a definitive answer.
- Insufficient evidence
- Set by the follow-up investigation: the available evidence does not support the record as first labelled.
3. In the follow-up investigation
Machine-run follow-up on one selected claim record. Sources listed include material that was retrieved and not used.
- Confirmed
- The investigation reached a definitive answer supporting the selected claim. The report was rewritten after it.
- Refuted
- The investigation reached a definitive answer against the selected claim. The report was rewritten after it.
- Materially refined
- The investigation reached a definitive answer that changes the selected claim in a material way. The report was rewritten after it.
- Inconclusive
- The investigation did not reach a definitive answer. The report text was kept; the investigation could only attribute, hedge or lower confidence. Individual findings inside it can still carry their own outcome.
Each finding has its own outcome and a confidence written by the model. That confidence is in the finding as worded, which may itself be a statement that something is unknown.
Kinds of investigation source
- External web page
- A web page retrieved during the follow-up investigation. Its address is stored and linked.
- Source observation behind a claim record
- A source observation the claim records were built from. No address is stored for it.
- Nightwatch archive item
- An item found by searching the Nightwatch archive during the investigation. It may be unrelated to the question. No address is stored for it.
