RF Aerospace Saturation Strikes Kyiv and Odesa; UAF Deep Strikes Degrade Kerch Ferry Capacity
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 23.9 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 execution of a massive, multi-vector Russian Federation (RF) aerospace saturation campaign targeting Kyiv and Odesa. RF forces deployed approximately 166 aerial assets, including ballistic missiles (Iskander-M, Zirkon) and anti-ship missiles (Onyx), resulting in confirmed impacts on civilian and dual-use infrastructure in Kyiv Oblast and maritime targets near Odesa. While Ukrainian Air Defense intercepted 76% of incoming threats, debris and penetrators caused casualties and structural damage, including at the UKRTAC defense industrial facility and Lukianivska metro station.
Concurrently, Ukrainian Armed Forces (UAF) asymmetric operations achieved a strategic logistical degradation in the south. The UAF Unmanned Systems Forces Commander claimed a 75% reduction in Kerch Strait ferry capacity following sustained strikes on all five active ferries. In the deep rear, satellite imagery confirms massive fires at the Wildberries logistics hub in Elektrostal (Moscow Oblast), validating earlier UAF strikes and highlighting continued vulnerability in RF commercial supply chains. Ground operations remain static with high-tempo attritional assaults in the Pokrovsk and Sloviansk directions.
Operational Updates
- Eastern Sector (Donetsk): RF forces maintained high-intensity ground assaults, repelling 60 attacks across the front per UAF General Staff data. The highest concentrations occurred in Pokrovsk (15 attacks) and Sloviansk (14 attacks). RF MoD claims capture of Volne (Dnipropetrovsk Oblast) to secure flanks for an advance on Pokrovske, though this lacks independent geospatial verification. UAF units, including the 49th Separate Assault Battalion "Karpat Sich", explicitly refuted RF claims of losing control in Kostiantynivka.
- Northern Sector (Kharkiv/Sumy): RF aerospace activity intensified against rear areas. Strikes hit Izium three times with KABs, MLRS, and drones, damaging residential buildings and power grids. In Kharkiv Oblast, RF struck 24 settlements using 17 KABs, killing 2 and injuring 20. A strike on a Nova Poshta sorting terminal in Kharkiv Oblast killed 3 and injured 20. In Sumy Oblast, RF struck a rehabilitation center for children and persons with disabilities, causing significant fire damage.
- Southern Sector (Zaporizhzhia/Odesa/Kherson): The primary axis of RF aerospace escalation. Following overnight strikes, RF Tu-22M3 bombers launched ~8 Kh-22/32 missiles towards Odesa and Chornomorsk, supplemented by Black Sea-launched missiles. Visual evidence confirms at least two cargo ships burning near the Port of Odesa. In Zaporizhzhia, RF strikes destroyed multiple floors of an apartment building and damaged private sector infrastructure. A reported strike on a passenger train near Vilniansk injured one conductor.
- Central Rear (Kyiv): RF launched 166 aerial targets (41 missiles, 125 UAVs) against Kyiv. UAF Air Force reported intercepting 126 targets. Impacts were recorded in 20 locations, including the Amtel Properties logistics complex (two warehouses destroyed), UKRTAC military gear factory (confirmed destroyed), and Lukianivska square (metro station, cinema, and residential buildings damaged). Casualties in Kyiv city include 1 dead and 17 injured.
Deep Strikes & Air Defense
- UAF Deep Strikes:
- Kerch Strait: UAF Unmanned Systems Forces claim to have degraded Kerch ferry crossing capacity by 75% by targeting all five ferries (Lavrentiy, Panagia, Aysk, Maria, SKS-One) over two weeks.
- Energy/Logistics: SBU struck the RF shadow fleet tanker "Avero" in the Black Sea and three oil depots in Stavropol Krai (~600km from border), causing large-scale fires. Satellite imagery confirms a massive smoke plume over the Wildberries facility in Elektrostal (Moscow Oblast).
- RF Aerospace Campaign:
- Kyiv Axis: Utilized 10x Zirkon hypersonic missiles (Kursk), 25x Iskander-M/S-400 (Bryansk/Kursk), and 125 UAVs. UAF intercepted 17 ballistic/cruise missiles and 108 UAVs.
- Southern Axis: Launched Onyx anti-ship missiles from Crimea and Kh-22/32 from Tu-22M3 bombers against Odesa/Chornomorsk ports.
- Frontline/Rear: Sustained KAB strikes on Izium, Zaporizhzhia, and Kharkiv. RF MoD claims strikes on Shebelinka gas plant (Kharkiv) and Nova Poshta terminals.
- Air Defense: UAF Air Force actively tracked and engaged multi-vector threats. RF MoD claimed interception of 678 UAVs and destruction of 2 UAF unmanned boats, figures assessed as highly exaggerated.
SAR Intelligence (Satellite Data)
- High Priority:
- AB Pribylovo / 549th Base Air Group (60.46, 28.74): Score 7.42 (Critical Anomaly). Indicates significant logistical reshuffling or unit movement, likely reactive dispersal following deep strikes.
- 66th Guards Pontoon-Bridge Regiment (Moscow Military District): Score 6.22 (Critical Anomaly). Significant deviation from historical patterns requiring investigation.
- Wildberries Elektrostal: Optical/SAR confirmation of massive fire and smoke plume corroborates UAF strike BDA.
- Analysis: The elevated score at AB Pribylovo aligns with reported RF aviation activity and potential dispersal measures. The anomaly at the pontoon brigade may indicate equipment movement or storage changes unrelated to immediate frontline combat but warrants monitoring. No significant changes were detected at frontline logistics hubs, indicating stable baseline activity there.
Equipment & Losses
- RF Losses: UAF claims 75% degradation of Kerch ferry capacity. Shadow fleet tanker "Avero" struck. Oil depots in Stavropol Krai and Wildberries hub in Elektrostal damaged/destroyed. RF FPV drones destroyed one UAF self-propelled howitzer near Mala Rybytsia (Sumy Oblast).
- UAF Losses/Damage: UKRTAC factory and warehouses in Kyiv Oblast confirmed destroyed. Amtel Properties logistics center near Kyiv struck (two warehouses destroyed). Civilian casualties reported in Kyiv (1 dead, 17 injured), Kharkiv (3 dead, 20 injured at Nova Poshta), Izium (20 injured), and Odesa (1 dead, 12 injured).
Confidence Check
- Kyiv/Odesa Strike BDA: HIGH (Confirmed by DSNS, local authorities, and visual evidence).
- Wildberries/Elektrostal Fire: HIGH (Confirmed by satellite imagery and local sources).
- Kerch Ferry Degradation: MEDIUM (Claimed by UAF Unmanned Systems Commander; requires AIS/satellite verification of actual throughput).
- Volne Capture Claim: LOW (RF MoD claim only; lacks independent geospatial verification).
- UKRTAC Destruction: HIGH (Confirmed by company director and ASTRA).
The Bottom Line
The conflict trajectory is defined by RF's escalation of aerospace pressure against Ukrainian urban centers and defense industry (Kyiv) and maritime logistics (Odesa), while UAF continues to successfully interdict RF deep-rear logistics (Wildberries, Stavropol oil) and critical chokepoints (Kerch Strait). In the next 24 hours, monitor:
- Odesa Port Operations: Verification of damage to the burning cargo ships and assessment of operational impact on grain/military cargo flows.
- Kyiv DIB Impact: Assessment of the medium-term impact of the UKRTAC factory destruction on UAF individual protective equipment supply chains.
- Kerch Throughput: AIS tracking and satellite imagery to verify the actual status of the five targeted ferries and remaining RF logistics throughput.
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 18 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 23.9 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 |
|---|---|---|---|
| Kyiv | UA | 0, 0 | |
| Odesa | UA | 46.4845702, 30.7326047 | |
| Chornomorsk | UA | 46.2952236, 30.6480855 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Sloviansk | UA | 48.8532, 37.6053 | |
| Izium | UA | 49.2121445, 37.2665006 | |
| Kerch Strait | RU | 45.2414255, 36.529626 | |
| Elektrostal | RU | 55.7835532, 38.4551611 | |
| Volne | UA | 0, 0 | |
| Stavropol Krai | RU | 0, 0 | |
| AB Pribylovo | RU | 0, 0 | |
| Zaporizhzhia | UA | 47.83928419999999, 35.13870970000001 | |
| Vilniansk | UA | 47.94032259999999, 35.4328125 | |
| Sumy Oblast | UA | 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.
