Daily intelligence

UAF Deep Strikes Target Ufa Refineries and Cripple Crimean Grid; RF Adapts via FPV Saturation

Published Intelligence Summary & Geospatial Analysis
Report number
721

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

Ukrainian Armed Forces (UAF) deep-strike operations are inflicting compounding logistical friction, most notably through unconfirmed strikes on the Ufa refinery complex (~1,300km range) targeting 10.5M tons/year of processing capacity. Simultaneously, a severe energy and fuel emergency is unfolding in occupied Crimea, where UAF destruction of coastal infrastructure has forced the implementation of rolling blackouts and emergency diesel generator deployment across the Sevastopol banking sector.

In response to mounting rear-area vulnerabilities, Russian Federation (RF) forces are rapidly adapting their tactical strike profiles. This includes the widespread formation of mobile "BARS" machine-gun groups in the Volga region to mitigate air defense gaps, the introduction of jet-powered (reactive) UAVs to bypass UAF intercept windows, and extreme localized FPV drone saturation (accounting for over 70% of strikes in the Zaporizhzhia sector). Concurrently, UAF is generating new northern brigades to counter verified military infrastructure build-ups along the Belarusian border.

Operational Updates

  • Northern/Northeastern (Belarus/Sumy/Kharkiv/Chernihiv): Ukrainian intelligence (SZRU) confirmed significant Belarusian military infrastructure construction, including Fuel Base 2766 (Krasny Bereg) and Ammo Base 1405 (Velykaya Gorodnya). UAF authorities ordered the mandatory evacuation of 12 border villages in Chernihiv due to intensifying strikes. RF deployed jet-powered UAVs from the Sumy/Kharkiv border toward Poltava. Weather in Kharkiv (21.0°C, light rain, 4.2 m/s wind, 49% cloud) remains permissive for low-altitude operations.
  • Eastern (Donetsk/Luhansk): High-intensity urban combat persists in Krasnyi Lyman. RF aviation utilized a FAB-1500 to destroy a river crossing at Mayaky, complicating UAF logistics on the western bank of the Seversky Donets. High activity of the UAF NGU "Omega" drone unit is reported in the Pokrovsk axis. Weather in Pokrovsk (20.9°C, overcast, 2.4 m/s wind, 100% cloud cover) continues to provide visual concealment from high-altitude ISR.
  • Southern (Zaporizhzhia/Kherson/Crimea): UAF forces destroyed the Korsak River auto bridge, restricting movement on the "Novorossiya" highway. In Zaporizhzhia, RF forces conducted massive FPV saturation, with 694 FPV strikes recorded in 24 hours. The Kinburn Spit flag placement was confirmed by UAF Navy as a remote drone operation; physical ground control remains contested with active RF EW and drone launch sites. Weather in Kherson is hot (30.8°C, partly cloudy, 4.5 m/s wind).
  • Deep Rear (Russian Interior): Unconfirmed drone strikes targeted the Bashneft-UNPZ and Bashneft-Ufaneftekhim refineries in Ufa. Massive "Rocket Danger" alerts were triggered across more than 10 RF regions, including Moscow, Penza, and Saratov, indicating heightened sensitivity to UAF OWA-UAV ingress.

SAR Intelligence (Satellite Data)

  • High Priority Anomalies: Critical deviations from historical baselines were detected at the 549th Base Air Group (Score: 7.21), AB Pribylovo (Score: 7.21), 155th Central Communications Warehouse (Score: 6.69), 66th Guards Pontoon-Bridge Regiment (Score: 5.79), 81st Radio-Technical Regiment (Score: 3.43), and the 15th Separate Coastal Missile-Artillery Brigade (Score: 3.28).
  • Analysis: Elevated activity at Leningrad Military District aviation nodes (549th Base Air Group, AB Pribylovo) strongly correlates with emergency dispersal or heightened sortie readiness. High anomaly scores at the 66th Guards Pontoon-Bridge Regiment and 155th Central Comms in the Moscow Military District indicate significant administrative reallocation or emergent engineering deployments. The 15th Coastal Brigade activity aligns with defensive posturing in response to the ongoing Crimean energy crisis.

Equipment & Losses

  • Ufa Refineries (Bashneft): Unconfirmed damage to primary distillation units ELOU-AVT-6 and AVT-4.
  • Logistics Infrastructure (UAF Strikes): Confirmed destruction of the Korsak River auto bridge (Zaporizhzhia) and rail bridges over the Aidar and Luhanchik rivers (Luhansk).
  • Mayaky Crossing: Destroyed by an RF FAB-1500 glide bomb.
  • "Lancet" Loitering Munition: First recorded combat use by the RF "African Corps" against a vehicle in Mali.

Confidence Check

  • HIGH: Crimean energy/fuel emergency and banking mitigation measures; Belarusian border infrastructure development; Kinburn Spit flag placement as an unmanned operation.
  • MEDIUM: Extent of structural damage to the Korsak, Aidar, and Luhanchik bridges; tactical impact of jet-powered UAV deployments.
  • LOW: BDA for the Ufa refinery strikes (pending satellite corroboration due to raw report timestamp anomalies); RF claims of 269 intercepted drones overnight.

The Bottom Line

The UAF's synchronized targeting of deep-rear refining capacity and occupied coastal infrastructure is generating severe, cascading logistical strain for the RF, evidenced by Crimean blackouts and Volga-region civilian fuel rationing. RF forces are attempting to offset these rear-area deficits by maintaining high offensive tempo in the East and South, utilizing extreme FPV saturation and integrating faster jet-powered UAVs to defeat UAF point defenses. Monitor UAF force generation and deployment in the Northern Sector as a primary indicator of assessed threat levels regarding the Belarusian border militarization.

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 Jun 2026, 15:03 UTC
Map revision comparison

Against the previous report from 24 Jun 2026, 15:03 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

5 visuals
Open full size
Nightwatch daily report #721: Krasnyi Lyman area

Geospatial Analysis

15 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 15 places with coordinates
Geocoded places in report 721
PlaceCountryLatitude, longitudeCopy
UfaRU54.73479099999999, 55.9578555
SevastopolUA44.61665, 33.525367
Krasny BeregBY54.4449717, 30.32659809999999
Velykaya GorodnyaBY54.54494940000001, 30.4082201
ChernihivUA51.4982, 31.28935
Krasnyi LymanUA48.9897585, 37.8049964
MayakyUA48.1300538, 39.7672162
PokrovskUA48.282193, 37.1847804
ZaporizhzhiaUA47.83928419999999, 35.13870970000001
Kinburn SpitUA46.635417, 32.616867
MoscowRU55.340396, 38.2917651
549th Base Air GroupRU59.9310584, 30.3609097
AB PribylovoRU60.425671, 28.6753152
66th Guards Pontoon-Bridge RegimentRU55.7568721, 37.6150527
15th Separate Coastal Missile-Artillery BrigadeRU45.3453029, 34.4997274

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.