Daily intelligence

UAF Confirms Strikes on Yaroslavl Refinery and Kerch Naval Assets; RF Escalates Infrastructure Targeting in Kherson and Pavlohrad

Published Intelligence Summary & Geospatial Analysis
Report number
763

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 26.3 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 confirmed Ukrainian Armed Forces (UAF) deep strike campaign against Russian Federation (RF) energy and maritime assets. The Security Service of Ukraine (SBU) and Defense Forces successfully targeted the Slavneft-YANOS oil refinery in Yaroslavl Oblast (over 700 km from the border) and FSB Coast Guard patrol boats in Kerch, resulting in confirmed fires and infrastructure damage. This action underscores the continued degradation of RF domestic fuel logistics, which are already strained by a reported 27% reduction in refining capacity.

Concurrently, RF forces intensified their aerospace campaign against Ukrainian critical infrastructure, causing a city-wide blackout in Kherson and civilian casualties in Pavlohrad (Dnipropetrovsk Oblast). On the ground, RF milbloggers continue to claim unverified territorial advances in Zaporizhzhia and Sumy oblasts, while UAF maintains defensive pressure and conducts complex tactical extractions. The juxtaposition of successful UAF deep strikes against persistent RF frontline attrition highlights the asymmetric nature of the current conflict phase.

Operational Updates

  • Northern Sector (Sumy/Kharkiv): RF forces conducted KAB strikes on Sumy city, damaging residential infrastructure and injuring at least two civilians. Pro-Russian sources claim unverified advances near Ryzhivka (Sumy Oblast) and Olkhovatka (Kharkiv Oblast), though independent geospatial verification is lacking. UAF Air Force tracked incoming UAVs toward Okhtyrka and Lozova.
  • Eastern Sector (Donetsk/Kharkiv): High-tempo attritional combat continues. RF forces utilized heavy FAB-3000 glide bombs against crossing points in the Kupiansk direction. UAF repelled assaults in the Pokrovsk and Lyman directions. RF milbloggers claim advances near Pavlovka (Zaporizhzhia Oblast), approaching the Zaporizhzhia-Orikhiv highway, but these claims remain unconfirmed.
  • Southern Sector (Zaporizhzhia/Kherson): RF strikes caused a total power outage in Kherson city after damaging critical energy infrastructure. In Zaporizhzhia city, visual evidence confirmed damage to two high-rise buildings and a dormitory. RF forces employed heavy-lift hexacopters ("Mangas") to drop TM-62 anti-tank mines on UAF positions in the Zaporizhzhia sector.
  • Central Sector (Dnipropetrovsk/Kyiv): An RF strike on an industrial facility in Pavlohrad (Dnipropetrovsk Oblast) killed at least two civilians and injured seven. In Kyiv Oblast, logistical disruptions persist following previous strikes on distribution hubs in Brovary. Partial power outages were reported in Lviv due to emergency grid shutdowns, with RF sources attributing it to heat rather than kinetic action.

Deep Strikes & Air Defense

  • UAF Deep Strikes:
    • Yaroslavl Oblast: Confirmed strikes on the Slavneft-YANOS refinery. Visuals show massive smoke plumes; reports indicate fires in four RVS-2000 crude oil tanks and damage to processing units.
    • Kerch (Occupied Crimea): UAF drones reportedly damaged two FSB Coast Guard Project 10410 patrol boats, "Balaclava" and "Kerch," in port. No visual BDA provided.
    • Leipzig/Halle Airport (Germany): German Interior Minister labeled the recent drone discovery a "hybrid attack scenario," confirming the strategic nature of the incident.
  • RF Aerospace Campaign:
    • Infrastructure Targeting: Strikes on Kherson energy infrastructure caused a city-wide blackout. Strikes in Pavlohrad resulted in civilian casualties.
    • Maritime Interdiction: RF MoD claims drone strikes on cargo ships, including the MERA QUEEN, in the Black Sea. Independent verification is lacking; visual evidence relies on unverified thermal footage.
    • Air Defense Activity: UAF Air Force issued multiple warnings for incoming KABs and UAVs targeting Zaporizhzhia, Sumy, Donetsk, and Chornomorsk.

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: Fires and damage confirmed at Slavneft-YANOS refinery (Yaroslavl). Damage to FSB patrol boats in Kerch (Unconfirmed visual BDA).
    • Personnel: Burials confirmed for Major-General Valery Plohotnyuk and Daniil Peredriy, casualties from the August 1 Moscow restaurant explosion.
  • UAF Losses/Damage:
    • Infrastructure: Critical energy infrastructure damaged in Kherson (city-wide blackout). Industrial facility struck in Pavlohrad. Residential buildings damaged in Zaporizhzhia and Sumy.
    • Personnel: At least 2 dead and 7 injured in Pavlohrad. At least 2 injured in Sumy.

Confidence Check

  • UAF Strikes on Yaroslavl/Kerch: HIGH (Confirmed by SBU, GUR, and visual evidence of smoke/fire).
  • Kherson/Pavlohrad Infrastructure Damage: HIGH (Confirmed by local authorities and utility reports).
  • RF Territorial Claims (Sumy/Zaporizhzhia): LOW (Claimed by RF milbloggers; lacks independent geospatial verification).
  • RF Maritime Strike Claims (MERA QUEEN): LOW/MEDIUM (Claimed by RF MoD; lacks independent AIS or satellite verification).
  • Lviv Power Outage Cause: MEDIUM (Utility cites emergency shutdown; RF cites heat/sabotage narrative).

The Bottom Line

UAF has demonstrated sustained capability to degrade RF strategic energy and maritime assets deep within Russian territory, exacerbating existing domestic fuel shortages. In response, RF forces continue to target Ukrainian critical infrastructure to induce humanitarian and logistical strain, particularly in Kherson and Dnipropetrovsk oblasts. In the next 24 hours, monitor:

  1. Refinery BDA: Satellite imagery assessment of damage to Slavneft-YANOS and its impact on regional fuel supplies.
  2. Grid Stability: Restoration efforts in Kherson and monitoring of Lviv grid stability amid high temperatures.
  3. Ground Truth: Geospatial verification of RF claims regarding advances near Pavlovka (Zaporizhzhia) and Ryzhivka (Sumy).

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

Against the previous report from 05 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 26.3 hours before this report. The daily change covers 23.3 h. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
+5.7 km²
23 h ending 05 Aug 2026, 12:47 UTC
Daily net
+5.7 km²
23.3 h comparison
Seven-day net
+28 km²
160.1 h comparison
Largest changes in the latest measured interval
Near Pokrovsk
5.7 km² changed · RF-held gained 5.7 / 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 #763: Pavlovka 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 763
PlaceCountryLatitude, longitudeCopy
YaroslavlRU57.62607440000001, 39.8844708
KerchUA45.357314, 36.468293
KhersonUA46.635417, 32.616867
PavlohradUA48.5294478, 35.9032574
SumyUA50.9077, 34.7981
ZaporizhzhiaUA47.83928419999999, 35.13870970000001
RyzhivkaUA51.25142719999999, 34.2470576
OlkhovatkaUA50.1825804, 37.5172647
PavlovkaUA47.7878439, 36.4019031
LvivUA49.839683, 24.029717

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.