Daily intelligence

VSRF Executes Pulse Strikes on Dnipro Infrastructure; UAF Sustains Deep Penetration UAV Campaign into Russian Urals

Published Intelligence Summary & Geospatial Analysis
Report number
655

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 operational environment is currently defined by a dual-axis escalation: Russian forces (VSRF) have initiated a sustained "pulse" strike sequence against Dnipro utilizing ballistic missiles and jet-powered loitering munitions to saturate local air defenses (AD), resulting in mass civilian casualties. Concurrently, the Ukrainian Armed Forces (UAF) executed a mass-saturation deep-strike campaign, penetrating over 1,500km to target the Russian industrial heartland in the Chelyabinsk and Sverdlovsk regions.

Tactically, Russian frontline units exhibit acute manpower shortages, evidenced by the cannibalization of technical specialists—specifically, 20% of the 218th UAV Regiment—for infantry assault roles within the 810th Separate Naval Infantry Brigade. In response to sustainment requirements, UAF Commander-in-Chief Syrskyi has mandated a theater-wide logistics audit by 20 May, prioritizing the frontline integration of unmanned ground vehicles (UGVs).

Operational Updates

  • Central Sector (Dnipro/Kyiv): VSRF transitioned from a single ballistic impact (1411Z) to a coordinated series of "double-tap" explosions in Dnipro, heavily taxing AD networks. Casualties stand at 5 confirmed dead and 41 wounded. Secondary UAV vectors continue to probe northern AD corridors toward Kyiv and Chernihiv.
  • Eastern Sector (Donetsk/Pokrovsk): Under primarily overcast conditions (93-100% cloud cover), VSRF tactical aviation is maintaining high-volume guided aerial bomb (KAB) strikes. The 103rd Motorized Rifle Regiment is actively hunting UAF drone operators near Kostyantynivka. Russian sources claim unconfirmed territorial gains near Belytske along the Dobropillya axis.
  • Southern Sector (Zaporizhzhia): VSRF aviation is exploiting clearer conditions (14.6°C, 95% cloud cover transitioning) to launch KABs. Unconfirmed reports suggest a localized VSRF tactical advance of 800m near Mirnoye.
  • Russian Rear Areas: Massive UAF UAV saturation strikes (Russia claims 127 interceptions) reached the Urals. In Tuapse (Krasnodar Krai), widespread "black acid rain" containing combustion byproducts indicates severe secondary environmental effects from recent strikes on regional petroleum infrastructure.
  • Weather Impact: Current temperatures range from 10.5°C in Kharkiv to 15.0°C in Kherson. Overnight forecasts indicate a significant transition to sub-zero minimums (-0.6°C in Kharkiv; -0.3°C in Luhansk) with widespread overcast (Code 3) conditions, requiring immediate adjustments to thermal camouflage protocols.

SAR Intelligence (Satellite Data)

SAR analytics identified 50 locations exhibiting critical anomaly levels, indicating significant deviations from historical baselines. Measurements near zero at other monitored sites confirm baseline continuity, not abandonment.

  • High Priority: CRITICAL deviations were recorded across multiple elements of the 76th Guards Air-Assault Division (Scores > 1.18), specifically its HQ, the 1140th Artillery Regiment, 124th Separate Tank Battalion, and 1682nd Material Support Battalion. Additionally, high anomaly scores were observed at AB Voronezh Malshevo (Score: 0.45, high robust Z-score) and the 197th Landing Ship Brigade in Crimea (Score: 0.43, high robust Z-score).
  • Analysis: The synchronized anomalies across the logistics, artillery, and armored elements of the 76th Guards Air-Assault Division suggest a major reconstitution, repositioning, or staging event. Activity at aviation nodes aligns with the current elevated tempo of standoff and KAB strikes.

Equipment & Losses

  • Confirmed Capability: UAF successfully deployed "Shahedoriz" interceptor systems (RUBAKA unit), neutralizing at least six Russian loitering munitions (Shahed/Gerbera variants).
  • Confirmed Sightings: VSRF employment of jet-powered loitering munitions to compress AD reaction times.
  • Confirmed Losses: UAF drone strike destroyed a VSRF Kamaz 4385 armored truck and a fuel vehicle near Pisky.

Confidence Check

  • HIGH: UAF mass-saturation UAV strikes into the Russian Urals; pulse strikes and mass casualties in Dnipro; UAF logistics audit directive; transition to sub-zero overnight temperatures in northern sectors.
  • MEDIUM: The reassignment of VSRF UAV specialists to infantry assault units; Russian intelligence compromise of German official Signal accounts; Tuapse environmental contamination stemming from petroleum strikes.
  • LOW: VSRF territorial advances near Belytske and Mirnoye; claims of 127 total UAV interceptions by Russian regional governors.

The Bottom Line

The VSRF's "pulse" strike methodology in Dnipro demonstrates a calculated effort to exhaust UAF air defense interceptors during active search and rescue operations. UAF rear-area commanders must redistribute short-range and electronic C-UAS assets to mitigate high-speed jet-powered drones. Tactically, sub-zero overnight temperatures will highly expose frontline infantry thermal signatures; strict enforcement of light and heat discipline is imperative. Finally, the cannibalization of the Russian 218th UAV Regiment indicates acute local manpower friction, presenting a short-term window where VSRF tactical ISR and drone strikes in that sector may degrade.

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 25 Apr 2026, 15:01 UTC
Map revision comparison

Against the previous report from 25 Apr 2026, 00:44 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

4 visuals
Open full size
Nightwatch daily report #655: Kostyantynivka area

Geospatial Analysis

7 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 7 places with coordinates
Geocoded places in report 655
PlaceCountryLatitude, longitudeCopy
DniproUKR48.464717, 35.046183
ChelyabinskRUS55.1644419, 61.4368431
KostyantynivkaUKR48.52394289999999, 37.7075811
TuapseRUS44.0961624, 39.0745411
AB Voronezh MalshevoRUS51.6237435, 39.1650677
SevastopolRUS44.61665, 33.525367
PiskyUKR48.0643351, 37.6741329

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.