RF Missile Salvo Decimates Kyiv Logistics Hubs; Putin Formalizes Command Restructuring
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 25.6 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 successful penetration of Russian Federation (RF) ballistic and hypersonic missiles into Kyiv and Kyiv Oblast, resulting in the destruction of major commercial logistics nodes, including the Rozetka distribution center in Brovary and the Liqui Moly warehouse. Unlike previous days where UAVs were the primary threat, this strike utilized Iskander-M and claimed Zircon missiles, against which Ukrainian Air Defense failed to intercept any of the 28 incoming ballistic/cruise assets. This represents a critical degradation of central Ukraine’s supply chain resilience and highlights a severe vulnerability in anti-ballistic defense coverage.
Concurrently, President Vladimir Putin formalized a major restructuring of the Russian Ministry of Defence, appointing new commanders for Groupings "Center" and "East," a Deputy Minister for rear logistics, and establishing a dedicated command for Unmanned Systems troops. This consolidation signals a strategic shift toward streamlining logistics and institutionalizing drone warfare to sustain offensive tempo. On the ground, RF forces continue high-tempo attritional assaults, with unverified claims of advances in Kharkiv and Sumy oblasts, while UAF deep strikes disrupted RF grain exports via the Azov-Don Canal.
Operational Updates
- Northern Sector (Kyiv/Kyiv Oblast): RF forces executed a coordinated overnight strike (00:20–01:30 UTC) using ballistic and hypersonic missiles. Confirmed impacts destroyed the Rozetka e-commerce hub in Brovary and the Liqui Moly warehouse, causing massive fires and halting production/distribution. A strike on Kvitneve railway station killed logistics workers. Kyiv Oblast declared August 6 a Day of Mourning. Casualties in Kyiv city are confirmed at 1 dead and 24–26 injured.
- Eastern Sector (Donetsk/Kharkiv): High-intensity combat continues. UAF General Staff reported repelling 45 RF assaults in the Pokrovsk direction and 28 in the Lyman direction. RF sources claim territorial advances near Baksheevka and Ustynivka (Kharkiv Oblast) and the capture of Ryzhivka (Sumy Oblast), though independent geospatial verification is pending. RF KABs and drones struck civilian infrastructure in Kharkiv city, injuring 8.
- Southern Sector (Zaporizhzhia/Odesa/Mykolaiv): RF MoD claims "Geran-4" drones struck five cargo ships near Mykolaiv and in the Black Sea, and destroyed two UAF unmanned surface vessels (USVs) southeast of Ochakiv. Independent battle damage assessment is lacking. In Zaporizhzhia Oblast, RF conducted over 1,000 strikes in 24 hours, heavily utilizing FPV drones. UAF drone units continue targeting RF logistics in the Zaporizhzhia direction.
- Deep Rear (Russia): An assassination attempt via car bomb critically injured Vladimir Tkachuk, director of the "Uraldronezavod" (producer of "Upyr" FPV drones), in Sverdlovsk Oblast. This marks the second such incident targeting RF drone industry leadership in a week.
Deep Strikes & Air Defense
- RF Aerospace Campaign:
- Kyiv/Brovary: Saturation attack involving 24 Iskander/S-400 ballistic missiles, 4 Zircon/Onyx, and 115 UAVs. UAF intercepted 98 UAVs but zero missiles. Impacts confirmed at 26 locations, primarily logistics and industrial sites.
- Maritime Interdiction: RF MoD claims strikes on 5 cargo ships and 2 USVs in the Black Sea/Mykolaiv sector. Fesco had previously suspended Black Sea bookings, corroborating the strategic intent to choke maritime exports.
- Other Targets: Drone strikes hit an enterprise in Odesa district (1 dead, 8 injured) and caused a chemical spill at an industrial park in Domodedovo (Moscow Oblast).
- UAF Deep Strikes:
- Logistics Disruption: UAF strikes on the Azov-Don Canal are causing severe bottlenecks in Russian grain exports, threatening a 6.5 million ton reduction in H2 exports.
- Sabotage Attempt: An explosive-laden drone was discovered near a cargo plane at Leipzig/Halle Airport (Germany). The device failed to detonate, but a secondary collision occurred during a go-around. Investigation ongoing.
- Air Defense Development: UAF reports a threefold drop in partner anti-ballistic missile supplies in H1 2026 compared to H1 2025. Negotiations are underway for localized Patriot component manufacturing in Europe.
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:
- Personnel: Vladimir Tkachuk, director of "Uraldronezavod," critically injured in car bomb explosion; driver killed.
- Infrastructure: Wildberries sorting center in Aleksin (Tula Oblast) damaged by UAV strike; deliveries rerouted. Industrial fire in Ufa confirmed due to UAV debris.
- UAF Losses/Damage:
- Infrastructure: Destruction of Rozetka and Liqui Moly warehouses in Kyiv Oblast. Damage to Kvitneve railway station. Strike on civilian enterprise in Kharkiv (Novobavarskyi district).
- Personnel: 1 dead, 24–26 injured in Kyiv city; 1 dead, 8 injured in Odesa district; 8 injured in Kharkiv.
- Maritime: RF claims destruction of 2 USVs and damage to 5 cargo ships (Unconfirmed).
Confidence Check
- Kyiv Logistics Destruction: HIGH (Confirmed by multiple Ukrainian sources and RF milbloggers).
- Missile Penetration Rate: HIGH (UAF Air Force confirmed 0 interceptions of 28 ballistic/cruise missiles).
- RF Command Restructuring: HIGH (Officially announced by TASS and Kremlin).
- RF Maritime Strike Claims: LOW (Claimed by RF MoD; lacks independent AIS or satellite verification).
- RF Territorial Advances (Kharkiv/Sumy): LOW/MEDIUM (Claimed by RF sources; lacks independent geospatial verification).
- Tkachuk Assassination Attempt: HIGH (Confirmed by multiple RF state and independent sources).
The Bottom Line
RF forces have demonstrated a renewed capability to penetrate Ukrainian air defense with high-value ballistic and hypersonic missiles, inflicting disproportionate damage on critical civilian logistics infrastructure in Kyiv Oblast. The formalization of RF command structures, particularly the creation of a dedicated Unmanned Systems troop branch, indicates a long-term adaptation to sustain drone-intensive warfare. In the next 24 hours, monitor:
- Supply Chain Impact: Assessment of the operational disruption caused by the loss of the Rozetka and Liqui Moly hubs.
- Maritime BDA: Satellite imagery verification of RF claims regarding destroyed cargo ships in the Black Sea.
- Ground Truth: Geospatial confirmation of RF claims of advances in Sumy (Ryzhivka) and Kharkiv (Baksheevka) oblasts.
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 04 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.
The latest control-map interval ended 25.6 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
15 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 15 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Kyiv | UA | 0, 0 | |
| Brovary | UA | 50.511083, 30.7909 | |
| Kvitneve | UA | 50.5334605, 30.8446582 | |
| Kharkiv | UA | 50.00201269999999, 36.3073994 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Lyman | UA | 48.9897585, 37.8049964 | |
| Baksheevka | UA | 0, 0 | |
| Ryzhivka | UA | 51.25142719999999, 34.2470576 | |
| Mykolaiv | UA | 46.9660801, 32.003246 | |
| Ochakiv | UA | 46.61876669999999, 31.5387942 | |
| Zaporizhzhia | UA | 47.83928419999999, 35.13870970000001 | |
| Azov-Don Canal | RU | 0, 0 | |
| Sverdlovsk | RU | 56.8430993, 60.64540859999999 | |
| Aleksin | RU | 54.5031038, 37.0671916 | |
| Ufa | RU | 54.73479099999999, 55.9578555 |
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.
