Daily intelligence

Daily Intelligence Report

Published Intelligence Summary & Geospatial Analysis
Report number
475

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

DTG: 171300Z NOV 25 REPORTING PERIOD: 161300Z NOV 25 – 171300Z NOV 25 SUBJECT: Intelligence Summary - CRITICAL: RF Strike Executed, Threat Shifts to SpN Exploitation of Confirmed GLOC Severance

1. EXECUTIVE SUMMARY

(HIGH CONFIDENCE) NEW: The Russian Federation (RF) executed the predicted large-scale strike, expending over 100 UAVs in a saturation attack which UAF successfully countered. NEW: SAR intelligence indicates a subsequent decrease in activity at key GRAU arsenals, lowering the immediate threat of a follow-on massed strike and shifting the paramount threat to RF Spetsnaz (SpN) exploitation of the now-confirmed severed rail line at Zaporizhzhia-Kamyan’ske.

2. CHANGES FROM PREVIOUS

  • RF Strike Posture (STATUS CHANGE: IMMINENT STRIKE → STRIKE EXECUTED/RECONSTITUTION PAUSED): The massed strike anticipated in the previous report has occurred. UAF Air Force confirms neutralizing 108 UAVs. This represents a significant expenditure of RF assets. CRITICAL CHANGE: Contrary to yesterday's assessment of accelerated reconstitution, new SAR data shows STABLE or FALLING activity at monitored arsenals. The immediate reconstitution effort appears to have culminated with this strike. (HIGH CONFIDENCE)
  • Zaporizhzhia-Kamyan’ske Rail Interdiction (STATUS CHANGE: ASSESSED → CONFIRMED): The strike on the critical rail hub is now officially confirmed by the CEO of Ukrainian Railways (UZ). The logistical crisis is a confirmed operational reality. (HIGH CONFIDENCE)
  • RF Air Defense Posture (STATUS CHANGE: RISING → STABLE/FALLING): Yesterday’s identified threat of AD hardening, specifically from the 183rd Guards AD Regiment, is not corroborated by today’s SAR data. Activity at monitored AD sites is generally stable or falling, suggesting the hardening effort has plateaued for now. (MEDIUM CONFIDENCE)
  • NEW Strategic Development: The EU Council has formally agreed to redirect civilian funds for military aid and support Ukraine's accession to the European Defence Fund. This provides a significant long-term strategic advantage for UAF sustainment and force generation. (HIGH CONFIDENCE)

3. THREAT ASSESSMENT

  • RF SpN Kinetic Action (THREAT LEVEL: PARAMOUNT - UNCHANGED/INCREASED URGENCY): This remains the primary and most time-sensitive tactical threat. With the Kamyan’ske rail GLOC confirmed severed, UAF is entirely dependent on vulnerable road transport. The operational window for RF SpN elements in the Kostiantynivka sector to interdict these convoys and achieve operational paralysis is at its peak. (HIGH CONFIDENCE)
  • RF Follow-on Strikes (THREAT LEVEL: HIGH → MEDIUM-LOW): This is a significant downgrade from the previous report. The expenditure of >100 UAVs and the lack of SAR indicators for immediate reloading/reconstitution at key arsenals significantly lowers the probability of another massed missile/UAV strike within the next 24-48 hours. The threat of smaller, opportunistic strikes remains. (MEDIUM CONFIDENCE)
  • RF ISR Exploitation (THREAT LEVEL: MEDIUM → HIGH): The threat of RF UAS conducting Battle Damage Assessment (BDA) over Kamyan’ske and actively identifying UAF contingency logistics hubs and transloading points for future targeting is now assessed as HIGH. (HIGH CONFIDENCE)

4. OPERATIONAL DEVELOPMENTS

  • Air Defense Domain: UAF AD forces achieved a major tactical success, neutralizing 108 RF UAVs in a single reporting period. This action successfully defended against a large-scale saturation attack but represents a significant expenditure of friendly AD interceptors.
  • Logistics Domain: The severance of the primary rail GLOC at Kamyan’ske is confirmed, forcing a full dependency on road convoys through the Kostiantynivka operational rear. This has placed extreme stress on J4 planning and force protection assets.
  • Friendly Losses: Reports confirm 8 fatalities within the 35th Marine Brigade resulting from a separate RF strike in the Dnipropetrovsk area.
  • Ground Domain: RF forces continue to apply high-tempo pressure on the Pokrovsk axis to fix UAF defenders and exploit the ongoing logistics crisis.

5. INTELLIGENCE GAPS

  • PRIORITY 1 (CRITICAL - UNCHANGED): Determine OOB, C2 structure, and specific targeting plans for RF SpN elements in the Kostiantynivka-Myrnohrad sector. The urgency of this requirement has increased.
  • PRIORITY 2 (CRITICAL - UNCHANGED): Obtain definitive BDA and Estimated Time to Repair (ETR) for the Kamyan’ske railway station. The continued absence of this data is severely degrading operational and logistical planning.
  • PRIORITY 3 (HIGH - NEW): Assess RF long-range strike asset inventory (specifically Shahed-type UAVs) following the mass expenditure. Task collection against the '2652th' and '70th' arsenals to confirm their current low activity status and establish a baseline for identifying the start of the next reconstitution cycle.

6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)

  • MOST LIKELY COA (SpN Exploitation): (HIGH CONFIDENCE) RF SpN elements will execute kinetic attacks (ambush, IED, FPV strikes) on UAF logistics convoys along the Kostiantynivka road bypass within 24 hours to maximize disruption. Concurrently, RF ISR assets will conduct reconnaissance of the Kamyan’ske area to finalize BDA and identify new logistics targets (transloading points, repair crews). High-tempo ground assaults at Pokrovsk will continue unabated.
  • MOST DANGEROUS COA (Operational Paralysis): (MEDIUM CONFIDENCE) The probability of this COA remains. A successful SpN interdiction of the road GLOCs is no longer dependent on a follow-on air strike to be decisive. An attack that halts road traffic for >18 hours could, by itself, create a logistics failure severe enough to trigger a forced, non-tactical withdrawal from forward positions at Pokrovsk.

7. RECOMMENDATIONS

  1. Reiterate and Enforce Operation IRON CLAW / VIPER HUNT (IMMEDIATE/CRITICAL - J3/J4/GUR): Re-issue standing orders with maximum urgency. All logistics convoys through the Kostiantynivka sector MUST proceed with mandatory armored escort and dedicated overhead ISR. Prioritize all available SOF and SIGINT assets to neutralize the SpN threat before it can act.
  2. Task ISR for Post-Strike Analysis (IMMEDIATE - J2): Task all-source collection to determine RF strike inventory post-expenditure. Specifically task SAR/IMINT against the '2652th' and '70th' arsenals to confirm current activity levels. NEW: Add Air Base Monchegorsk to the collection plan due to a new RISING SAR trend.
  3. Direct Contingency Planning (IMMEDIATE - J3/J5): Direct Brigade Commanders on the Pokrovsk front to finalize and rehearse pre-planned, phased withdrawal routes to alternative defensive lines. The risk of logistics failure is now a confirmed, high-probability event. Proactive planning is essential to prevent a tactical setback from becoming an operational collapse.
  4. Escalate BDA Requirement (IMMEDIATE - J3 to J4/ENGINEERS): J3 must formally task J4/Engineers with a non-negotiable 4-hour deadline to provide a preliminary BDA and ETR for the Kamyan’ske rail hub. All further operational planning is contingent upon this data.

//END OF REPORT//

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 17 Nov 2025, 13:01 UTC
Map revision comparison

Against the previous report from 16 Nov 2025, 13:01 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

1 visuals
Open full size
Nightwatch daily report #475: Pokrovsk axis area

Geospatial Analysis

10 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 10 places with coordinates
Geocoded places in report 475
PlaceCountryLatitude, longitudeCopy
Kamyan’skeUkraine47.0649393, 35.4967687
Zaporizhzhia-Kamyan’ske Rail LineUkraine47.83928419999999, 35.13870970000001
Kostiantynivka sectorUkraine48.52394289999999, 37.7075811
Kostiantynivka operational rearUkraine48.52394289999999, 37.7075811
Pokrovsk axisUkraine48.282193, 37.1847804
Pokrovsk front (forward positions)Ukraine48.282193, 37.1847804
Dnipropetrovsk areaUkraine48.464717, 35.046183
'2652th' arsenalUnknown0, 0
'70th' arsenalUnknown0, 0
Air Base MonchegorskRussia67.943134, 32.8919562

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.