Daily intelligence

RF Ballistic Strikes Kill First Responders in Kyiv; SBU Drones Ignite Ufa Refineries

Published Intelligence Summary & Geospatial Analysis
Report number
758

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
Newest map data is 42.1 h older than this report.

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 most significant operational development of the last 24 hours is the execution of a multi-wave Russian Federation (RF) aerospace campaign against Kyiv, resulting in the death of a patrol police officer during a secondary strike and severe damage to civilian logistics infrastructure. This escalation coincides with a successful Ukrainian Security Service (SBU) deep-strike operation targeting three Bashneft refineries in Ufa (Bashkortostan Oblast), confirming Ukraine’s sustained capacity to degrade RF energy infrastructure at ranges exceeding 1,600 km.

Tactically, the conflict remains characterized by high-tempo attritional ground combat with no verified major territorial shifts, despite RF claims of advances in Kupiansk and Zaporizhzhia. The convergence of intensified RF strikes on Ukrainian commercial logistics (e.g., Rozetka, Nova Poshta) and continued UAF asymmetric strikes on RF rear-area fuel networks highlights a mutual strategy of economic and logistical degradation. Weather conditions across the contact line remain clear and dry, facilitating continued UAV and artillery operations.

Operational Updates

  • Eastern Sector (Donetsk/Kharkiv): Ground operations remain static but kinetic. RF milbloggers claim the 37th Separate Guards Motorised Rifle Brigade captured Lybytske (Zaporizhzhia Oblast) and that forces occupied a structure in central Kupiansk (Kharkiv Oblast); these claims lack independent geospatial verification. In the Kostiantynivka direction, RF units employed aerial mining combined with FPV drones to interdict UAF logistics north of the city. RF KAB glide bomb strikes continued against Sloviansk and Kharkiv urban areas.
  • Southern Sector (Zaporizhzhia/Mykolaiv/Odesa): No significant ground maneuvers were reported. RF forces claimed strikes on port infrastructure in Odesa and Mykolaiv, including POL tanks and a sea tug; independent damage assessment is pending. UAF Air Force tracked jet-powered UAVs approaching Zatoka and Mykolaiv from the Black Sea. In Zaporizhzhia Oblast, RF sources alleged a UAF strike on a residential building in Enerhodar, though casualty figures remain unverified.
  • Northern Sector (Sumy/Chernihiv): UAF conducted cross-border drone and artillery strikes into Belgorod Oblast (RF), injuring two civilians in Novaya Nelidovka and Lugovka. RF forces continued UAV pressure on Sumy and Chernihiv, with a drone striking a mobile Ukrposhta branch near Pushkari (Chernihiv Oblast), injuring two staff members. The 47th Separate Mechanized Brigade demonstrated the operational use of Unmanned Ground Vehicles (UGVs) for logistics and medevac in Sumy Oblast.

Deep Strikes & Air Defense

  • UAF Deep Strikes:
    • Bashkortostan: SBU drones struck three Bashneft refineries in Ufa; visual evidence confirms massive fires (Confidence: HIGH).
    • Krasnodar Krai: SBU claimed strikes on four radar systems; uncorroborated by visual evidence (Confidence: LOW).
    • Belgorod Oblast: UAF strikes injured two civilians in border villages (Confidence: HIGH).
    • Crimea: UAF 422 Luftwaffe drone unit claimed a strike on MVD forces using RAM2X and Bulava drones (Confidence: MEDIUM).
  • RF Aerospace Campaign:
    • Kyiv: A ballistic missile strike killed 22-year-old patrol police officer Yegor Terekhin during a secondary impact while he was assisting civilians. Severe structural damage was confirmed at the Velmart shopping center and other residential buildings. Total casualties from the overnight barrage stand at 9 dead and 23 injured (Confidence: HIGH).
    • Kyiv Oblast: A Shahed-type drone struck a Rozetka e-commerce warehouse in Brovary, killing one employee and injuring six to seven others (Confidence: HIGH).
    • Dnipropetrovsk Oblast: An RF strike hit a passenger minibus in Chervonohryhorivka (Nikopol district), injuring seven civilians, two critically (Confidence: HIGH).
    • Vinnytsia Oblast: Visual evidence confirms a fire at a Nova Poshta logistics facility in Haisyn, attributed to an RF drone strike (Confidence: MEDIUM).
    • Odesa/Mykolaiv: RF MoD claimed strikes on POL storage tanks in Odesa port and a USV-equipped tug in Mykolaiv. RF sources also claimed the destruction of the Zatoka railway bridge; satellite imagery shows no structural collapse, assessing the claim as exaggerated (Confidence: LOW for bridge collapse, MEDIUM for strikes).

SAR Intelligence (Satellite Data)

  • Imagery Review: No validated exact-track backscatter-change measurements available from imagery acquired in the last 24 hours.
  • Assessment: Nothing significant to report.

Equipment & Losses

  • RF Losses/Damage:
    • Infrastructure: Confirmed massive fires at three Bashneft refineries in Ufa. Fire extinguished at Nizhnekamskneftekhim complex in Tatarstan (reported by RF authorities).
    • Maritime: Discrepancy exists regarding a sunken vessel in the Black Sea; SBU/Rosatom confirm sinking of sanctioned ship Yanina, but USV footage shows Bourda Monrovia (Confidence: MEDIUM for incident, LOW for specific identification).
  • UAF Losses/Damage:
    • Personnel: One patrol police officer killed in Kyiv; one Rozetka employee killed in Brovary; two Ukrposhta staff injured in Chernihiv Oblast; seven civilians injured in Dnipropetrovsk Oblast.
    • Infrastructure: Severe damage to Velmart shopping center and residential buildings in Kyiv. Fire at Rozetka warehouse in Brovary. Fire at Nova Poshta facility in Haisyn.

Confidence Check

  • Kyiv Casualties & Damage: HIGH (Confirmed by DSNS visuals and official police reports).
  • Ufa Refinery Strikes: HIGH (Confirmed by visual evidence of fires).
  • RF Territorial Claims (Lybytske/Kupiansk): LOW/MEDIUM (Unverified by independent geolocation; likely information operations).
  • Zatoka Bridge Collapse: LOW (Satellite imagery contradicts RF claims of structural failure).
  • Maritime Vessel Identity: MEDIUM (Incident confirmed, but target identity discrepancy between Yanina and Bourda Monrovia remains unresolved).

The Bottom Line

The RF’s intensification of ballistic and drone strikes against Ukrainian civilian logistics and first responders in Kyiv and Brovary represents a deliberate effort to degrade economic resilience and morale. Simultaneously, UAF’s successful strikes on Ufa refineries demonstrate that RF deep-rear energy infrastructure remains vulnerable despite increased air defense posturing. In the next 24 hours, monitor:

  1. Logistical Impact: Assessment of supply chain disruptions following strikes on Rozetka and Nova Poshta facilities.
  2. Zatoka Infrastructure: Verification of actual damage to the Zatoka substation and rail approaches, despite the bridge remaining intact.
  3. RF Satellite Deployment: Operational status of the newly claimed Rassvet satellite constellation, which may enhance RF C4ISR capabilities.

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 01 Aug 2026, 15:05 UTCLagged by 42.1 h
Map revision comparison

Against the previous report from 31 Jul 2026, 15:05 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

The latest control-map interval ended 42.1 hours before this report. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
+2.4 km²
24 h ending 30 Jul 2026, 20:59 UTC
Daily net
+2.4 km²
24.3 h comparison
Seven-day net
+20 km²
175.3 h comparison
Largest changes in the latest measured interval
Near Siversk
2.4 km² changed · RF-held gained 2.4 / lost 0.0 km²

Positive values indicate an increase in Russian-occupied area; negative values indicate a decrease. Yellow marks DeepState's infiltration area (gray zone), which is not included in occupied-area totals.

Report Visuals

4 visuals
Open full size
Nightwatch daily report #758: Odesa area

Geospatial Analysis

11 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 11 places with coordinates
Geocoded places in report 758
PlaceCountryLatitude, longitudeCopy
KyivUA50.4503596, 30.5245025
BrovaryUA50.511083, 30.7909
UfaRU54.73479099999999, 55.9578555
KupianskUA49.7055574, 37.6027997
LybytskeUA0, 0
OdesaUA46.4845702, 30.7326047
MykolaivUA46.9660801, 32.003246
HaisynUA48.8139473, 29.3812035
SumyUA50.9077, 34.7981
Belgorod OblastRU0, 0
ZatokaUA46.06625409999999, 30.4528371

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.