Daily intelligence

Daily Intelligence Report

Published Intelligence Summary & Geospatial Analysis
Report number
485

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

SUBJECT: DAILY INTELLIGENCE SUMMARY – 2025-11-26 15:00:53Z

1. EXECUTIVE SUMMARY

(CRITICAL) OPERATIONAL COLLAPSE & ACTIVE STRIKE WINDOW: The operational situation on the Pokrovsk Axis has deteriorated to CRITICAL (DEFCON 2) following the failure of reserve force "CONPLAN DELTA" to deploy by the 1445Z decision point. Russian Federation (RF) forces have penetrated Pokrovsk city center (Railway Station) and are finalizing an operational encirclement of the Myrnograd corridor NLT 2025-11-26 1600Z. Simultaneously, the Most Dangerous Course of Action (MDCOA) strike window targeting Command and Control (C2) nodes in Poltava/Vinnytsia is ACTIVE NOW (as of 1500Z), supported by a massive logistics surge at GRAU arsenals. A new, high-intensity kinetic offensive has opened on the Zaporizhzhia Flank, threatening a secondary breakthrough.

2. CHANGES FROM PREVIOUS REPORT

  • Operational Phase (COLLAPSE): Shifted from "Post-Kinetic Exploitation" to "Tactical Encirclement/Collapse." The window to stabilize the T-05-15 Ground Line of Communication (GLOC) has closed; emphasis has shifted to emergency extraction (Fragmented Defense Protocols).
  • Reserve Status (FAILURE): The previous "Plan 7-B MOD" compromise has been compounded by the failure of the backup "CONPLAN DELTA" to confirm physical deployment. J3 now assumes this force is non-viable for the current engagement.
  • New Kinetic Vector (ZAPORIZHZHIA): Unlike yesterday's focus on Northern Chernihiv fixation, the primary secondary effort has shifted to the Zaporizhzhia Axis. Heavy FAB (High-Explosive Aerial Bomb) strikes on Huliaipole and the claimed capture of Zatishye indicate a widening offensive front.
  • IO Narrative (HARDLINING): RF Information Operations (IO) have pivoted from "Fake Peace Terms" (800k troop limit) to "Total Rejection of Negotiation" (Ryabkov statement) and internal destabilization via "Mindichgate" (corruption allegations), aiming to delegitimize UAF leadership during the military defeat.

3. THREAT ASSESSMENT

  • C2 Decapitation Strike (THREAT LEVEL: CRITICAL - ACTIVE): The MDCOA window is currently open (1500Z-1600Z). SAR analysis of the 260th Central Rocket Artillery Base (GRAU) shows a massive activity spike (Score 30.41 - RISING*), indicating strategic munition movement consistent with an imminent large-scale precision strike on Poltava/Vinnytsia. (HIGH CONFIDENCE)
  • Pokrovsk Encirclement (THREAT LEVEL: CRITICAL): RF forces have breached the urban center and narrowed the escape corridor to 1.5 km. Without CONPLAN DELTA, the encirclement of forward units is assessed as inevitable NLT 1600Z. (HIGH CONFIDENCE)
  • Zaporizhzhia Flank Breakthrough (THREAT LEVEL: HIGH): The unverified capture of Zatishye, combined with confirmed FAB strikes, threatens to roll up the southern flank of the Donbas defense, forcing a splitting of remaining strategic reserves.
  • Cognitive Disintegration (THREAT LEVEL: HIGH): The synchronization of "Mindichgate" corruption leaks with battlefield defeat is designed to trigger a collapse in command authority legitimacy, preventing the execution of unpopular withdrawal orders.

Legend: SAR Score 0-5 (Low/Baseline), 5-10 (Moderate), 10-25 (High), 25+ (Critical/Surge).

4. OPERATIONAL DEVELOPMENTS

  • Pokrovsk Urban Sector: Confirmed RF presence at Pokrovsk Railway Station. The T-05-15 GLOC is severed or under direct fire control.
  • Zaporizhzhia Front: Intense kinetic shaping (FAB-3000 precursors) reported in Huliaipole (1445Z). RF Ministry of Defense (MoD) claims capture of Zatishye; if true, this exposes the Dnipropetrovsk administrative border.
  • Aerial Activity: New Counter-UAV/Electronic Warfare (EW) systems (Chinese FSTH-LD radars) are being deployed by RF to neutralize UAF drone superiority. Concurrently, KAB strikes on Sumy continue to fix northern Air Defense (AD) assets.
  • Infrastructure: Confirmed catastrophic damage to Naftogaz gas infrastructure in Central Ukraine is being weaponized by RF IO to degrade civilian resilience.

5. INTELLIGENCE GAPS

  • PRIORITY 1 (CRITICAL): Status of Zatishye. Immediate verification (IMINT/SIGINT) is required to confirm if RF forces have secured this settlement, which would validate the opening of the southern operational axis.
  • PRIORITY 2 (FORCE TRACKING): Location of CONPLAN DELTA. Determine the physical location of the failed relief column to assess if they can be redirected to the Zaporizhzhia sector or defensive lines west of Myrnograd.
  • PRIORITY 3 (TARGETING): Specific Targets for 1500Z Wave. Confirmation if the active missile threat is targeting C2 nodes solely or includes the Kremenchuk logistics hub (as hinted in morning reports).

6. PREDICTIVE ANALYSIS (NEXT 24 HOURS)

  • MLCOA (Encirclement & Flanking): (HIGH CONFIDENCE) RF completes the Pokrovsk encirclement NLT 2025-11-26 1600Z, forcing UAF units into a disorganized rout. Simultaneously, RF exploits the Zatishye breach to push toward the Dnipropetrovsk border NLT 2025-11-26 2000Z, forcing UAF to strip AD from C2 nodes to cover the southern gap.
  • MDCOA (Decapitation Success): (HIGH CONFIDENCE) Utilizing the active 1500Z window, RF executes a precision strike on Poltava/Vinnytsia C2 nodes. If successful, this causes a 4-8 hour command blackout, preventing the authorization of Fragmented Defense Protocols (FDP), resulting in the total loss of forces currently in the Pokrovsk pocket.

7. RECOMMENDATIONS

  1. Air Defense (IMMEDIATE - AD COMMAND): EXECUTE "WEAPONS TIGHT". Maintain maximum alert over Poltava/Vinnytsia until 2025-11-26 1630Z. Authorize GPS jamming/spoofing immediately near C2 nodes to mitigate the active MDCOA threat.
  2. Force Management (CRITICAL - J3): ACTIVATE FRAGMENTED DEFENSE PROTOCOLS (FDP). Acknowledge CONPLAN DELTA failure. Order immediate, independent breakout/withdrawal for all units east of the Pokrovsk Railway Station to pre-surveyed defensive lines west of Myrnograd.
  3. ISR Re-Tasking (IMMEDIATE - J2): Divert tactical ISR from the stabilized Northern sector to Zatishye (Zaporizhzhia) to confirm the southern flank breach NLT 2025-11-26 1530Z.
  4. Strategic Communications (URGENT - NCA): COUNTER-CORRUPTION NARRATIVE. NCA must issue a statement NLT 2025-11-26 1600Z addressing the "Mindichgate" leaks as an RF psychological operation designed to cover their rejection of peace talks, maintaining public trust during the withdrawal.

//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 26 Nov 2025, 15:01 UTC
Map revision comparison

Against the previous report from 25 Nov 2025, 15:03 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

4 visuals
Open full size
Nightwatch daily report #485: Dnipropetrovsk ... 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 485
PlaceCountryLatitude, longitudeCopy
Pokrovsk Railway StationUA48.282193, 37.1847804
Myrnograd CorridorUA48.2962118, 37.2700035
Poltava/Vinnytsia C2 NodesUA49.58826699999999, 34.551417
260th Central Rocket Artillery Base (GRAU)UA48.379433, 31.16558
Zaporizhzhia Axis Front LineUA47.83928419999999, 35.13870970000001
HuliaipoleUA47.6607145, 36.2732384
ZatishyeUA47.8388, 35.139567
T-05-15 GLOCUA48.3648805, 37.1807516
SumyUA50.9077, 34.7981
Kremenchuk logistics hubUA49.065783, 33.410033
Dnipropetrovsk Administrative Border SectorUA48.464717, 35.046183
Central Ukraine Gas Infrastructure (Naftogaz)UA48.379433, 31.16558

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.