Daily intelligence

Zaporizhstal Strike Halts Production; UAF Deep Strikes Indefinitely Disrupt Russian Petrochemical Logistics Amid Static Frontline Attrition

Published Intelligence Summary & Geospatial Analysis
Report number
768

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 19.3 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

Machine-generated narrative. Labels inside it are written by the model. How to read these labels

Strategic Overview

The most significant verified operational change of the day is the confirmed indefinite halt of operations at the Sibur-ZapSibNeftekhim petrochemical complex in Tobolsk, Tyumen Oblast, following a Ukrainian deep-strike campaign that now consistently disrupts strategic Russian energy processing and commercial logistics. Concurrently, a ballistic strike on the Zaporizhstal metallurgical facility in Zaporizhzhia Oblast resulted in 7 fatalities and 24 injuries, fully halting enterprise operations. Frontline contact lines remain static under high-tempo attrition with no verified territorial shifts, despite unverified pro-RF claims of minor advances near Toretskoe and Shcherbakovka.

Compared to yesterday's report, which highlighted strikes on Odesa/Kharkiv infrastructure and the Sizran Refinery, today's cycle confirms expanded kinetic effects into Western Siberia (Tobolsk), documents new UAF tactical adaptations including 40–150 km mid-range drone integration by the 7th Rapid Reaction Corps, and notes close-proximity SIGINT operations by the 129th Separate Heavy Mechanized Brigade near Vovchansk. Current conditions across the contact line feature temperatures ranging from 29.1°C in Kharkiv/Vovchansk to 34.2°C in Kherson, with negligible precipitation and cloud cover between 38% and 71%, providing optimal visibility for sustained aerospace operations.

Operational Updates

  • Kupiansk / Lyman / Izium / Volchansk: High-tempo attritional combat persists. Control boundaries are static. The 129th Separate Heavy Mechanized Brigade conducts close-proximity surveillance and SIGINT operations within approximately 5 meters of Russian positions near Vovchansk, Kharkiv Oblast. Pro-RF milbloggers claim minor advances near Chernoe and Shcherbakovka; these claims are UNCONFIRMED and lack independent geospatial validation or UAF corroboration.
  • Pokrovsk / Kostiantynivka / Sloviansk / Druzhkovka: Defensive lines hold under sustained bombardment. The 119th Separate Territorial Defense Brigade ("Nebula Division") and 71st Operational Aviation Brigade conduct active FPV and transport interdiction campaigns. Russian forces struck the central market in Slovyansk, Donetsk Oblast using a Molniya-2 drone, injuring four civilians per local administration. Claims of captures near Toretskoe, Novonikolaevka, and Novoe Pole are UNCONFIRMED.
  • Zaporizhzhia / Orikhiv: Extreme aerospace pressure continues. A ballistic strike hit the Zaporizhstal metallurgical facility, resulting in 7 fatalities and 24 injuries; operations are fully halted and a day of mourning was declared. A secondary strike on Zaporizhzhia city, Zaporizhzhia Oblast produced heavy smoke plumes; preliminary OVA assessment indicates zero casualties.
  • Kharkiv / Sumy / Poltava Axes: Elevated aerospace threat. Reactive UAV vectors tracked toward Poltava and northern approaches to Kharkiv and Sumy. A missile strike impacted a civilian enterprise in the Pishochyn community, Kharkiv Oblast, injuring two men (one in critical condition).
  • Odesa / Mykolaiv / Southern Coast: Active maritime/aerospace tracking. A hostile strike on a tanker truck near the Myaky/Rozdilna axis, Odesa Oblast killed two and injured three. The State Bureau of Investigation documented the crash site of a MiG-29 fighter in Odesa Oblast; the pilot successfully ejected, and an investigation is open.
  • Cross-Border / Kursk-Sumy Corridor: The 158th Separate Mechanized Brigade FPV drones destroyed a column of Russian all-terrain vehicles transiting a rural route between Kursk and Sumy regions.

Deep Strikes & Air Defense

  • RF Aerospace Campaign: Coordinated multi-vector saturation continues utilizing reactive UAVs, KAB glide bombs, and ballistic/cruise missiles. UAF Air Force tracks vectors toward Pryluky, western Kharkiv, southern Mykolaiv, and Odesa. Specific munition types beyond tracked profiles remain partially UNCONFIRMED pending forensic verification.
  • UAF Deep Strikes / ISR: Systemic long-range interdiction campaign confirmed by SBS Command. Visual and official reporting confirm hydrocarbon fires at Orsk Oil Refinery (Orenburg Oblast) and Wildberries logistics hubs (Voronezh Oblast). Operations at the Sibur-ZapSibNeftekhim complex in Tobolsk, Tyumen Oblast have been halted indefinitely following an August 10 UAV strike. Additional claimed targets include a Black Sea cargo vessel and Buk-M3 SAM systems.
  • Air Defense Engagement: UAF AD networks execute high-tempo engagements across northern, central, and southern approaches. Skynex systems remain deployed in the Western Command sector. UAF has adjusted public reporting metrics to preserve operational security regarding missile ingress volumes amid acknowledged interceptor stockpile constraints. Dempster-Shafer fusion models indicate persistent uncertainty (~0.83) regarding full interception outcomes during saturation events, corroborating reported engagement strain.

SAR Intelligence (Satellite Data)

  • Imagery Review: Nothing significant to report. 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:
    • Equipment: Two 2S19 Msta-S SPGs destroyed on the Vovchansk axis (57th Separate Mechanized Brigade). Imagery suggests potential strike damage to an S-400 Triumf installation near Gelendzhik, Krasnodar Krai, with wreckage moved into adjacent forest; specific identification remains unverified.
    • Personnel: Information insufficient.
  • UAF Losses/Damage:
    • Equipment: One MiG-29 fighter jet lost in Odesa Oblast following a combat sortie; cause under formal inquiry.
    • Personnel: Information insufficient.

Confidence Check

  • Zaporizhstal ballistic strike casualties (7 KIA, 24 WIA) & production halt: HIGH (Confirmed by Zaporizhzhia OVA/GS ZSU)
  • ZapSibNeftekhim (Tobolsk) indefinite operational halt: HIGH (Corroborated by Reuters/UAF SBS)
  • Pishochyn missile strike injuries: HIGH (Confirmed by Kharkiv OVA)
  • Odesa tanker truck strike casualties (2 KIA, 3 WIA): MEDIUM-HIGH (Confirmed by Odesa OVA)
  • RF territorial gains near Toretskoe/Shcherbakovka/Chernoe: LOW (Lack UAF corroboration and independent geospatial validation; map date anomalies noted)
  • UAF MiG-29 loss: HIGH (Documented by State Bureau of Investigation)
  • European Patriot interceptor stockpile constraints: MEDIUM (Reported by Politico/UAF statements)

The Bottom Line

Analysts assess that RF forces are executing sustained multi-vector aerospace sweeps aimed at compressing UAF air defense reaction windows and degrading regional economic resilience, while UAF deep-strike operations expand their operational radius into Russian strategic depth, inflicting indefinite halts on key petrochemical facilities and logistics hubs. Ground dynamics remain locked in high-tempo attrition with no verified breakthroughs, though both sides are rapidly adapting technical warfare postures through extended-range drone integration and close-proximity intelligence gathering.

Key indicators to monitor in the next 24 hours:

  1. UAF AD Interceptor Allocation & Reporting Adjustments: Monitor engagement outcomes and official statements regarding anti-ballistic capability constraints amid sustained multi-vector ingress.
  2. Terminal Damage Assessments (Zaporizhzhia/Donbas): Track municipal repair timelines and casualty triage updates following the Zaporizhstal strike and Slovyansk market attack.
  3. Frontline Geospatial Verification: Continue tracking open-source mapping for Toretskoe, Novonikolaevka, and Shcherbakovka peripheries to distinguish between speculative milblog narratives and actual positional changes.
  4. Mid-Range Drone Integration: Assess operational deployment and logistical impact of the 7th Rapid Reaction Corps' newly fielded 40–150 km strike platforms against Russian rear-area supply routes.

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.

Report 11 Aug 2026, 15:05 UTCLagged by 19.3 h
Map revision comparison

Against the previous report from 10 Aug 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.

Compare on map

The latest control-map interval ended 19.3 hours before this report. The daily change covers 24.8 h. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
+5.6 km²
25 h ending 10 Aug 2026, 19:46 UTC
Daily net
+5.6 km²
24.8 h comparison
Seven-day net
+29 km²
167.7 h comparison
Largest changes in the latest measured interval
Near Kupiansk
5.6 km² changed · RF-held gained 5.6 / lost 0.0 km²

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 visuals
Open full size
Nightwatch daily report #768: Vovchansk area

Geospatial Analysis

9 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 9 places with coordinates
Geocoded places in report 768
PlaceCountryLatitude, longitudeCopy
TobolskRU58.2227256, 68.2777646
VovchanskUA50.284234, 36.9329429
SlovyanskUA48.8532, 37.6053
RozdilnaUA46.8546237, 30.0749436
Orsk Oil RefineryRU51.2294181, 58.47514200000001
VoronezhRU51.6683487, 39.19192880000001
GelendzhikRU44.5620352, 38.0904574
PrylukyUA50.5884714, 32.3875825
Zaporizhzhia47.83928419999999, 35.13870970000001

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.