Daily intelligence

Daily Intelligence Report

Published Intelligence Summary & Geospatial Analysis
Report number
400

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

INTELLIGENCE SUMMARY: 041400Z SEP 25

REFERENCE: Previous Daily Report 041400Z SEP 25 REPORT DATE: Thursday, September 04, 2025

1. EXECUTIVE SUMMARY

(HIGH CONFIDENCE) The operational picture has significantly changed with Russian Federation (RF) forces executing a NEW successful ground offensive westward, claiming the liberation of Novoselivka in Dnipropetrovsk Oblast and Novoselovka in Zaporizhzhia Oblast. (HIGH CONFIDENCE) Concurrently, RF has escalated its deep strike campaign with a NEW and deliberate ballistic missile strike on a humanitarian demining mission in Chernihiv Oblast. (HIGH CONFIDENCE) A NEW major escalatory event occurred with two RF drones reportedly violating Polish airspace, risking broader regional conflict.

2. CHANGES FROM PREVIOUS

  • RF Ground Offensive (SIGNIFICANT CHANGE/NEW AXIS): RF has opened a NEW westward axis of advance, moving beyond the Donetsk Oblast border. (MEDIUM CONFIDENCE) RF claims, supported by video evidence, the "liberation" of Novoselivka (Dnipropetrovsk Oblast) and Novoselovka (Zaporizhzhia Oblast). This represents a significant tactical success for RF and a major shift from the previous focus on Kupyansk and Sieversk.
  • RF Targeting Escalation (NEW TACTICAL FOCUS): RF has expanded its target set to include humanitarian operations. (HIGH CONFIDENCE) A NEW ballistic missile strike in Chernihiv Oblast deliberately targeted and killed an employee of a humanitarian demining mission. This marks a grave departure from targeting military or dual-use infrastructure.
  • NATO Border Violation (NEW ESCALATORY EVENT): (HIGH CONFIDENCE) Two RF drones reportedly violated Polish airspace during a massive overnight UAV attack. This is a NEW and significant event with high potential for regional escalation and NATO response.
  • RF Massive Air Attack (NEW SCALE & IMPACT): RF launched a NEW massive wave of 112 UAVs overnight. (HIGH CONFIDENCE) While UAF intercepted 84, the attack resulted in a NEW successful strike on critical infrastructure in Sumy, causing a power outage, and damage to an Odesa warehouse.
  • Kupyansk Axis (STATUS UPDATE): The contested situation in Kupyansk has evolved. (MEDIUM CONFIDENCE) NEW reporting from third-party sources (DeepState) now confirms RF presence and infiltration attempts within the city, partially corroborating previous RF claims and indicating a fragmented UAF defense, though UAF denies RF has "firm control."
  • UAF DIB Development (NEW CAPABILITY): (HIGH CONFIDENCE) Ukrainian company "Fire Point" announced the NEW development of domestic ballistic missiles (FP-7, FP-9) and air defense systems, signaling a significant long-term strategic development for UAF offensive and defensive capabilities.
  • UAF Tactical Innovation (NEW CAPABILITY): (HIGH CONFIDENCE) UAF has demonstrated NEW FPV drones on the Zaporizhzhia front designed to be resistant to RF Electronic Warfare (EW), indicating rapid tactical adaptation to counter prevalent RF capabilities.
  • Internal Security (NEW THREAT VECTOR): (HIGH CONFIDENCE) A NEW internal security incident was reported in Volyn Oblast, with gunfire directed at a Territorial Recruitment Center (TCC) group, indicating potential for localized resistance to mobilization efforts.

3. THREAT ASSESSMENT

  • UAF Ground Forces – Dnipropetrovsk/Zaporizhzhia Axes (THREAT LEVEL: CRITICAL - NEW): (MEDIUM CONFIDENCE on extent of RF control; HIGH CONFIDENCE on RF intent). The successful RF advance into Dnipropetrovsk and Zaporizhzhia Oblasts presents a CRITICAL threat. This new axis compromises UAF defensive lines, threatens to outflank forces in the Donbas, and places new population centers and industrial assets at risk.
  • Humanitarian & NGO Operations (THREAT LEVEL: SEVERE - NEW): (HIGH CONFIDENCE). The confirmed deliberate targeting of a demining mission elevates the threat to all non-combatant humanitarian and NGO personnel to SEVERE. RF demonstrates capability and willingness to strike these targets, severely constraining their ability to operate safely.
  • Regional Stability (THREAT LEVEL: HIGH - NEW ESCALATORY RISK): (HIGH CONFIDENCE). The violation of Polish airspace by RF drones constitutes a HIGH and immediate escalatory risk. It could trigger a NATO response, fundamentally altering the conflict's strategic calculus.
  • UAF Critical Infrastructure (THREAT LEVEL: SEVERE - SUSTAINED): (HIGH CONFIDENCE). The successful strike on Sumy's critical infrastructure, causing a power outage, reaffirms the SEVERE and persistent threat to Ukraine's energy and utility grids.
  • UAF Internal Security (THREAT LEVEL: MEDIUM - NEW): (MEDIUM CONFIDENCE). The attack on a TCC group in Volyn represents a new MEDIUM-level threat. If indicative of a wider trend, such incidents could disrupt mobilization, divert security resources, and be exploited by RF IO.

4. OPERATIONAL DEVELOPMENTS

  • Air Warfare:
    • (HIGH CONFIDENCE) RF launched 112 UAVs overnight; UAF neutralized 84. Successful RF strikes caused a power outage in Sumy, a warehouse fire in Odesa, and damage in Sloviansk and Kharkiv.
    • (HIGH CONFIDENCE) An RF ballistic missile strike targeted a humanitarian demining mission in Chernihiv Oblast, resulting in one fatality and two wounded.
    • (HIGH CONFIDENCE) Two RF drones reportedly violated Polish airspace during the overnight attacks.
    • (HIGH CONFIDENCE) All 14 Shahed UAVs targeting Odesa/Fontanka from the Black Sea were successfully intercepted by UAF air defense.
  • Ground Warfare:
    • Dnipropetrovsk/Zaporizhzhia Axis: (MEDIUM CONFIDENCE) RF forces claim the "liberation" of Novoselivka (Dnipropetrovsk) and Novoselovka (Zaporizhzhia), supported by video evidence. This indicates a NEW successful offensive west of the Donbas.
    • Kupyansk Axis: (MEDIUM CONFIDENCE) The situation remains contested, but third-party sources now confirm RF infiltration and presence in the city, suggesting UAF defenses are under severe strain.
    • Donetsk Axis: (HIGH CONFIDENCE) UAF claims to have struck an RF ammunition depot in occupied Selydove. Flames and thick smoke from the target area support this claim.
    • UAF Tactical Developments: (HIGH CONFIDENCE) UAF demonstrated FPV drones designed for EW-contested environments on the Zaporizhzhia front.
    • Internal Security: (HIGH CONFIDENCE) Gunfire was reported against a TCC group near Lutsk, Volyn Oblast.

5. INTELLIGENCE GAPS

  • CRITICAL (NEW): What is the definitive ground truth of RF control in Novoselivka (Dnipropetrovsk) and Novoselovka (Zaporizhzhia)? What is the disposition, composition, and objective of RF forces on this new axis?
  • HIGH (NEW): What were the specifics of the Polish airspace violation? Was it intentional probing or an operational error? What was the NATO/Polish response?
  • HIGH (NEW): What is the BDA for the claimed UAF strike on the RF ammunition depot in Selydove? Assess the impact on RF logistics for the Donetsk front.
  • MEDIUM (NEW): Is the attack on the TCC group in Volyn an isolated incident or part of a coordinated effort to disrupt mobilization?
  • PERSISTING: What is the definitive BDA for the RF strike on the Khmelnytskyi electronics facility and its impact on UAF DIB?

6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)

  • MOST LIKELY COA (RF GROUND): (HIGH CONFIDENCE) RF will prioritize exploiting its breakthrough into Dnipropetrovsk and Zaporizhzhia Oblasts, conducting reconnaissance-in-force to identify further weaknesses and attempt to consolidate gains. Pressure will be maintained on Kupyansk to fix UAF defenders and complete the seizure of the city. RF IO will heavily promote the "liberation" of new territories and push the narrative of Ukraine using children for sabotage to justify its actions.
  • MOST LIKELY COA (RF STRIKES): (HIGH CONFIDENCE) RF will continue large-scale UAV and missile strikes, likely targeting critical energy infrastructure as demonstrated in Sumy. Follow-on strikes against humanitarian operations are possible to create fear and disrupt aid. RF will likely test NATO air defenses along the border again, either deliberately or through operational carelessness.
  • MOST PROBABLE COA (UAF): (MEDIUM CONFIDENCE) UAF will attempt to rush reserves to the Dnipropetrovsk/Zaporizhzhia front to contain the RF advance and establish new defensive lines. UAF will prioritize deep strikes against RF logistics and C2 supporting this new offensive axis. UAF will accelerate the operational testing of its new EW-resistant FPV drones in this sector.

7. RECOMMENDATIONS

  1. Prioritize ISR for Dnipropetrovsk/Zaporizhzhia Axis: Immediately re-task all available ISR assets (UAV, IMINT, SIGINT) to determine RF force disposition, composition, and intent west of the Donetsk Oblast border. Prepare dynamic targeting packages for long-range fires to interdict RF advances.
  2. Issue Threat Warning for Humanitarian Operations: Immediately disseminate a high-priority threat warning to all humanitarian and NGO partners operating in Ukraine regarding the deliberate RF targeting of their personnel. Recommend immediate review of OPSEC, movement protocols, and physical hardening of facilities.
  3. Urgent NATO/Polish Liaison: Immediately engage with Polish and NATO intelligence counterparts to deconflict information regarding the airspace violation, understand their assessment of RF intent, and coordinate potential responses to prevent miscalculation.
  4. Accelerate Counter-EW Drone Fielding: Task relevant commands to accelerate the fielding and mass production of the newly demonstrated EW-resistant FPV drones. Prioritize their deployment to units facing the new RF offensive in Zaporizhzhia and Dnipropetrovsk Oblasts.
  5. Assess and Counter Internal Security Threats: Task SBU and National Police to conduct an urgent assessment of the TCC attack in Volyn to determine if it is an isolated event or part of a wider trend. Develop and implement enhanced security protocols for mobilization activities nationwide.

//END 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 04 Sep 2025, 14:05 UTC
Map revision comparison

Against the previous report from 03 Sep 2025, 14: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

5 visuals
Open full size
Nightwatch daily report #400: Selydove area

Geospatial Analysis

11 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 11 places with coordinates
Geocoded places in report 400
PlaceCountryLatitude, longitudeCopy
NovoselivkaUA47.9467339, 33.6070094
NovoselovkaUA47.61654000000001, 35.9986399
Chernihiv OblastUA51.4982, 31.28935
Polish airspacePL51.919438, 19.145136
SumyUA50.9077, 34.7981
OdesaUA46.4845702, 30.7326047
KupyanskUA49.7055574, 37.6027997
SelydoveUA48.1475145, 37.297136
Zaporizhzhia frontUA47.83928419999999, 35.13870970000001
Volyn OblastUA50.74723299999999, 25.325383
LutskUA50.7518548, 25.3299206

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.