Daily intelligence

RF Aerospace Campaign Targets Civilian Infrastructure in Chernihiv and Zaporizhzhia; UAF Confirms Deep Strike Reach to Urals

Published Intelligence Summary & Geospatial Analysis
Report number
752

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 22.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 intensification of Russian Federation (RF) aerospace strikes against Ukrainian civilian infrastructure, resulting in confirmed fatalities in Chernihiv and Zaporizhzhia. A drone strike on an ATB supermarket in Chernihiv killed two civilians, including a child, while guided aerial bombs (KABs) struck Zaporizhzhia city, causing one death. These attacks underscore RF’s continued strategy of targeting rear-area urban centers to degrade morale and disrupt logistics, contrasting with the static nature of frontline ground operations.

Concurrently, Ukrainian President Volodymyr Zelenskyy confirmed the operational reach of Ukrainian Armed Forces (UAF) long-range drones, stating they have executed over 1,000 fire missions this year against targets in the Urals and Siberia (>3,000 km range). This announcement formalizes the strategic shift toward asymmetric deep-strike campaigns aimed at crippling RF energy and logistics nodes far beyond the tactical battlefield. Weather conditions remain overcast with light rain forecast for the eastern front, continuing to degrade optical ISR and favoring RF reliance on artillery and KABs.

Operational Updates

  • Northern Sector (Chernihiv/Sumy/Kharkiv): RF conducted sustained drone and missile strikes across northern oblasts. In Chernihiv (Chernihiv Oblast), a drone strike on an ATB supermarket resulted in 2 fatalities (including a 9-year-old child) and 13 injuries. Visual evidence confirms severe structural damage. In Kharkiv (Kharkiv Oblast), a strike on a residential building killed one person and injured 16. UAVs were tracked moving south from the north towards Chernihiv and Kharkiv throughout the day.
  • Eastern Sector (Donetsk): Ground operations remain characterized by high-tempo attritional assaults. The UAF General Staff reported repelling 46 RF assaults in the Pokrovsk direction, 29 in Kostiantynivka, and 21 in Sloviansk. RF milbloggers claim advances in the Borovsk and Alexeevo-Druzhkivka directions, alleging the capture of Shevchenko and ~30 sq km of territory; these claims lack independent geospatial verification. RF aviation employed FAB-500 bombs against alleged UAF positions in Dobropillia and Kiyanytsia.
  • Southern Sector (Zaporizhzhia/Odesa/Kherson): RF launched KABs and jet-powered UAVs towards Zaporizhzhia city, causing one fatality and one injury. In Odesa Oblast, RF MoD claimed strikes on a container terminal in Chornomorsk port and a bulk carrier south of Odesa; independent battle damage assessment (BDA) is pending. UAVs were tracked heading towards Kherson from the east and Zaporizhzhia from the south.
  • Central Rear (Poltava/Dnipropetrovsk): Overnight, RF Geran drones struck at least four gas stations in Poltava (Poltava Oblast), causing severe fires and structural damage to fuel logistics nodes. In Kryvyi Rih (Dnipropetrovsk Oblast), a strike caused a massive fire at an "Epitsentr" hypermarket, complicating firefighting efforts due to ongoing air raid alerts.

Deep Strikes & Air Defense

  • UAF Deep Strikes: President Zelenskyy confirmed that UAF drones have reached targets >3,000 km away in the Urals and Siberia, executing >1,000 fire missions this year against RF oil facilities, military production, and logistics. Previous strikes on the Tyumen Oil Refinery and Wildberries hubs continue to impact RF interior logistics, with video evidence showing fuel queues in Tyumen.
  • RF Aerospace Campaign: RF launched a complex saturation attack involving ballistic missiles, cruise missiles, and UAVs. Key impacts include:
    • Chernihiv: Drone strike on ATB supermarket (2 dead, 13 injured).
    • Zaporizhzhia: KAB strikes on city infrastructure (1 dead, 1 injured).
    • Kharkiv: Strike on residential building (1 dead, 16 injured).
    • Poltava: Strikes on four gas stations.
    • Odesa/Chornomorsk: Claimed strikes on port infrastructure and maritime vessels (unverified).
  • Air Defense: UAF Air Force tracked and intercepted numerous incoming assets, including Shahed-type UAVs and KABs. A Romanian Air Force F-16 shot down a Shahed-type drone over Romanian territorial waters in the Sulina-Chilia area, prompting a formal diplomatic protest from Bucharest to Moscow.

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 damage to Tyumen Oil Refinery (NPRZ) and Wildberries logistics hubs. Fuel shortages evidenced by queues in Tyumen.
    • Maritime: Unconfirmed claims of damage to vessels in Chornomorsk and south of Odesa.
  • UAF Losses/Damage:
    • Civilian Casualties: 2 dead (incl. child) and 13 injured in Chernihiv; 1 dead and 16 injured in Kharkiv; 1 dead and 1 injured in Zaporizhzhia.
    • Infrastructure: Severe damage to four gas stations in Poltava; major fire at "Epitsentr" hypermarket in Kryvyi Rih; damage to residential buildings in Kharkiv and Chernihiv.

Confidence Check

  • Chernihiv/Zaporizhzhia/Civilian Casualties: HIGH (Confirmed by multiple sources, visual evidence, and official statements).
  • UAF Deep Strike Reach (>3,000 km): HIGH (Confirmed by President Zelenskyy).
  • RF Territorial Claims (Borovsk/Shevchenko): LOW (RF claims only; lacks independent geospatial verification).
  • Chornomorsk Port Strikes: MEDIUM (Claimed by RF MoD; independent BDA pending).
  • Romanian Intercept: HIGH (Confirmed by Romanian President and visual evidence).

The Bottom Line

The conflict trajectory remains defined by RF aerospace saturation against Ukrainian urban centers and civilian infrastructure, countered by UAF asymmetric deep strikes degrading RF energy and logistics nodes in the interior. In the next 24 hours, monitor:

  1. Chornomorsk/Odesa BDA: Verification of RF claims regarding strikes on port infrastructure and maritime vessels in the Black Sea.
  2. Fuel Logistics in Poltava: Assessment of the impact of the four gas station strikes in Poltava on regional military and civilian fuel distribution.
  3. RF Interior Fuel Crisis: Continued monitoring of fuel availability and rationing measures in RF interior regions (e.g., Tyumen) following refinery strikes.

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 26 Jul 2026, 15:06 UTCLagged by 22.1 h
Map revision comparison

Against the previous report from 25 Jul 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

The latest control-map interval ended 22.1 hours before this report. A 24-hour change estimate is unavailable. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
+7.2 km²
51 h ending 25 Jul 2026, 16:58 UTC
Daily net
Unavailable
No daily comparison available
Seven-day net
+12 km²
169.7 h comparison
Largest changes in the latest measured interval
Near Kharkiv
4.7 km² changed · RF-held gained 4.7 / lost 0.0 km²
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 #752: Zaporizhzhia area

Geospatial Analysis

10 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 10 places with coordinates
Geocoded places in report 752
PlaceCountryLatitude, longitudeCopy
ChernihivUA51.4982, 31.28935
ZaporizhzhiaUA47.83928419999999, 35.13870970000001
KharkivUA50.00201269999999, 36.3073994
PokrovskUA48.282193, 37.1847804
SlovianskUA48.8532, 37.6053
PoltavaUA49.58826699999999, 34.551417
TyumenRU57.1553394, 65.5618636
ChornomorskUA46.2952236, 30.6480855
Kryvyi RihUA47.910483, 33.391783
UralsRU60.2784931, 59.1619065

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.