Daily intelligence

UAF Expands Deep-Strike Energy Interdiction and Passive C-UAS Defenses Amid Sustained RF Offensives

Published Intelligence Summary & Geospatial Analysis
Report number
678

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

Machine-generated narrative. Labels inside it are written by the model. How to read these labels

Strategic Overview

The bottom line up front is the continued degradation of Russian Federation (RF) fuel logistics by Ukrainian Armed Forces (UAF) deep strikes, evidenced by successful engagements against the Ryazan petrochemical facility and the Solnechnogorsk Pumping Station. Concurrently, UAF has rapidly scaled passive counter-UAS (C-UAS) infrastructure, deploying over 1,170 km of overhead netting to protect vital frontline logistics corridors.

RF forces maintain high-tempo infantry pressure in the east and south, continuing a strategy of decentralized attrition while standardizing commercial Li-ion battery usage to extend tactical FPV range. RF strike packages continue to route through central Ukraine, exploiting overcast conditions to test secondary UAF air defense (AD) handoff seams.

Operational Updates

  • Northern/Kharkiv Sector: RF maintains high-frequency infantry assaults (>150 engagements in early May) on the South-Slobozhansky axis. UAF NGU "Khartia" Brigade maintains defensive control and introduced aerial-net interceptor UAVs to physically capture RF ISR drones. Sustained RF KAB strikes continue targeting Sumy and Kharkiv. Weather in Vovchansk (27.8°C, 100% cloud cover, 2.2 m/s wind) and forecasted fog will degrade optical tracking, favoring acoustic cueing.
  • Eastern/Donbas Sector: RF claims the capture of Grishino (DPR) by the 30th Separate Guards Motorised Rifle Brigade. UAF has not verified this change in control lines. The frontline remains fluid under heavy artillery and FPV pressure along the Pokrovsk axis. Weather in Pokrovsk (18.2°C, light rain, 100% cloud cover, 2.1 m/s wind) restricts rotary-wing mobility and limits optical counter-battery acquisition.
  • Southern/Zaporizhzhia Sector: UAF "Artan" unit is executing clearance operations in Stepnohirsk. RF Vostok Group claims the employment of TOS-1A thermobaric systems against hardened UAF fortifications. RF forces are standardizing commercial Li-ion battery packs for extended FPV endurance near Vasylivka. Weather in Orikhiv (19.4°C, 100% cloud cover, 2.4 m/s wind) masks low-altitude UAS routing but restricts long-range visual reconnaissance.
  • Strategic Rear & Belarus: UAF strikes ignited fires at the Ryazan refinery and damaged four RVS-5000 tanks at the Solnechnogorsk Pumping Station. UAF has extended overhead AD netting along logistics routes at a rate of 8.5 km/day. Meanwhile, Belarus restricted civilian access to 19 border forest districts; while this aligns with historical covert staging patterns, no kinetic activity is confirmed.

SAR Intelligence (Satellite Data)

  • High Priority: No SAR intelligence data is available from imagery acquired in the last 24 hours.
  • Analysis: Battle damage assessment (BDA) for the Ryazan refinery and Solnechnogorsk Pumping Station currently relies on primary radar, commercial satellite imagery, and ELINT.

Equipment & Losses

  • Confirmed Sightings/Deployments: UAF NGU "Khartia" deployment of net-equipped interceptor UAVs; UAF deployment of >1,170 km of overhead anti-drone logistics netting; RF standardization of Li-ion battery FPV deployments in Zaporizhzhia.
  • Confirmed Losses/Friction: Structural damage to four RVS-5000 fuel tanks at Solnechnogorsk; fire damage at Ryazan refinery; hospitalization of RF-appointed official in Skadovsk following a drone strike.
  • Unconfirmed: RF claims of Grishino capture; RF "Sparta" battalion claims of mid-air FPV interception against a UAF "Baba Yaga" drone; UAF fielding AI-assisted target acquisition for FPVs.

Confidence Check

  • HIGH: UAF strike impacts on Ryazan and Solnechnogorsk; UAF passive C-UAS netting deployment; NGU "Khartia" drone-net operations; UAF domestic treason convictions.
  • MEDIUM: RF standardization of Li-ion FPV configurations; Belarusian border forest closures indicating potential staging; structural damage extent at Solnechnogorsk.
  • LOW: RF territorial capture of Grishino; UAF AI-assisted FPV deployment; RF destruction of UAF infantry in Sumy.

The Bottom Line

UAF precision deep-strikes are successfully taxing RF fuel logistics networks, while the rapid institutionalization of passive netting and kinetic interceptor UAVs demonstrates an evolving, cost-effective counter-UAS doctrine. Commanders should anticipate continued RF attempts to exploit forecasted fog and heavy cloud cover across the northern and eastern sectors to mask localized probing. Intelligence assets must prioritize verifying Belarusian border district activity for signs of force staging.

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.

Report 18 May 2026, 15:06 UTC
Map revision comparison

Against the previous report from 17 May 2026, 15:06 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.

Compare on map
Frontline change measurements are unavailable for this briefing.

Report Visuals

0 visuals

No report-specific visuals are available for this briefing.

Geospatial Analysis

Frontline comparison

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.

No geocoded places are stored for this report.

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.