UAF Strikes Omsk Refinery and Leningrad Rocket Brigade; RF Mass Strike Kills 15 in Kyiv
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 41.4 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 Ukrainian Armed Forces (UAF) executed a historic deep-strike campaign over the last 24 hours, targeting critical Russian energy and military infrastructure at ranges exceeding 2,500 km. Modified FP-1 drones struck the Omsk Oil Refinery in Siberia, causing massive fires and forcing airport closures, while separate strikes degraded the 26th Rocket Brigade base in Leningrad Oblast. These operations demonstrate an expanded UAF strike envelope capable of disrupting strategic fuel production and Iskander missile logistics deep within the Russian Federation.
In response, the Russian Federation (RF) launched a complex saturation attack on Ukraine, combining hypersonic (Zircon), ballistic (Iskander-M), cruise (Kh-101/Kalibr), and massed UAVs. While UAF air defense intercepted 86% of incoming targets, ballistic missiles penetrated defenses, striking residential and industrial areas in Kyiv and Kyiv Oblast. The death toll in Kyiv has risen to 15, with significant structural damage reported in the Podilskyi district and secondary detonation risks in Vyshneve. Ground operations remain largely static, with RF forces maintaining high-tempo but unsuccessful assaults in the Pokrovsk and Kostiantynivka sectors, accompanied by intensified information operations claiming territorial gains.
Operational Updates
-
Eastern Sector (Donetsk / Kharkiv):
- Kostiantynivka: RF continues to amplify IO narratives claiming full control of the city, releasing coerced footage of captured UAF personnel from the 25th Air Assault and 156th Mechanized Brigades. Ground truth confirms the frontline remains contested with no verified RF breakthrough; UAF continues to repel localized assaults.
- Kharkiv Oblast: RF systematic targeting of fuel infrastructure continues, with confirmed destruction of at least two gas stations in and near Kharkiv City. Over the past week, RF strikes have killed 14 civilians and injured 143 across 109 settlements using KABs, Geran-2, and Molniya drones.
- Pokrovsk / Lyman: RF maintains high-pressure assaults (22+ daily in Pokrovsk axis). UAF General Staff reports repelling multiple assaults near Novopavlivka, Shevchenko, and Kotlyne. RF claims of advances near Dobropillia remain unverified.
-
Southern Sector (Zaporizhzhia / Kherson):
- Zaporizhzhia: RF milbloggers claim Shahed-type drones struck a UAF POL storage facility near the city; visual confirmation is pending. Active RF UAV threats continue to target the oblast from the south.
- Kherson: No significant change in frontline geometry. RF continues KAB strikes on the right bank.
-
Northern Sector (Sumy / Chernihiv):
- Sumy: RF UAVs actively target the oblast from the southeast. Sumy OVA continues to warn civilians against visiting gas stations due to systematic RF drone campaigns against fuel nodes.
Deep Strikes & Air Defense
-
UAF Strikes on RF/Occupied Rear:
- Omsk Oblast: UAF modified FP-1 drones struck the ELU-AVT-11 unit at the Omsk Oil Refinery (~3,000 km range). Visuals confirm massive hydrocarbon fires, emergency pressure venting, and flight restrictions at Omsk airport. RF claims of successful interception are contradicted by open-source imagery.
- Leningrad Oblast: A UAF drone struck the permanent deployment base of the RF 26th Rocket Brigade (Iskander systems, unit 54006) in Luga, causing structural damage to base buildings and nearby residential structures.
- Sea of Azov / Crimea: UAF drones (FP-2, Chaklun-V, RAM-2) struck two RF shadow fleet tankers (7,000 tons each) en route to Crimea, a Kerch oil depot, a Nebo-U radar, and S-400 launchers in occupied Crimea and Bryansk Oblast.
- Belgorod Oblast: A Ukrainian drone struck a passenger bus on the Nikolskoye-Tavrovo road, wounding six people, including two children.
-
RF Strikes on Ukraine:
- Kyiv / Kyiv Oblast: Overnight mass strike involved 419 targets (6 Zircon, 23 Iskander-M, 33 Kh-101, 6 Kalibr, 351 UAVs). UAF AD intercepted 363 targets. Penetrating ballistic missiles struck a 25-story residential building in Podilskyi district (Kyiv) and logistics facilities in Vyshneve. Casualties: 15 dead, 56 injured. Secondary detonation risks in Vyshneve forced evacuation of >500 residents.
- Nationwide: Mass power outages reported in several oblasts due to combined RF shelling and severe weather.
SAR Intelligence (Satellite Data)
- High Priority:
- AB Pribylovo / 549th Base Air Group: SAR anomaly detection identifies critical activity scores (8.25) at these Leningrad Oblast air bases, significantly deviating from historical baselines. This correlates with reported UAF strikes in the region and potential RF dispersal or heightened alert postures.
- Omsk Oil Refinery: While not explicitly scored in the provided SAR snippet, visual confirmation of fires and infrastructure damage is HIGH confidence from optical sources.
- Analysis: The elevated SAR activity at AB Pribylovo and 549th Base Air Group suggests operational friction or reactive posturing in the Leningrad sector following the UAF strike on the 26th Rocket Brigade. No significant SAR changes were detected at major frontline airbases in the south, indicating baseline operational tempo there.
Equipment & Losses
- RF Equipment: Confirmed destruction of an RF Buk-M3 SAM system and two command posts by UAF combined arms elements (Lasar’s Group, Air Force, 151st OMBr). Two RF shadow fleet tankers struck in the Sea of Azov. S-400 launcher reportedly destroyed in Bryansk Oblast.
- RF Infrastructure: Severe damage to Omsk Oil Refinery (ELU-AVT-11 unit). Damage to 26th Rocket Brigade base in Luga. Fires at Kerch port and Simferopol substation in occupied Crimea.
- UAF/Civilian Impact: 15 civilian deaths in Kyiv. Destruction of residential infrastructure in Podilskyi district. Damage to gas stations in Kharkiv Oblast.
Confidence Check
- HIGH: UAF strikes on Omsk Refinery and Luga Rocket Brigade; RF mass strike on Kyiv causing 15 deaths; RF IO regarding Kostiantynivka is fabricated/coerced.
- MEDIUM: Extent of damage to Crimean energy grid (full blackout reported); effectiveness of RF interceptor drones against UAF "Baba Yaga"; specific tonnage of fuel lost in Sea of Azov tanker strikes.
- LOW: RF claims of Su-57 interceptors over Omsk; RF claims of full control over Kostiantynivka; WSJ reports on complete depletion of Patriot missiles (assessed as potential IO exploitation of known shortages).
The Bottom Line
UAF has successfully demonstrated the ability to strike strategic Russian energy and military assets at extreme ranges (>2,500 km), imposing systemic logistical costs and forcing RF to divert air defense resources to the deep rear. RF retaliated with a high-volume mixed strike package that exploited ballistic missile vulnerabilities to inflict significant civilian casualties in Kyiv. Monitor the operational status of the Omsk Refinery and the Crimean energy grid for long-term disruption effects. Watch for RF escalation in IO narratives regarding "Western direct involvement" following reports of US intelligence support for deep 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.
Against the previous report from 05 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 41.4 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.
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
14 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 14 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Omsk Oil Refinery | RU | 54.9913545, 73.3645204 | |
| Luga | RU | 58.73774839999999, 29.8496614 | |
| Kyiv | UA | 0, 0 | |
| Vyshneve | UA | 50.3919, 30.368267 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Kostiantynivka | UA | 48.52394289999999, 37.7075811 | |
| Kharkiv City | UA | 50.00201269999999, 36.3073994 | |
| Zaporizhzhia | UA | 47.83928419999999, 35.13870970000001 | |
| Sea of Azov | UA | 0, 0 | |
| Crimea | UA | 45.3453029, 34.4997274 | |
| Bryansk Oblast | RU | 0, 0 | |
| AB Pribylovo | RU | 60.425671, 28.6753152 | |
| 549th Base Air Group | RU | 0, 0 | |
| Sumy | UA | 50.9077, 34.7981 |
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.
