UAF Deep Strikes Damage Perm and Ryazan Refineries; RF Claims Maritime Interdiction in Odesa
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 19.5 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
Analyst briefMachine-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 degradation of Russian Federation (RF) strategic energy infrastructure through coordinated Ukrainian Armed Forces (UAF) deep strikes. Visual evidence and official confirmations indicate successful impacts on the Lukoil-Permnefteorgsynthesis refinery in Perm Krai and the Ryazan Oil Refinery, compounding previous disruptions to RF fuel processing capabilities. These strikes demonstrate a sustained UAF capability to target critical industrial nodes over 1,000 km from the border, leveraging Western intelligence support for air defense mapping.
Concurrently, the RF intensified its aerospace campaign against Ukrainian maritime logistics, claiming strikes on multiple cargo vessels and port infrastructure in Odesa and Mykolaiv. While damage assessments remain pending, these actions align with the ongoing RF strategy to strangle Black Sea export corridors. Diplomatically, President Volodymyr Zelenskyy engaged in high-level talks with Polish Prime Minister Donald Tusk in Lublin, addressing recent bilateral tensions and securing continued infrastructure support, signaling a stabilization of key regional alliances despite internal political friction.
Operational Updates
- Eastern Sector (Donetsk/Kharkiv): Ground operations remain characterized by high-tempo attritional assaults with no independently verified territorial changes. RF milbloggers claim advances in Krasnyi Lyman and Druzhkivka (Donetsk Oblast), but independent RF sources dispute control of settlements like Nova Sitch (Sumy Oblast), indicating fragmented information operations. UAF units, including the SIGNUM battalion and 67th Mechanized Brigade, conducted effective FPV drone strikes against RF artillery and personnel in the Lyman and Novopole sectors. Weather conditions, including thunderstorms in Kharkiv (5.9 mm precip), continue to degrade optical reconnaissance and FPV effectiveness.
- Southern Sector (Zaporizhzhia/Mykolaiv/Odesa): RF MoD claimed strikes on a fuel tank in Odesa port and three dry cargo ships in Yuzhny port and at sea, alleging military cargo transport. UAF "Omega" special operations group reported intercepting Shahed and Heron drones targeting Odesa using donated FPV interceptors. In Zaporizhzhia Oblast, UAF GUR "Artan" special forces claimed the capture of four RF prisoners in Stepnohirsk. RF forces continue to adapt tactically, deploying "Nabat" drone detectors via civilian charity networks in the Kramatorsk direction.
- Northern Sector (Sumy/Chernihiv): RF aerospace activity persisted with UAVs tracked from Sumy towards Poltava and from Chernihiv towards Kyiv. No significant ground maneuvers were reported, though cross-border shelling continues. UAF Air Force maintained active tracking of multi-vector aerial threats, including jet-powered UAVs approaching from the Black Sea.
Deep Strikes & Air Defense
- UAF Deep Strikes:
- Perm Krai: UAF drones struck the Lukoil-Permnefteorgsynthesis refinery. Regional Governor Dmitry Makhonin confirmed the attack and interceptions, while OSINT sources allege damage to the AVT-5 primary distillation unit.
- Ryazan Oblast: Confirmed strikes on the Ryazan Oil Refinery and a Wildberries logistics hub in Tyushevo, causing massive fires and evacuations. RF authorities reported six hospitalized personnel.
- Other Targets: UAF General Staff claimed strikes on a Black Sea Fleet fast patrol boat base near Mezhdvodne (Crimea), a radar station in Bryansk Oblast, and a drone storage facility in Donetsk.
- RF Aerospace Campaign:
- Maritime Interdiction: RF MoD claimed strikes on port infrastructure and cargo vessels in Odesa and Mykolaiv. Visual evidence of specific vessel damage remains unconfirmed.
- Urban/Industrial Strikes: KABs targeted Pavlohrad (Dnipropetrovsk Oblast) and Zaporizhzhia, causing suburban fires. A jet-powered UAV was tracked towards Apostolove.
- Intercepts: UAF "Omega" group claimed interception of Shahed/Heron drones over Odesa. NGU Lasar's Group claimed a high-altitude intercept of a ZALA Z-20 drone at 6,400 meters.
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 fires at Perm and Ryazan refineries and Wildberries logistics hub. An unconfirmed fire occurred at an oil/chemical facility in Pyt-Yakh (Khanty-Mansi Autonomous Okrug).
- Personnel: Attempted assassination of Andrey Cherezov, head of "Russian Laboratory of Air Transport," in Tula; he was hospitalized in critical condition. A 9-year-old child died in Kerch from injuries sustained in a previous UAF strike.
- UAF Losses/Damage:
- Civilian Casualties: RF shelling in Rayhorodok (Donetsk Oblast) killed one woman and injured six, including a child. KAB strikes in Pavlohrad caused property damage.
- Internal Security: NPU detained three soldiers from the 425th OShP "Skelya" in Zaporizhzhia for involvement in a darknet weapons cache network.
Confidence Check
- Perm/Ryazan Refinery Strikes: HIGH (Confirmed by RF governors and visual evidence).
- RF Maritime Strike Claims (Odesa/Mykolaiv): MEDIUM (Claimed by RF MoD; independent BDA pending).
- RF Territorial Claims (Donetsk/Sumy): LOW (Contradicted by independent RF sources and lacking geospatial verification).
- Zelenskyy-Tusk Meeting: HIGH (Confirmed by official channels).
- Tula Assassination Attempt: MEDIUM (Reported by multiple RF sources; victim identity relies on secondary reports).
The Bottom Line
UAF deep-strike campaigns continue to successfully degrade RF strategic energy and logistics infrastructure, forcing costly repairs and operational halts far behind the front lines. RF responses remain focused on maritime interdiction and urban saturation, though claims of territorial gains are increasingly contested even within Russian information spaces. In the next 24 hours, monitor:
- Refinery BDA: Satellite assessment of damage to the AVT-5 unit in Perm and operational status of the Ryazan refinery.
- Maritime Logistics: Verification of damage to cargo vessels in Odesa/Yuzhny ports and impact on grain export flows.
- Diplomatic Outcomes: Official readouts from the Zelenskyy-Tusk meeting regarding security cooperation and resolution of recent bilateral tensions.
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.
Against the previous report from 28 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.
The latest control-map interval ended 19.5 hours before this report. These map dates may differ from the reporting period and do not establish when territorial changes occurred.
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 visualsGeospatial Analysis
16 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 16 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Perm | Russia | 58.00916830000001, 56.22696740000001 | |
| Ryazan | Russia | 54.6095418, 39.7125857 | |
| Odesa | Ukraine | 46.4845702, 30.7326047 | |
| Mykolaiv | Ukraine | 46.9660801, 32.003246 | |
| Yuzhny | Ukraine | 46.6240213, 31.1000648 | |
| Lublin | Poland | 51.2509458, 22.5747275 | |
| Krasnyi Lyman | Russia | 0, 0 | |
| Druzhkivka | Russia | 48.6161912, 37.52721870000001 | |
| Nova Sitch | Russia | 0, 0 | |
| Stepnohirsk | Russia | 47.5869326, 35.358148 | |
| Pavlohrad | Ukraine | 48.5294478, 35.9032574 | |
| Mezhdvodne | Russia | 0, 0 | |
| Bryansk | Russia | 53.2635306, 34.41611 | |
| Tula | Russia | 54.1921956, 37.6164115 | |
| Kerch | Russia | 45.357314, 36.468293 | |
| Rayhorodok | Ukraine | 48.9001251, 37.7248512 |
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.
