Daily Intelligence Report
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
Analyst briefMachine-generated narrative. Labels inside it are written by the model. How to read these labels
INTELLIGENCE SUMMARY
DTG: 121300Z NOV 25 REPORTING PERIOD: 111300Z NOV 25 – 121300Z NOV 25 SUBJECT: Operational Response to Confirmed Logistics Interdiction and UAF Strategic Counter-Strike
1. EXECUTIVE SUMMARY
(HIGH CONFIDENCE) The kinetic interdiction of the Zaporizhzhia-Kamyan’ske railway station is now CONFIRMED, initiating a critical logistics crisis for the Pokrovsk salient. Concurrently, UAF has executed a successful strategic counter-interdiction strike against the Kostroma GRES deep inside RF territory. The immediate operational focus is now the preemption of the anticipated RF Spetsnaz (SpN) attack on vulnerable road-based Ground Lines of Communication (GLOCs) in the Kostiantynivka sector, which is assessed as the next immediate step in the RF operational plan.
2. CHANGES FROM PREVIOUS
- Logistics Status (STATUS CHANGE: INTERDICTED → CONFIRMED OPERATIONAL CRISIS): NEW: The strike on the Zaporizhzhia-Kamyan’ske railway station is now fully confirmed by Ukrainian Railways (UZ), validating previous intelligence. The operational impact is no longer anticipated but is now an active crisis requiring immediate mitigation. (HIGH CONFIDENCE)
- UAF Strategic Posture (STATUS CHANGE: DEFENSIVE → DEFENSIVE WITH STRATEGIC COUNTER-STRIKE): NEW: UAF has demonstrated expanded operational reach by successfully striking the Kostroma GRES power station. This action represents a significant escalation in UAF's counter-interdiction campaign, shifting from purely defensive actions to imposing direct costs on RF critical energy infrastructure deep within its territory. (HIGH CONFIDENCE)
- RF Saturation Attack (STATUS CHANGE: EXECUTED → QUANTIFIED): NEW: The scale of the preceding RF UAV attack is now confirmed, with the Ukrainian Air Force reporting 108 enemy platforms neutralized. This quantifies the high volume of assets RF expended to fix Air Defense (AD) assets and achieve its primary objective. (HIGH CONFIDENCE)
- Environmental Factors: NEW: A G3-level geomagnetic storm is active. This has the potential to degrade GPS-guided munitions (e.g., KAB, JDAM) and long-range UAS command links for both forces, while also potentially degrading RF Air Defense radar performance. This factor must now be included in operational planning. (MEDIUM CONFIDENCE)
3. THREAT ASSESSMENT
- RF SpN Kinetic Action (THREAT LEVEL: CRITICAL - UNCHANGED but IMMINENT): The threat from RF SpN groups in the Kostiantynivka-Myrnohrad sector remains paramount. With the rail GLOC confirmed severed, the SpN mission to interdict the makeshift road GLOCs is now the decisive action for the RF to achieve the complete logistical isolation of Pokrovsk. An attack is expected imminently. (HIGH CONFIDENCE)
- RF Follow-on Strikes (THREAT LEVEL: HIGH - PERSISTENT): Despite the high expenditure of UAVs, the threat of follow-on precision strikes persists. RF ISR will now prioritize identifying UAF logistics convoys and temporary transloading points for targeting. Rising activity trends at key GRAU depots (Missile Arsenal, 2652th Artillery Base) indicate RF is actively reconstituting strike packages for subsequent waves. (MEDIUM CONFIDENCE)
- RF Information Operations (THREAT LEVEL: MEDIUM - PERSISTENT): UPDATE: RF IO has intensified, now amplifying confirmed UAF casualties within the 35th Marine Brigade and displaying captured UAF UAV debris to degrade morale and create a narrative of UAF technical inferiority. This is synchronized with kinetic operations to maximize psychological impact. (HIGH CONFIDENCE)
4. OPERATIONAL DEVELOPMENTS
- UAF Deep Strike Domain: NEW: UAF conducted a successful long-range UAS strike on the Kostroma GRES, confirming the capability and intent to hold RF strategic energy assets at risk. This action directly supports UAF's strategic objective of imposing systemic costs on the RF war effort.
- UAF Air Defense Domain: UPDATE: UAF AD demonstrated high tactical effectiveness by neutralizing 108 RF UAVs in a single wave. However, this action proved insufficient to prevent the strategic effect of the subsequent kinetic strike on the primary logistics node, highlighting a persistent challenge.
- UAF Ground Domain: NEW: Despite the operational-level crisis, tactical effectiveness remains high. Units of the 79th DShV Brigade are confirmed conducting successful close-quarters combat and clearing operations on the Pokrovsk axis, leveraging FPV drones to attrit RF personnel.
5. INTELLIGENCE GAPS
- PRIORITY 1 (CRITICAL - UNCHANGED/URGENT): Determine the OOB, C2 structure, and specific targeting plan for RF SpN elements in the Kostiantynivka-Myrnohrad sector. This remains the most urgent intelligence requirement to prevent operational isolation.
- PRIORITY 2 (CRITICAL - UNCHANGED/URGENT): Obtain a detailed Battle Damage Assessment (BDA) of the Kamyan’ske railway station to quantify the loss of throughput capacity and produce an accurate Estimated Time to Repair (ETR) to inform operational sustainment planning.
- PRIORITY 3 (HIGH - UNCHANGED): Assess RF long-range strike asset inventory (Shahed UAVs, cruise/ballistic missiles) following the recent large-scale expenditure to predict the timeline for the next operational pulse.
6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)
- MOST LIKELY COA (Coordinated GLOC Interdiction - UNCHANGED and VALIDATED): (VERY HIGH CONFIDENCE) With all preparatory shaping operations complete, RF SpN elements will execute multiple, coordinated kinetic attacks (ambush, IED, guided munitions) against UAF logistics convoys and command nodes on the Kamyan’ske road bypass within the next 24 hours. This will be supported by RF ISR assets attempting to provide real-time targeting for follow-on fires.
- MOST DANGEROUS COA (Synchronized Collapse - UNCHANGED): (MEDIUM CONFIDENCE) The probability of this COA is contingent entirely on the success of the MLCOA. A successful SpN attack creates a logistics halt (>18 hours), starving frontline units. RF ground forces at Pokrovsk, exploiting this vulnerability, will launch a focused assault to achieve an operational penetration and force a disorderly withdrawal from the salient.
7. RECOMMENDATIONS
The following recommendations from the previous reporting period are UNCHANGED and URGENTLY REITERATED as their conditions are now fully met:
- Execute Operation IRON CLAW (IMMEDIATE - J4/J3): Implement mandatory armored escort (min. 2x IFV/APC) and dedicated overhead ISR for all logistics convoys transiting the Kostiantynivka-Myrnohrad sector without exception.
- Surge Assets for VIPER HUNT (IMMEDIATE - J3/GUR): Re-task all available SOF, C-UAS, and SIGINT assets to the Kostiantynivka sector to find, fix, and destroy the SpN threat before they execute their attack. The window for preemption is now minimal.
- Expedite BDA & Engineering Plan (URGENT - J2/J4): Deliver a preliminary BDA and ETR for the Kamyan’ske rail lines within the next 4 hours to inform operational-level decisions on sustainment risk.
- Finalize Phased Withdrawal Plans (URGENT - J3): Direct commanders on the Pokrovsk axis to confirm and rehearse phased withdrawal plans to secondary defensive lines as a prudent measure against the MDCOA.
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.
Against the previous report from 11 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.
Report Visuals
2 visualsGeospatial Analysis
8 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 8 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Zaporizhzhia-Kamyan’ske railway station | Ukraine | 47.83928419999999, 35.13870970000001 | |
| Pokrovsk salient | Ukraine | 48.282193, 37.1847804 | |
| Kostroma GRES | Russia | 57.7677078, 40.9262609 | |
| Kostiantynivka sector | Ukraine | 48.52394289999999, 37.7075811 | |
| Kostiantynivka-Myrnohrad sector | Ukraine | 48.2962118, 37.2700035 | |
| Missile Arsenal (RF GRAU Depot) | Russia | 61.52401, 105.318756 | |
| 2652th Artillery Base (RF GRAU Depot) | Russia | 61.52401, 105.318756 | |
| Kamyan’ske road bypass | Ukraine | 48.516033, 34.6128617 |
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.
