Daily intelligence

RF KAB Strikes Hit Zaporizhzhia Residential Sector; UAF Claims Advances in Pokrovsk Direction

Published Intelligence Summary & Geospatial Analysis
Report number
759

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 66.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 Russian Federation (RF) guided air bomb (KAB) strikes against a private residential sector in Zaporizhzhia (Zaporizhzhia Oblast), resulting in one confirmed fatality and severe structural damage. This incident underscores the continued RF strategy of targeting urban civilian infrastructure to degrade morale and strain emergency response capabilities, despite clear weather conditions facilitating high-tempo aerial operations across the frontline.

Simultaneously, open-source intelligence indicates localized Russian tactical advances in the Pokrovsk direction (Donetsk Oblast), with reports of forces occupying Sukhetske and advancing near Nicanorivka and Rodynske. While these claims require independent geospatial verification, they highlight sustained pressure on Ukrainian defensive lines in the east. In the deep rear, Ukrainian Armed Forces (UAF) drone activity disrupted civil aviation and public events in Omsk (Omsk Oblast, RF), demonstrating persistent asymmetric reach into the Russian strategic interior.

Operational Updates

  • Eastern Sector (Donetsk/Kharkiv): Ground operations remain highly kinetic. DeepState reports indicate RF forces occupied Sukhetske and advanced near Nicanorivka and Rodynske in the Pokrovsk direction (Confidence: MEDIUM). In the Krasno-Lyman axis, the RF 25th Combined Arms Army institutionalized dedicated drone battalions ("Hyperion") for combined arms operations. UAF FPV drones successfully destroyed an RF BM-21 "Grad" MLRS in Donetsk Oblast (Confidence: MEDIUM).
  • Southern Sector (Zaporizhzhia/Mykolaiv/Odesa): RF KAB glide bombs struck a private residential sector in Zaporizhzhia city, causing one death and two injuries from acute stress; rescue operations have concluded (Confidence: HIGH). RF Ministry of Defense claimed strikes on port infrastructure and bulk carriers in Mykolaiv and the Black Sea, though independent verification of maritime damage is pending (Confidence: LOW/MEDIUM).
  • Northern Sector (Sumy/Chernihiv): RF forces struck the "Sumyteploenergo" thermal power plant in Sumy city, causing a large fire and significant damage (Confidence: HIGH). Multiple KAB strikes were also directed at the Kovpakivskyi district. UAF Air Force tracked jet-powered UAVs transiting from Sumy towards Poltava.

Deep Strikes & Air Defense

  • UAF Deep Strikes:
    • Omsk Oblast: UAF UAVs forced the closure of Omsk airport and cancellation of City Day events; a field fire was confirmed from downed debris, while claims of an oil refinery strike remain unconfirmed (Confidence: HIGH for disruption, LOW for refinery hit).
    • Samara/Chelyabinsk: Unconfirmed reports indicate massive fires at a Wildberries warehouse in Novosemeykino (Samara Oblast) and an industrial concrete facility in Chelyabinsk Oblast, attributed to UAF drone strikes (Confidence: LOW/MEDIUM).
    • Saratov/Kaluga/Bryansk: Kharkiv Governor claimed overnight strikes on the Saratov Oil Refinery, Engels airbase, Lyudinovskaya oil base, and a drone facility; visual confirmation is pending (Confidence: MEDIUM).
  • RF Aerospace Campaign:
    • Zaporizhzhia: KAB strikes on residential areas caused casualties and damage (Confidence: HIGH).
    • Poltava: RF strikes hit critical infrastructure, causing industrial fires involving hazardous materials; no casualties reported (Confidence: HIGH).
    • Mykolaiv/Black Sea: RF MoD claimed strikes on port infrastructure, two bulk carriers, and a maritime tug; claims lack independent corroboration (Confidence: MEDIUM for claims, LOW for damage).
    • Air Defense: UAF intercepted 109 of 133 incoming RF UAVs overnight (~82% rate). A record intercept of an RF Shahed-type UAV at 53 km distance was claimed by the UAF 123rd Brigade near Snake Island using a Wovkulaka Spitfire system (Confidence: MEDIUM).

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:
    • Equipment: One BM-21 "Grad" MLRS destroyed by UAF FPV drone in Donetsk Oblast (Confidence: MEDIUM).
    • Infrastructure: Fires reported at Wildberries warehouse in Samara Oblast and concrete facility in Chelyabinsk Oblast (unconfirmed attribution). Field fire in Omsk Oblast from UAV debris.
  • UAF Losses/Damage:
    • Personnel: One civilian killed and two injured in Zaporizhzhia city KAB strike. No military casualties explicitly reported in input.
    • Infrastructure: Significant damage to "Sumyteploenergo" thermal power plant in Sumy. Industrial fires in Poltava Oblast requiring hazmat response. Severe structural damage to residential sector in Zaporizhzhia.

Confidence Check

  • Zaporizhzhia Civilian Casualties: HIGH (Confirmed by Zaporizhzhia Oblast Military Administration and ASTRA).
  • Sumy TEC Strike: HIGH (Confirmed by pro-RF sources and consistent with strike patterns).
  • Pokrovsk Direction Advances: MEDIUM (Reported by DeepState, requires geospatial verification).
  • Omsk Airport Closure: HIGH (Confirmed by local authorities and Kazakhstan MFA denial of cross-border launch).
  • Mykolaiv/Black Sea Maritime Strikes: LOW/MEDIUM (RF MoD claims only; no independent visual or AIS data provided in input).
  • ZNPP Strike Claims: LOW (RF Rosatom/milblogger claims of UAF drone strike on spent fuel storage remain unconfirmed by IAEA).

The Bottom Line

RF continues to leverage KAB glide bombs against Ukrainian urban centers, evidenced by the fatal strike in Zaporizhzhia and damage to energy infrastructure in Sumy. While ground lines remain largely static, localized Russian advances in the Pokrovsk direction warrant close monitoring for potential breakthroughs. UAF deep-strike campaigns continue to disrupt Russian civil aviation and industrial logistics, as seen in Omsk and Samara. In the next 24 hours, monitor:

  1. Geospatial Verification: Confirmation of Russian territorial gains in Sukhetske and Nicanorivka.
  2. Maritime Logistics: Independent assessment of RF claims regarding strikes on bulk carriers and port infrastructure in Mykolaiv.
  3. Energy Infrastructure: Impact assessment of the strike on "Sumyteploenergo" and industrial fires in Poltava.

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 02 Aug 2026, 15:06 UTCLagged by 66.1 h
Map revision comparison

Against the previous report from 01 Aug 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 66.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

5 visuals
Open full size
Nightwatch daily report #759: Rodynske area

Geospatial Analysis

12 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 12 places with coordinates
Geocoded places in report 759
PlaceCountryLatitude, longitudeCopy
ZaporizhzhiaUA47.83928419999999, 35.13870970000001
SukhetskeUA48.3771108, 37.2221899
NicanorivkaUA0, 0
RodynskeUA48.3507226, 37.2097768
OmskRU54.9913545, 73.3645204
SumyUA50.9077, 34.7981
PoltavaUA49.58826699999999, 34.551417
MykolaivUA46.9660801, 32.003246
Snake IslandUA0, 0
NovosemeykinoRU53.3753761, 50.3474228
ChelyabinskRU55.1644419, 61.4368431
Engels AirbaseRU51.4867682, 46.1251358

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.