Daily intelligence

Daily Intelligence Report

Published Intelligence Summary & Geospatial Analysis
Report number
488

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-29 15:00:53Z

1. EXECUTIVE SUMMARY

(CRITICAL) TACTICAL FAILURE & TECHNOLOGICAL ESCALATION: The operational situation in the Southern Sector has deteriorated from containment to localized collapse. The Russian Federation (RF) Vostok Group is exploiting the logistical strangulation of the UAF 33rd Separate Assault Regiment (33 OShP) to force a tactical breach near Stepnohorsk, shifting focus from Huliaipole. Simultaneously, RF forces have formalized a new Drone Systems Troops (BPS) doctrine, deploying Air-to-Air (A2A) capable UAVs to strip UAF of aerial reconnaissance. Strategically, RF logistics have adapted rapidly to previous deep strikes by activating alternative rail and road routes through Kazakhstan, mitigating the impact of the Caspian Pipeline Consortium (CPC) terminal damage.

2. CHANGES FROM PREVIOUS REPORT

  • Southern Front Status (DETERIORATED): Changed from "Tactical Containment" to "Localized Breach & Retrograde." The logistical failure on the Konstiantynivka Ground Line of Communication (GLOC) has forced the 33 OShP to abandon equipment and execute a defensive withdrawal; RF focus shifted from Huliaipole to Stepnohorsk.
  • Drone Warfare (NEW DOCTRINE): RF has formalized drone operations under Drone Systems Troops (BPS), moving from opportunistic use to centralized Command and Control (C2). New intelligence confirms deployment of A2A UAVs ("Geran-fighters") specifically to hunt UAF ISR platforms.
  • RF Logistics (ADAPTED): The assessment of "Logistical Severance" regarding the CPC terminal is downgraded. RF has successfully activated alternative Kazakh rail/road corridors, bypassing the damaged terminal.
  • Strategic Rear (STABILIZED): The immediate threat of massive missile saturation (Kyiv) has transitioned to a "Post-Strike Consolidation" phase, focused on thermal denial (heating infrastructure damage) rather than immediate decapitation.

3. THREAT ASSESSMENT

  • Tactical Air Superiority (THREAT LEVEL: CRITICAL): The introduction of RF A2A UAVs creates an immediate risk of "blindness" for UAF tactical units. If UAF FPV/ISR drones are neutralized, the defense at Stepnohorsk will lose fire-correction capabilities. (HIGH CONFIDENCE)
  • Stepnohorsk Encirclement (THREAT LEVEL: HIGH): The fragmentation of the 33 OShP due to supply starvation, combined with fresh RF motorized rifle assaults (37th Guards Motor Rifle Brigade), threatens to turn a tactical retrograde into an operational rout. (HIGH CONFIDENCE)
  • Logistical Resilience (THREAT LEVEL: MEDIUM): RF activation of Kazakhstan alternative routes negates the strategic shock of the UAF deep strike campaign. Without immediate interdiction of these new rail hubs, RF Vostok Group POL (Petroleum, Oil, Lubricants) stocks will stabilize within 72 hours. (HIGH CONFIDENCE)
  • Internal Destabilization (IO): RF Information Operations (IO) are aggressively targeting National Command Authority (NCA) stability, leveraging the resignation/firing rumors of key leadership (Yermak) to suggest political collapse. (HIGH CONFIDENCE)
  • Aerial/AD Disposition (SAR INDICATORS): Synthetic Aperture Radar (SAR) analysis of the 1488th Anti-Aircraft Missile Regiment shows a score of 13.88 - RISING*, confirming RF is surging AD assets to protect rear logistics hubs against UAF deep strikes.
    • Legend: SAR Score 0-5 (Low), 5-10 (Moderate), 10-25 (High), 25+ (Critical).

4. OPERATIONAL DEVELOPMENTS

  • Southern Axis Breach: RF Vostok Group has bypassed the hardened Huliaipole center to exploit the Stepnohorsk-Vremyevsky vector. Elements of the UAF 3rd Assault Brigade are deploying to establish blocking positions behind the retreating 33 OShP.
  • Technological Escalation: The 4th Guards Motor Rifle Brigade is confirmed to be integrating the new BPS doctrine, utilizing NTK Kurier UGVs for GLOC interdiction and A2A drones for airspace clearance.
  • Maritime Operations: UAF Naval Forces successfully struck the RF shadow fleet tanker Virat near the Turkish coast. This confirms UAF capability to sustain economic pressure despite RF countermeasures.
  • Logistical GLOC Failure: The Konstiantynivka GLOC is assessed as effectively closed due to "Kurier" UGV ambushes and remote mining (ISDM Zemledeliye). Supply convoys are unable to reach the 33 OShP.
  • Civilian Infrastructure: Recent RF strikes on Kyiv have successfully damaged district heating networks (Obolon/Sviatoshynskyi), enforcing a "Thermal Denial" strategy during sub-freezing conditions.

5. INTELLIGENCE GAPS

  • PRIORITY 1 (SIGINT/TECHINT): A2A UAV Specifications. Technical characteristics (frequency, guidance, payload) of the RF "Geran-fighter" drones are required to tune UAF Electronic Warfare (EW) countermeasures.
  • PRIORITY 2 (IMINT): Kazakhstan Transit Nodes. Identification of specific rail classification yards and border crossings in the Caspian/Volga region being used for the new RF POL supply route.
  • PRIORITY 3 (HUMINT): BPS C2 Nodes. Precise geolocation of the Command and Control centers for the newly formed Drone Systems Troops in the Zaporizhzhia sector to enable Hunter-Killer strikes.

6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)

  • MLCOA (Tactical Exploitation & Blindness): (HIGH CONFIDENCE) RF Vostok Group will utilize A2A UAVs to degrade UAF ISR over Stepnohorsk NLT 2025-11-30 0600Z. Under this aerial cover, and utilizing reserves replenished via Kazakh routes, they will push to overrun the 33 OShP rear guard before UAF 3rd Assault Brigade can fully consolidate the secondary defensive line.
  • MDCOA (Operational Collapse via Hybrid Shock): (MEDIUM CONFIDENCE) RF synchronizes the Stepnohorsk ground assault with a localized Starlink denial event (jamming/cyber). The resulting loss of communication prevents the 33 OShP from coordinating with the relieving 3rd Assault Brigade, leading to fratricide or encirclement, while RF IO amplifies "government collapse" narratives to freeze UAF strategic reserve commitment.

7. RECOMMENDATIONS

  1. Counter-A2A Defense (IMMEDIATE - J3/EW): INITIATE OPERATION "SKY SWEEPER". Immediately reallocate 30% of mobile C-UAS (Counter-Unmanned Aerial Systems) and EW assets from Kyiv infrastructure defense to the Stepnohorsk-Vremyevsky sector. Frontline units must be equipped with thermal detection to spot and jam RF A2A drones NLT 2025-11-29 2200Z.
  2. Counter-Logistics Strike 2.0 (URGENT - J2/J3): AUTHORIZE TRANS-BORDER TARGETING. Develop and execute deep strike packages against the newly identified Kazakh-RF rail transshipment hubs (Caspian/Volga region) NLT 2025-11-30 1200Z. The RF logistical adaptation must be broken before Vostok Group stocks are fully replenished.
  3. Stepnohorsk Stabilization (CRITICAL - J3): EXECUTE "SCORCHED EARTH" RETROGRADE. Authorize UAF 33 OShP to destroy all non-recoverable heavy equipment immediately. The priority is preserving personnel for integration with the 3rd Assault Brigade's blocking line. Deploy Hunter-Killer SOF teams to sanitize the GLOC of Kurier UGVs to facilitate casualty evacuation.
  4. Strategic Communications (IMMEDIATE - NCA): UNIFIED LEADERSHIP ADDRESS. The National Command Authority must issue a visual address NLT 2025-11-29 2000Z debunking the "Yermak Resignation" rumors and confirming the tactical plan for the South. Silence is currently acting as a force multiplier for RF IO.

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

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

4 visuals
Open full size
Nightwatch daily report #488: Huliaipole 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 488
PlaceCountryLatitude, longitudeCopy
StepnohorskUA52.3466294, 71.8798089
Konstiantynivka Ground Line of Communication (GLOC)UA48.52394289999999, 37.7075811
HuliaipoleUA47.6607145, 36.2732384
Kazakh-RF Rail Transshipment HubsKZ/RU41.934977, 50.66894500000001
1488th Anti-Aircraft Missile RegimentRU61.52401, 105.318756
Kyiv (Infrastructure Focus)UA50.4503596, 30.5245025
Obolon/Sviatoshynskyi DistrictsUA50.54672979999999, 30.4372576
Stepnohorsk-Vremyevsky VectorUA52.3466294, 71.8798089
BPS C2 Nodes (Zaporizhzhia sector)UA47.83928419999999, 35.13870970000001
Turkish CoastTR38.963745, 35.243322

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.