Daily intelligence

RF Force Expansion and Deep-Strike Logistics Disruption Define July 31 Operational Picture

Published Intelligence Summary & Geospatial Analysis
Report number
757

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 42.4 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 formal increase of Russian Armed Forces (RF) personnel strength by 27,000 to 2,426,130, effective August 1. This administrative expansion occurs alongside confirmed severe logistical disruptions in the RF rear, specifically fuel shortages in Volgograd following UAF strikes on the Lukoil-Volgogradneftepererabotka refinery. The convergence of forced manpower growth and degraded energy infrastructure highlights RF attempts to offset frontline stagnation through quantitative measures while managing cascading supply chain failures.

Concurrently, the conflict’s geographic footprint expanded diplomatically with Polish investigators confirming that debris from a Kh-101 cruise missile found in Lublin Voivodeship was manufactured in Q2 2026 in Moscow Oblast. This forensic confirmation solidifies the assessment of the incident as a direct RF aerospace failure rather than a Ukrainian interception error. In Ukraine, an unplanned munitions detonation at a training ground in Khmelnytskyi Oblast resulted in four injuries and missing personnel, prompting a criminal investigation into weapons handling violations.

Operational Updates

  • Eastern Sector (Donetsk/Kharkiv): Ground operations remain characterized by high-tempo attritional assaults with no independently verified major territorial changes. RF milbloggers claimed covert underground operations by the 5th Guards Brigade in the "Belitsky" area using VR-equipped FPV drones, though location and mercenary claims remain unverified. In the Kupiansk direction, video evidence confirmed a direct hit on an RF 1486th Motorized Rifle Regiment subterranean bunker, causing structural compromise. RF forces continued FAB-1500 glide bomb strikes against UAF brigade positions in Orikhiv and Sloviansk.
  • Southern Sector (Zaporizhzhia/Mykolaiv/Odesa): No significant ground maneuvers were reported. RF MoD claimed strikes on a dry cargo ship south of Odesa and port infrastructure, including a POL tank and Odessa Oil Refinery workshops; independent verification of damage remains pending. UAF Air Force tracked multiple UAV groups approaching Odesa from the Black Sea, engaging them over maritime approaches. In Zaporizhzhia Oblast, civilian evacuations continued from frontline villages such as Lystivka due to sustained air strikes.
  • Northern Sector (Sumy/Chernihiv): UAF Air Force engaged an RF reconnaissance UAV approaching Sumy from the southeast. RF forces continued artillery and UAV strikes across the border, with air raid alerts issued for Kharkiv and Poltava oblasts. No verified territorial changes occurred in the Vovchansk or Kupiansk sectors despite RF claims of advances.

Deep Strikes & Air Defense

  • UAF Deep Strikes:
    • Volgograd Oblast: Confirmed fires at the Lukoil-Volgogradneftepererabotka refinery and a Wildberries logistics hub. Local reports indicate severe fuel queues in Volgograd city, demonstrating immediate logistical impact.
    • Tatarstan/Dagestan: Unconfirmed reports and visual evidence indicated strikes on industrial complexes and logistics hubs in Kazan, Zelenodolsk, and Nizhnekamsk. A massive explosion was observed in Khmelnytskyi Oblast at a military training ground, later confirmed as an unplanned munitions detonation injuring four personnel.
    • Cheboksary: Visual evidence confirmed the demolition of a severely damaged building at the VNIIR-Progress factory, assessing damage from a prior June strike as beyond repair.
  • RF Aerospace Campaign:
    • Maritime/Port: RF MoD claimed strikes on a cargo ship and Odessa Oil Refinery infrastructure. Claims remain unverified by independent imagery.
    • Logistics: RF sources claimed a Geran-4 UAV struck a Nova Poshta hub near Pidhorodne (Dnipropetrovsk Oblast); provided video only showed targeting overlays without impact confirmation.
    • Urban/Infrastructure: Missile and KAB strikes targeted Kharkiv, Poltava, and Zaporizhzhia. A massive fire erupted at a shopping complex in Pavlohrad (Dnipropetrovsk Oblast), with one injury reported.

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: Confirmed fires at Lukoil-Volgogradneftepererabotka and Wildberries hub in Volgograd. Demolition of damaged VNIIR-Progress facility in Cheboksary.
    • Personnel: Structural compromise of RF 1486th MRP bunker in Kupiansk direction. Relatives of 126th and 127th regiments publicly denounced command over missing soldiers and unpaid pay.
  • UAF Losses/Damage:
    • Personnel: Four military personnel injured and several missing following unplanned munitions detonation at Khmelnytskyi training ground. One civilian injured in Pavlohrad fire.
    • Security: Thwarted assassination attempt on Col. Igor Obolensky (2nd Army Corps) in Kharkiv; 69-year-old suspect detained.

Confidence Check

  • RF Force Expansion: HIGH (Confirmed by RF policy sources).
  • Volgograd Fuel Shortages: MEDIUM (Based on local reports and visual evidence of queues; corroborates refinery strike).
  • Kh-101 Debris Origin: HIGH (Confirmed by Polish investigators and Ukrainian experts).
  • Khmelnytskyi Detonation Cause: HIGH (Confirmed by Prosecutor General’s Office as accidental/handling violation).
  • RF Maritime Strike Claims: LOW (No independent visual confirmation of ship/refinery damage).
  • Belitsky Underground Operations: LOW (Unverified milblogger claims; likely information operation).

The Bottom Line

The RF’s decision to expand its armed forces by 27,000 personnel coincides with tangible logistical degradation in its deep rear, particularly in the Volga region. This suggests a strategy of compensating for qualitative deficits and supply chain fragility with quantitative manpower increases. In the next 24 hours, monitor:

  1. Logistical Cascades: Whether fuel shortages in Volgograd spread to other RF regions or impact frontline sustainment.
  2. US Aid Policy: Official US administration responses to reports regarding the refusal of 300 Patriot missiles and Starlink deep-strike authorization.
  3. Khmelnytskyi Investigation: Updates on the missing personnel and potential security implications of the training ground detonation.

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 31 Jul 2026, 15:05 UTCLagged by 42.4 h
Map revision comparison

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

Compare on map

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

Latest interval
+1.6 km²
25 h ending 29 Jul 2026, 20:42 UTC
Daily net
+1.6 km²
25.1 h comparison
Seven-day net
+11 km²
177.6 h comparison
Largest changes in the latest measured interval
Near Chasiv Yar
1.6 km² changed · RF-held gained 1.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

5 visuals
Open full size
Nightwatch daily report #757: Pavlohrad area

Geospatial 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
Geocoded places in report 757
PlaceCountryLatitude, longitudeCopy
VolgogradRU48.708048, 44.5133034
Lukoil-VolgogradneftepererabotkaRU0, 0
Wildberries HubRU0, 0
KupianskUA49.7055574, 37.6027997
OrikhivUA47.5658802, 35.7876745
SlovianskUA48.8532, 37.6053
VNIIR-ProgressRU56.1032427, 47.2640744
KhmelnytskyiUA49.422983, 26.987133
Odessa Oil RefineryUA0, 0
PavlohradUA48.5294478, 35.9032574
PidhorodneUA48.57248, 35.0869121
Lublin VoivodeshipPL0, 0
SumyUA50.9077, 34.7981
LystivkaUA47.8487538, 35.7633284
KharkivUA50.00201269999999, 36.3073994

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.