Daily intelligence

UAF Strikes Syzran Refinery and Moscow Region; RF Infiltrates Kostiantynivka Sectors

Published Intelligence Summary & Geospatial Analysis
Report number
738

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.0 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 operational development of the last 24 hours is the Ukrainian Armed Forces’ (UAF) execution of a massive, multi-vector deep strike campaign targeting Russian Federation (RF) energy infrastructure and rear-area logistics. UAF drones struck the Syzran Oil Refinery in Samara Oblast, with analysis confirming the destruction of primary processing capacity, while Moscow authorities reported intercepting approximately 300 UAVs over the capital region. This sustained aerial pressure complements ongoing maritime interdiction in the Sea of Azov, further degrading RF fuel logistics.

On the ground, RF forces achieved tactical infiltration in Kostiantynivka (Donetsk Oblast), penetrating eastern, south-eastern, and western sectors, though UAF retains control of the north-western and central districts. Concurrently, RF intensified aerospace attacks on civilian infrastructure, striking gas distribution stations in Kramatorsk and public transport in Kherson, resulting in multiple casualties. The frontline remains largely static elsewhere, with high-tempo but contained assaults in the Pokrovsk and Sumy directions.

Operational Updates

  • Eastern Sector (Donetsk): Significant tactical shifts occurred in Kostiantynivka. RF Tactical Groups "Dzerzhinsk" (8th CAA) and "Bakhmut" (3rd AK) infiltrated the eastern, south-eastern, and western parts of the city using small infantry groups supported by concentrated KAB and artillery fire. UAF continues to hold the north-western and central sectors. In the Pokrovsk direction, RF conducted 44 repelled assaults near Novooleksandrivka and Shakove. UAF 1st NGU Corps "Azov" struck an RF fuel and logistics base in Novoamvrosiivka, damaging storage tanks and blocking railway infrastructure.
  • Northern Sector (Sumy/Kharkiv/Chernihiv): RF milbloggers claimed advances in Bachivsk (Sumy Oblast) and a 3km penetration into the southern residential area of Kazacha Lopan (Kharkiv Oblast), supported by geolocated footage. UAF Air Force tracked multiple UAV incursions towards Bohodukhiv, Kharkiv, and Chernihiv. A UAF FPV drone destroyed a modified RF armored vehicle (suspected BREM-2) on the northern outskirts of Vovchansk.
  • Southern Sector (Zaporizhzhia/Kherson/Odesa): RF conducted systematic drone strikes on civilian public transport and a gas station in Kherson, causing multiple casualties among elderly civilians. In Zaporizhzhia, UAF 3rd Separate Special Purpose Regiment (SSO) claimed the destruction of 24 RF logistics vehicles using "Hornet" kamikaze drones. RF also launched KAB strikes on Zaporizhzhia Oblast and claimed strikes on port infrastructure in Chornomorsk (Odesa Oblast).
  • Kursk Direction: No significant change in ground contact lines. UAF 8th Air Assault Corps continues to repel localized assaults.

Deep Strikes & Air Defense

  • UAF Strategic Interdiction (Land): UAF FP-1 drones struck the Syzran Oil Refinery (Rosneft) in Samara Oblast. OSINT analysis confirms damage to the ELOU-AVT-5, AVT-6, and LCh-35/11-600 units, destroying 100% of primary processing capacity (8.9M tons/yr). RF confirmed 1 dead and 3 injured at the site.
  • UAF Deep Strikes (Moscow Region): Moscow Mayor Sobyanin claimed approximately 300 UAF UAVs targeted the Moscow region over the last 24 hours, with 45 destroyed near the city. Air raid alerts were also triggered in Voronezh, Lipetsk, Oryol, and Volgograd.
  • RF Aerospace Campaign: RF launched a mixed barrage of missiles, MLRS, and ~45 UAVs across Kharkiv Oblast, injuring 20 civilians. RF tactical aviation launched KABs on Dnipropetrovsk and Zaporizhzhia oblasts. RF MoD claimed strikes on vessels and port infrastructure in Chornomorsk (Odesa Oblast).
  • Air Defense: UAF Air Force tracked reactive UAVs towards Kryvyi Rih and Zhovti Vody. RF air defense claimed high intercept rates in the Moscow region, though the scale of the attack suggests significant saturation.

SAR Intelligence (Satellite Data)

  • High Priority: SAR anomaly detection identified critical activity deviations at several locations:
    • 25th Separate Guards Motor Rifle Brigade (6th Combined Arms Army): Score 3.57 (Critical Anomaly). Indicates significant movement or logistical reshuffling.
    • FGKU plant "Monolith" (Vladimir region): Score 1.94 (Critical Anomaly). Potential industrial or military production activity shift.
    • 549th Base Air Group (Leningrad Military District): Score 8.58 (Moderate Activity). Warrants monitoring for aviation asset movements.
  • Analysis: The elevated scores at the 25th Separate Guards Motor Rifle Brigade and FGKU plant "Monolith" suggest reactive logistical adjustments or increased operational tempo in response to UAF deep strikes. The high noise index in Crimea and southern Ukraine continues to limit change detection reliability due to weather conditions.

Equipment & Losses

  • RF Losses: UAF claims destruction of 24 logistics vehicles in Zaporizhzhia direction. RF confirmed 1 dead and 3 injured at Syzran Refinery. UAF General Staff reported +1,320 RF personnel and +2,034 UAVs eliminated in the last 24 hours (cumulative).
  • UAF Losses: Confirmed civilian casualties in Kherson (multiple injured/killed from drone strikes on public transport) and Kharkiv (20 injured from mixed barrage). UAF 155th STDB Commander Stanislav Luchanov remains AWOL/wanted following kidnapping allegations involving subordinates.

Confidence Check

  • Syzran Refinery Damage: HIGH (Confirmed by multiple OSINT sources, visual evidence of fire, and RF casualty reports).
  • Kostiantynivka Infiltration: MEDIUM (Corroborated by RF milbloggers and tactical reporting, but exact frontline geometry requires geolocated verification).
  • Moscow UAV Scale: MEDIUM (Based on RF official claims; actual penetration numbers remain unverified by independent Western sources).
  • Kherson Civilian Strikes: HIGH (Confirmed by local reporting and RF occupation authorities).

The Bottom Line

The conflict trajectory is defined by UAF's successful asymmetric degradation of RF strategic energy nodes (Syzran) and sustained pressure on Moscow's air defenses, forcing RF to divert resources to rear-area security. On the ground, RF is achieving slow, costly tactical gains in Kostiantynivka through infiltration tactics rather than operational breakthroughs. In the next 24 hours, monitor:

  1. Syzran Refinery Status: Extent of operational shutdown and impact on Volga region fuel distribution.
  2. Kostiantynivka Frontline: Potential UAF tactical withdrawals or counterattacks to stabilize the north-western sector.
  3. Moscow Air Defense: Follow-up UAF strikes exploiting any identified gaps in the capital's SHORAD coverage.

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 12 Jul 2026, 15:08 UTCLagged by 25.0 h
Map revision comparison

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

Compare on map

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

Latest interval
+2.5 km²
21 h ending 11 Jul 2026, 14:10 UTC
Daily net
+2.5 km²
21.0 h comparison
Seven-day net
+24 km²
160.4 h comparison
Largest changes in the latest measured interval
Near Pokrovsk
1.6 km² changed · RF-held gained 1.6 / lost 0.0 km²
Near Pokrovsk
0.8 km² changed · RF-held gained 0.8 / 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

5 visuals
Open full size
Nightwatch daily report #738: Kostiantynivka area

Geospatial Analysis

12 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 12 places with coordinates
Geocoded places in report 738
PlaceCountryLatitude, longitudeCopy
Syzran Oil RefineryRussia53.1585015, 48.4648902
KostiantynivkaUkraine48.52394289999999, 37.7075811
PokrovskUkraine48.282193, 37.1847804
NovoamvrosiivkaUkraine0, 0
VovchanskUkraine50.284234, 36.9329429
BachivskUkraine51.8449942, 34.2728339
Kazacha LopanUkraine50.15552831709362, 36.1612129141051
KhersonUkraine46.635417, 32.616867
ChornomorskUkraine46.2952236, 30.6480855
Moscow RegionRussia0, 0
25th Separate Guards Motor Rifle BrigadeRussia0, 0
FGKU plant MonolithRussia0, 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.