UAF Deep Strikes Hit Leningrad Logistics; RF Escalates 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 46.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 expansion of Ukrainian Armed Forces (UAF) deep-strike operations into Leningrad Oblast, where drone attacks on Wildberries logistics hubs in Shushary and Novosaratovka caused massive fires and claimed civilian fatalities. This marks a continued degradation of Russian Federation (RF) commercial logistics networks far from the frontline, compounding earlier strikes in Udmurtia and Rostov. Simultaneously, RF President Vladimir Putin signed a decree increasing the armed forces' staff by 27,000 personnel effective August 1, specifically citing the creation of new military construction units to support rear-area engineering and logistics.
In response to UAF asymmetric pressure, RF intensified its aerospace campaign against Ukrainian southern maritime infrastructure. The RF Ministry of Defence explicitly claimed high-precision strikes on a petroleum terminal in Odesa port, fuel tanks in Chornomorsk, and a dry cargo vessel in Mykolaiv. While independent battle damage assessment (BDA) remains pending, the targeting indicates a sustained effort to strangle Ukrainian export corridors. Diplomatic tensions escalated as Romania declared a Russian diplomat persona non grata and recalled its ambassador following repeated airspace violations by Shahed-type drones.
Operational Updates
- Eastern Sector (Donetsk/Kharkiv): Ground operations remain characterized by high-tempo attritional assaults with no independently verified territorial changes. RF milbloggers claim the capture of Torske and Komyunarka (Dnipropetrovsk Oblast), but these assertions lack geospatial confirmation. In Kharkiv Oblast, RF aviation employed FAB-500 guided bombs against alleged UAF drone command nodes in Liptsy and Oleksandrivka, causing severe structural damage. A separate strike in Balakliya killed one civilian and injured eight.
- Southern Sector (Zaporizhzhia/Odesa/Mykolaiv): RF continues heavy airstrikes on urban centers. In Zaporizhzhia city, KAB strikes damaged 75 private homes and 10 apartment buildings, with casualties rising to seven. In Crimea, a UAF drone strike hit a residential building in Kerch, injuring ten civilians. RF aerospace assets, including six Su-30/34/35 fighters, were detected over the Black Sea, posing an imminent threat to Odesa and Mykolaiv ports.
- Northern Sector (Sumy/Chernihiv): RF UAVs were tracked towards Khomiv (Chernihiv Oblast) and Putyvl (Sumy Oblast). No significant ground maneuvers were reported, though cross-border artillery shelling persists.
Deep Strikes & Air Defense
- UAF Deep Strikes:
- Leningrad Oblast: Drones struck Wildberries distribution centers in Shushary and Novosaratovka, causing large-scale fires and claimed fatalities. This follows similar strikes in Udmurtia and Rostov-on-Don over the previous 24 hours.
- Kursk Oblast: The UAF 414th OBpAS "Ptakhy Madyara" intercepted a RF Forpost-R UAV using a "Chaklun-KM" system, claiming an engagement altitude of 4,300m.
- Crimea: A drone strike impacted a five-story residential building in Kerch, resulting in ten injuries.
- RF Aerospace Campaign:
- Southern Ports: RF MoD claimed precise strikes on a POL terminal in Odesa, fuel tanks in Chornomorsk, and a bulk carrier in Mykolaiv. UAF sources confirmed damage to vessels and crew injuries in Mykolaiv.
- Kharkiv/Donetsk: Sustained use of KABs and FAB-500s against rear-area logistics and drone nodes. Jet-powered UAVs were tracked towards Kherson and Kamianske.
- Air Defense: Romanian Air Force F-16s intercepted multiple Shahed-type drones over territorial waters in the Sulina-Chilia zone. Romania formally presented downed drone debris to the Russian ambassador and expelled a diplomat.
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:
- Infrastructure: Severe fire damage to Wildberries hubs in Leningrad Oblast and Sarapul (Udmurtia). Smoke plumes observed near Rostov Sea Port.
- Aviation: One L-39 training aircraft crashed in Krasnodar Krai during low-altitude aerobatics.
- Logistics: Two ammunition trucks of the RF 68th Division destroyed in Tavolzhanka due to poor dispersal discipline.
- UAF Losses/Damage:
- Civilian Casualties: 7 dead/injured in Zaporizhzhia; 10 injured in Kerch; 1 dead/8 injured in Balakliya; 1 dead/22 injured in Kharkiv Oblast.
- Maritime: Damage confirmed to bulk carriers in Mykolaiv port following RF strikes.
Confidence Check
- Leningrad/Wildberries Strikes: HIGH (Confirmed by multiple visual sources and local reports).
- RF Southern Port Claims (Odesa/Mykolaiv): MEDIUM (Claimed by RF MoD; UAF confirms vessel damage but specific infrastructure impact awaits BDA).
- RF Territorial Claims (Torske/Komyunarka): LOW (RF claims only; lacks independent geospatial verification).
- Romanian Diplomatic Expulsion: HIGH (Confirmed by official Romanian statements and debris presentation).
- RF Force Increase Decree: MEDIUM (Reported by ASTRA; aligns with previous expansion patterns).
The Bottom Line
The conflict trajectory continues to feature UAF asymmetric deep strikes degrading RF commercial logistics in the interior, countered by RF aerospace saturation against Ukrainian maritime and urban infrastructure. In the next 24 hours, monitor:
- Southern Port BDA: Verification of damage to the Odesa POL terminal and Chornomorsk fuel tanks, which could critically impact Ukrainian fuel imports.
- RF Force Generation: Initial administrative steps regarding the integration of 25,000 new military construction personnel into the RF Armed Forces effective August 1.
- Diplomatic Fallout: Potential Russian retaliatory measures following Romania's expulsion of its diplomat and recall of its ambassador.
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 26 Jul 2026, 15:06 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 46.1 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 |
|---|---|---|---|
| Shushary | RU | 59.8065675, 30.3960031 | |
| Novosaratovka | RU | 59.84142019999999, 30.5240877 | |
| Odesa | UA | 46.4845702, 30.7326047 | |
| Chornomorsk | UA | 46.2952236, 30.6480855 | |
| Mykolaiv | UA | 46.9660801, 32.003246 | |
| Torske | UA | 49.000063, 37.9691589 | |
| Komyunarka | UA | 0, 0 | |
| Liptsy | UA | 50.2080033, 36.4094244 | |
| Balakliya | UA | 49.4643925, 36.8584805 | |
| Zaporizhzhia | UA | 47.83928419999999, 35.13870970000001 | |
| Kerch | UA | 45.357314, 36.468293 | |
| Putyvl | RU | 51.3345739, 33.8646835 | |
| Sarapul | RU | 56.4770315, 53.8171237 | |
| Rostov-on-Don | RU | 47.2357137, 39.701505 | |
| Tavolzhanka | RU | 50.6830353, 37.7773224 |
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.
