UAF Deep Strikes Damage Wildberries Logistics Hubs in Moscow and Tambov Oblasts; RF Intensifies Aerospace Campaign Against Southern Ports
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 50.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 confirmed damage to major Russian Federation (RF) logistics infrastructure deep in the rear. Ukrainian Armed Forces (UAF) drone strikes heavily damaged Wildberries distribution centers in Elektrostal (Moscow Oblast) and Kotovsk (Tambov Oblast), with satellite imagery confirming massive fires at the Elektrostal facility. RF authorities acknowledged casualties, reporting 7 killed and up to 25 injured in Kotovsk, and 24 injured in Elektrostal. These strikes underscore the vulnerability of RF’s dual-use commercial logistics networks to sustained UAF asymmetric interdiction.
Concurrently, RF aerospace forces executed a high-intensity saturation campaign against southern Ukraine, primarily targeting Odesa and Chornomorsk ports. The attack involved a mix of ballistic missiles (Iskander-M), anti-ship missiles (Onyx), cruise missiles, and a large UAV swarm. While UAF air defense intercepted 70 of 97 incoming targets, impacts were recorded at 19 locations, causing civilian casualties and damaging port infrastructure. On the ground, the frontline remains largely static, with RF forces maintaining high-tempo assaults in the Pokrovsk and Sloviansk directions but achieving no operational breakthroughs.
Operational Updates
- Eastern Sector (Donetsk): RF forces continued grinding assaults, with the highest concentrations reported in Pokrovsk (34 attacks repelled) and Sloviansk (23 attacks repelled). UAF General Staff reported repelling 229 ground attacks across the front over the previous 24-hour cycle. RF milbloggers claimed tactical advances in the Shevchenko microdistrict of Chasiv Yar and near Dolga Balka, but these claims lack independent geospatial verification. In the Lyman direction, UAF drones from the 66th Separate Mechanized Brigade are reportedly disrupting RF ground logistics, forcing resupply on foot.
- Northern Sector (Kharkiv/Sumy): RF forces intensified efforts to create a "buffer zone" in Sumy Oblast, with sources claiming a 3km advance toward Korchakivka. The UAF 210th Assault Regiment is actively repelling infiltrations in the Myropil, Krasnopil, and Hrabovske areas. In Kharkiv Oblast, RF tactical aviation launched repeated KAB strikes on eastern districts and Izyum, causing residential damage and civilian injuries.
- Southern Sector (Zaporizhzhia/Kherson/Odesa): The primary focus of RF aerospace activity. Following overnight strikes, RF MoD claimed hits on three bulk carriers in Yuzhny and Odesa ports, though independent verification of cargo or extent of damage is pending. Civilian casualties were reported in Zaporizhzhia (2 injured) and Odesa (truck driver injured). UAF Special Operations Forces claimed the destruction of 13 RF shadow fleet vessels overnight, continuing maritime interdiction efforts.
- Kursk Direction: UAF strikes on energy infrastructure in Kursk Oblast resulted in a power outage affecting over 46,000 consumers, according to RF State Duma member Khinstein. Ground contact lines remain static with localized resistance.
Deep Strikes & Air Defense
- UAF Deep Strikes: President Zelenskyy confirmed UAF strikes on Wildberries logistics hubs in Elektrostal (Moscow Oblast) and Kotovsk (Tambov Oblast), alleging they supplied drone components. Satellite imagery confirms a massive fire at the Elektrostal facility. RF authorities confirmed 7 dead and 25 injured in Kotovsk, and 24 injured in Elektrostal. Additionally, UAF struck an oil depot in Noginsk (Moscow Oblast) and a Miratorg agricultural complex in Bryansk Oblast.
- RF Aerospace Campaign: RF launched a massive multi-vector assault on Odesa Oblast, utilizing 2 Iskander-M ballistic missiles, 2 Onyx anti-ship missiles, 3 Kh-59/69 cruise missiles, and 90 UAVs. UAF Air Force reported intercepting 70 targets, with debris falling in 19 locations. RF also launched KAB strikes on Kharkiv, Zaporizhzhia, and Dnipro districts, causing fires and civilian injuries.
- Air Defense: UAF Air Force actively engaged the saturation wave over Odesa. RF MoD claimed to have shot down 379 UAF drones overnight, a figure assessed as highly exaggerated for propaganda purposes. UAF Unmanned Systems Forces Commander reported striking 83 RF energy nodes in operational depth between July 1-18.
SAR Intelligence (Satellite Data)
- High Priority: SAR anomaly detection identified critical activity deviations at several locations:
- AB Pribylovo / 549th Base Air Group (60.46, 28.74): Score 8.67 (Critical Anomaly). Indicates significant logistical reshuffling or unit movement.
- Military site — Dezavar, Kermanshah Province (Iran) (34.84, 46.53): Score 7.26 (Critical Anomaly). Likely environmental or non-combat related noise given location, but warrants monitoring for regional spillover.
- Engineer Battalion (Leningrad Military District, 68.81, 32.82): Score 2.27 (High Anomaly). Suggests reactive logistical adjustments or dispersal.
- Analysis: The elevated score at AB Pribylovo aligns with reported RF aviation activity and potential dispersal measures following deep strikes. The Iranian anomalies are likely unrelated to the immediate theater but reflect broader regional monitoring requirements. No significant changes were detected at frontline logistics hubs, indicating stable baseline activity.
Equipment & Losses
- RF Losses: UAF SBS claimed destruction/damage of 13 RF shadow fleet vessels. RF sources admitted to critical power grid failures in Kursk Oblast (46,000+ consumers affected). Casualties confirmed at Wildberries facilities (7 killed, ~49 injured).
- UAF Losses: Confirmed civilian casualties in Zaporizhzhia (2 injured), Odesa (1 injured), and Kharkiv (residential damage, injuries reported). One UAF self-propelled artillery unit was destroyed by RF FPV drones near Vyshe Solone (Luhansk Oblast).
Confidence Check
- Wildberries Strikes BDA: HIGH (Confirmed by satellite imagery, RF authorities, and President Zelenskyy).
- Odesa Port Strikes: MEDIUM (RF MoD claims of hitting bulk carriers require independent AIS/satellite verification; civilian impact confirmed).
- Sumy Buffer Zone Advances: LOW (RF claim only; UAF reports active repulsion of infiltrations).
- Shadow Fleet Strikes: MEDIUM (Claimed by UAF SBS; independent AIS/satellite verification required).
- Kursk Power Outage: HIGH (Admitted by RF State Duma member).
The Bottom Line
The conflict trajectory is defined by UAF’s successful expansion of asymmetric strikes to RF deep-rear logistics hubs (Wildberries), exacerbating domestic economic and social friction, while RF continues its attritional grind on the eastern front and intensifies aerospace pressure on southern maritime infrastructure. In the next 24 hours, monitor:
- Wildberries BDA: Satellite imagery confirmation of the full extent of damage to Elektrostal and Kotovsk facilities and assessment of supply chain disruption.
- Odesa/Chornomorsk Port Operations: Verification of RF claims regarding struck bulk carriers and assessment of operational impact on grain/military cargo flows.
- Sumy Border Dynamics: Geospatial verification of RF claims of advances near Korchakivka versus UAF reports of contained infiltrations.
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 17 Jul 2026, 15:07 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 50.9 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
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 |
|---|---|---|---|
| Elektrostal | RU | 55.7835532, 38.4551611 | |
| Kotovsk | RU | 52.5978077, 41.50931870000001 | |
| Odesa | UA | 46.4845702, 30.7326047 | |
| Chornomorsk | UA | 46.2952236, 30.6480855 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Sloviansk | UA | 48.8532, 37.6053 | |
| Chasiv Yar | UA | 48.5884808, 37.8354218 | |
| Sumy Oblast | UA | 0, 0 | |
| Kursk Oblast | RU | 0, 0 | |
| Noginsk | RU | 55.8555031, 38.44094800000001 | |
| Bryansk Oblast | RU | 0, 0 | |
| AB Pribylovo | RU | 60.425671, 28.6753152 | |
| Yuzhny | UA | 46.6240213, 31.1000648 | |
| Vyshe Solone | UA | 49.7374321, 39.3451956 |
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.
