Daily intelligence

Daily Intelligence Report

Published Intelligence Summary & Geospatial Analysis
Report number
361

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
Age of the map data is not available.

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

1. EXECUTIVE SUMMARY

Enemy forces are escalating offensive pressure on the Avdiivka axis, employing new thermobaric munitions and armored tactics, indicating a concerted effort to achieve a tactical breakthrough (HIGH Confidence). Concurrently, a significant increase in sophisticated Electronic Warfare (EW) activity has been detected in the south, aimed at degrading friendly C4ISR and precision-guided munitions (PGM) capabilities (HIGH Confidence). These developments suggest a coordinated, multi-axis effort to seize the initiative before anticipated changes in weather conditions.

2. CHANGES FROM PREVIOUS

  • NEW - Offensive Tactics (Avdiivka): Confirmed use of TOS-1A thermobaric multiple launch rocket systems (MLRS) in direct support of mechanized assaults near Avdiivka, a significant escalation in firepower on this axis. Previous reports noted artillery preparation; this is a qualitative change in ordnance employed.
  • NEW - EW Capabilities (Zaporizhzhia): First-time identification of the Murmansk-BN long-range communications jamming system in the southern operational area. This represents a strategic-level EW threat not previously observed in this sector, capable of disrupting HF communications over a wide area.
  • CHANGED - Air Threat Profile: Enemy aviation has shifted from sporadic sorties to coordinated strikes using FAB-500 glide bombs against fixed positions along the entire southern front, a change from previous patterns of isolated air-to-ground attacks.
  • CHANGED - Force Posture (Lyman): Enemy forces in the Lyman sector have transitioned from a defensive posture to conducting localized, company-sized probing attacks, indicating a potential shift towards offensive operations.

3. THREAT ASSESSMENT

  • Air/PGM Threat: SEVERE. The combination of enhanced EW (Murmansk-BN, Shipovnik-Aero) and increased use of glide bombs poses a severe threat to friendly air operations, C2 nodes, and forward-deployed units. The enemy is actively attempting to create an anti-access/area denial (A2/AD) bubble to neutralize our PGM advantage (HIGH Confidence).
  • Ground Offensive Threat (Avdiivka): HIGH. The commitment of TOS-1A systems and fresh T-90M tanks, coupled with recent ground assaults, indicates a high and immediate threat of a renewed major offensive to encircle friendly forces in Avdiivka (HIGH Confidence).
  • Artillery Threat: HIGH. Enemy artillery, particularly in the Bakhmut and Avdiivka sectors, continues to fire at high volumes. The primary threat is counter-battery fire targeting friendly artillery assets, enabled by Orlan-10 and ZALA drone observation.
  • UAV Threat: HIGH. The integrated use of Lancet loitering munitions for tactical strikes and Orlan-10/Supercam drones for reconnaissance and artillery spotting remains a persistent, high-level threat to armor, artillery, and logistics convoys.

4. OPERATIONAL DEVELOPMENTS

  • Avdiivka Axis:

    • CONFIRMED: Enemy forces conducted two separate company-sized mechanized assaults on southern approaches to Avdiivka, supported by TOS-1A fire strikes. Both assaults were repelled with significant enemy armor losses (est. 5-7 MBTs, 10+ IFVs), but friendly positions sustained damage.
    • CONFIRMED: SIGINT and visual observation confirm the deployment of at least one company of T-90M tanks to this axis, likely from the 90th Guards Tank Division, replacing combat-ineffective units (HIGH Confidence).
  • Zaporizhzhia Axis (Robotyne/Verbove):

    • CONFIRMED: Widespread GPS signal degradation and C2 jamming reported across the front, corroborating the activation of the Murmansk-BN system. Multiple friendly UAV sorties were aborted due to loss of control link.
    • Enemy activity remains largely defensive, focused on reinforcing trench lines and emplacing new minefields. No significant ground attacks were reported in the last 24 hours.
  • Bakhmut Axis:

    • Positional fighting continues around Klishchiivka and Andriivka. Enemy forces conducted multiple platoon-level counter-attacks to regain lost high ground, all of which were unsuccessful (MEDIUM Confidence). Artillery duels remain the primary activity in this sector.
  • Lyman-Kupiansk Axis:

    • CONFIRMED: Enemy forces conducted probing attacks near Synkivka and Terny, likely to fix friendly forces in place and identify weaknesses in defensive lines. These actions appear to be shaping operations rather than a main effort (MEDIUM Confidence).

5. INTELLIGENCE GAPS

  • PRIMARY: What is the specific enemy trigger/criteria for committing main effort reserves for a larger-scale offensive in the Avdiivka sector?
  • PRIMARY: Location and operational status of the command-and-control node for the Murmansk-BN EW system.
  • Current stock levels and resupply rate of FAB-500 glide bombs to forward airfields.
  • Composition, readiness, and intent of enemy reserves behind the Lyman-Kupiansk line of contact.
  • Enemy assessment of the effectiveness of their new thermobaric and EW tactics.

6. PREDICTIVE ANALYSIS (24-48 HOUR FORECAST)

  • MOST LIKELY COA: Enemy will continue intense pressure on Avdiivka, using thermobaric and heavy artillery preparation to soften defenses for another multi-pronged armored assault within the next 24-48 hours. The objective remains the tactical encirclement of the city (HIGH Confidence).
  • SECOND MOST LIKELY COA: In the south, the enemy will leverage their enhanced EW bubble to support spoiling attacks with loitering munitions and glide bombs, aiming to disrupt friendly offensive preparations and degrade our command and control (MEDIUM Confidence).
  • POSSIBLE COA: A larger, battalion-level offensive could be launched in the Lyman sector if probing attacks reveal a significant vulnerability in friendly defenses (LOW Confidence).

7. RECOMMENDATIONS

  • PRIORITY 1 (DEFENSE): Immediately reinforce Avdiivka sector with additional ATGM teams and FPV drone assets to counter the renewed armored threat. Pre-plan counter-battery fires on likely TOS-1A firing positions.
  • PRIORITY 2 (EW/C4ISR): Task all available ISR assets (SIGINT, IMINT) to locate and target the Murmansk-BN EW system and associated C2 nodes in the south. This is now a high-priority target.
  • PRIORITY 3 (AIR DEFENSE): Disperse and camouflage forward air defense systems to mitigate the threat from glide bombs. Increase combat air patrols (CAP) if feasible to intercept launch platforms before weapon release.
  • PRIORITY 4 (INTEL): Focus collection efforts on identifying enemy reserve force movements behind the Avdiivka and Lyman fronts to provide early warning of a major offensive push.

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 28 Jul 2025, 15:08 UTC
Map revision comparison

Against the previous report from 27 Jul 2025, 15:04 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
Frontline change measurements are unavailable for this briefing.

Report Visuals

3 visuals
Open full size
Nightwatch daily report #361: Avdiivka area

Geospatial Analysis

16 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 16 places with coordinates
Geocoded places in report 361
PlaceCountryLatitude, longitudeCopy
AvdiivkaUkraine48.136596, 37.7491335
Southern approaches to AvdiivkaUkraine48.136596, 37.7491335
Zaporizhzhia axis (Robotyne/Verbove)Ukraine47.4497264, 35.8373394
Southern operational area (Zaporizhzhia region)Ukraine47.7806619, 35.1835641
Southern front (general)Ukraine48.379433, 31.16558
Lyman sectorUkraine48.9897585, 37.8049964
SynkivkaUkraine49.7657845, 37.7025771
TernyUkraine49.09196009999999, 37.9601291
KlishchiivkaUkraine48.529039, 37.9591079
AndriivkaUkraine48.5010918, 37.9653493
RobotyneUkraine47.4497264, 35.8373394
VerboveUkraine47.4303941, 35.9765345
Avdiivka Sector (rear areas)Ukraine48.136596, 37.7491335
Southern operational area (Zaporizhzhia region)Ukraine47.7806619, 35.1835641
Forward Airfields (Southern Front)Ukraine48.379433, 31.16558
Behind Lyman frontUkraine48.9897585, 37.8049964

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.