UAF Confirms Balaklava TPP Strike and Omsk Refinery Hit; RF Intensifies Kharkiv KAB Campaign
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.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
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 Ukrainian Armed Forces’ (UAF) confirmation of successful deep strikes against two critical Russian Federation (RF) strategic nodes: the Balaklava Thermal Power Plant (TPP) in occupied Crimea and the Omsk oil refinery in Bashkortostan, located 2,884 km from the launch site. President Zelenskyy officially confirmed these actions, marking a sustained degradation of RF energy infrastructure and rear-area logistics. The strike on Balaklava TPP has resulted in confirmed widespread blackouts across northwestern and eastern Crimea, corroborated by RF utility provider "Krymenergo."
Concurrently, RF forces intensified their aerospace campaign against civilian infrastructure in mainland Ukraine, particularly in Kharkiv (Kharkiv Oblast), where repeated KAB (guided aerial bomb) strikes have caused mounting civilian casualties (updated to 8 injured). On the ground, the frontline remains largely static with high-tempo RF assaults continuing in the Pokrovsk and Kostiantynivka directions, though no operational breakthroughs were achieved. Diplomatic momentum continues with the signing of a strategic industrial partnership ("Drone Deal") between Ukraine and the EU.
Operational Updates
- Eastern Sector (Donetsk): RF maintains high-tempo assaults in the Pokrovsk direction, with the UAF General Staff reporting 17 repelled attacks in this sector alone over the past 24 hours. In the Kostiantynivka sector, RF launched 17 assaults towards Illiniivka, Ivanopil, and Kucheriv Yar. RF milbloggers claim tactical advances near Novy Donbas, but geospatial verification remains pending. The 33rd Separate Assault Regiment continues to employ AI-assisted Unmanned Ground Vehicles (UGVs) in coordination with FPV drones.
- Southern Sector (Zaporizhzhia/Kherson/Odesa): RF conducted KAB strikes on Zaporizhzhia Oblast, hitting critical infrastructure and causing 1 death and 2 injuries. In Kherson Oblast, RF claimed a FAB-3000 strike destroyed a UAF 414th Brigade field HQ near Karabelka, alleging ~60 casualties; this claim remains unconfirmed and is assessed as likely information operations. UAF Special Operations Forces (SSO) confirmed responsibility for the Balaklava TPP strike, noting coordination with local resistance.
- Northern Sector (Kharkiv/Sumy): RF escalated KAB strikes on Kharkiv city (Kyivskyi district), resulting in 8 total civilian injuries and damage to administrative and residential buildings. In Sumy Oblast, UAF Air Force tracked multiple reactive UAVs approaching from the north/northeast. The UAF 47th Separate Mechanized Brigade "Magura" reported intercepting a high-speed "reactive Shahed" UAV, claiming 26 intercepts in 5 hours.
- Kursk Direction: No significant change in ground contact lines. RF "Akhmat" units are reportedly stalled near Bachevsk due to dense UAF mining and drone surveillance.
Deep Strikes & Air Defense
- UAF Strategic Interdiction: President Zelenskyy confirmed a UAF ballistic missile strike on the Omsk oil refinery (Bashkortostan), bringing the total number of disabled RF refineries to at least 15. UAF SSO confirmed the strike on Balaklava TPP (Sevastopol, Crimea), causing widespread blackouts. UAF Naval Forces expanded Operation "MoLoChKa" into the Black Sea, claiming damage to 20 RF shadow fleet vessels overnight (17 oil tankers, 2 gas carriers, 1 tugboat).
- RF Aerospace Campaign: RF launched a coordinated night strike of 122 UAVs and 2 Kh-59/69 cruise missiles. UAF Air Force reported 101 targets shot down or suppressed, with 18 impacting 19 locations. Continued KAB strikes targeted Kharkiv, Zaporizhzhia, and Dnipropetrovsk Oblasts. RF MoD claimed strikes on port infrastructure in Odesa and Chornomorsk, targeting fuel infrastructure and 4 ships.
- Air Defense: UAF Air Force actively tracked reactive UAVs towards Sumy, Chernihiv, and Kyiv. RF air defense engaged a massive UAV swarm over the Moscow region (340 UAVs in 24h). An air raid alert was triggered in Sevastopol, indicating ongoing UAF asymmetric pressure in Crimea.
SAR Intelligence (Satellite Data)
- High Priority: SAR anomaly detection identified critical activity deviations at several locations:
- FSB Department for the Bryansk Oblast: Score 3.25 (Critical Anomaly). Indicates significant logistical reshuffling or unit movement.
- 82nd Separate Special Purpose Radio-Technical Brigade (Moscow Military District): Score 3.75 (Critical Anomaly). Suggests reactive logistical adjustments or dispersal.
- 20th Special Purpose Communications Center (Spetssvyaz): Score 3.69 (Critical Anomaly). Warrants monitoring for aviation asset movements or dispersal.
- Analysis: The elevated scores at the FSB Department for the Bryansk Oblast and 82nd Separate Special Purpose Radio-Technical Brigade suggest reactive logistical adjustments in response to UAF deep strikes and ongoing rear-area security concerns. The confirmed destruction of the Balaklava TPP aligns with operational reporting of energy interdiction in Crimea.
Equipment & Losses
- RF Losses: UAF SSO confirmed damage to Balaklava TPP. UAF Naval Forces claimed damage/destruction of 20 RF shadow fleet vessels in the Black Sea. UAF 427th "Rarog" Brigade claimed destruction of an RF Mi-28 helicopter near Vyazove using a $400 Shrike 10 drone. RF sources confirmed crew casualties on the FSB patrol ship Izumrud in Gelendzhik.
- UAF Losses: Confirmed civilian casualties in Kharkiv (8 injured), Zaporizhzhia (1 killed, 2 injured), and Chernihiv (1 killed). Infrastructure damage reported at Chornomorsk and Yuzhny port terminals.
Confidence Check
- Balaklava TPP Strike: HIGH (Confirmed by UAF SSO and RF "Krymenergo" blackout reports).
- Omsk Refinery Strike: HIGH (Confirmed by President Zelenskyy; satellite verification pending).
- Kharkiv Civilian Casualties: HIGH (Confirmed by Kharkiv OVA head Oleg Syniehubov).
- Black Sea Maritime Strikes: MEDIUM (Claimed by UAF SBS; independent AIS/satellite verification required).
- Karabelka HQ Strike: LOW (RF claim only; no independent confirmation of UAF command disruption).
The Bottom Line
The conflict trajectory is defined by UAF’s successful expansion of asymmetric strikes to deep RF rear areas (Omsk) and critical Crimean energy infrastructure (Balaklava TPP), exacerbating RF logistical and domestic fuel crises. RF continues to rely on KABs and ballistic missiles to target Ukrainian urban centers, particularly Kharkiv, while facing systemic domestic fuel shortages. In the next 24 hours, monitor:
- Crimean Power Grid: Restoration efforts in Sevastopol and northern Crimea following the Balaklava TPP damage.
- Omsk Refinery Impact: Satellite assessment of damage extent and operational halt duration at the Omsk facility.
- RF Ballistic Strike Aftermath: Damage assessment in Kharkiv and Zaporizhzhia following the latest KAB and UAV waves.
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 14 Jul 2026, 15:08 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 26.1 hours before this report. The daily change covers 24.7 h. 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
4 visualsGeospatial 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
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Balaklava Thermal Power Plant | Ukraine | 0, 0 | |
| Omsk Oil Refinery | Russia | 0, 0 | |
| Kharkiv | Ukraine | 50.00201269999999, 36.3073994 | |
| Pokrovsk | Ukraine | 48.282193, 37.1847804 | |
| Kostiantynivka | Ukraine | 48.52394289999999, 37.7075811 | |
| Zaporizhzhia | Ukraine | 47.83928419999999, 35.13870970000001 | |
| Karabelka | Ukraine | 0, 0 | |
| Sumy | Ukraine | 50.9077, 34.7981 | |
| Chornomorsk | Ukraine | 46.2952236, 30.6480855 | |
| FSB Department Bryansk Oblast | Russia | 0, 0 | |
| 82nd Separate Special Purpose Radio-Technical Brigade | Russia | 0, 0 | |
| 20th Special Purpose Communications Center | Russia | 0, 0 |
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.
