Daily intelligence

Daily Intelligence Report

Published Intelligence Summary & Geospatial Analysis
Report number
517

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-12-28 DTG: 2025-12-28T15:00Z

1. EXECUTIVE SUMMARY

(STRATEGIC PIVOT) DIPLOMATIC CULMINATION & TACTICAL WIDENING: The operational environment has reached a critical juncture defined by the high-stakes meeting between President Zelenskyy and Donald Trump (scheduled 20:00 Kyiv time). Coinciding with this diplomatic window, the Russian Federation (RF) has widened its offensive breadth, launching a new high-intensity push in Western Zaporizhzhia (Primorske) while introducing fresh regimental forces (7th Regiment) to "burn out" defenses in Kharkiv. Concurrently, the RF strategic air campaign against Naftogaz infrastructure has expanded to central logistics hubs (Poltava) and the South (Kherson TPP).

2. CHANGES FROM PREVIOUS REPORT

  • Southern Front Expansion: NEW SECTOR ACTIVATION. Previous reporting focused on Huliaipole. Current intelligence (1458Z) confirms a significant widening of the offensive to the Primorske direction (Western Zaporizhzhia), threatening a broader collapse of the southern defensive belt.
  • Pokrovsk Status: STABILIZATION INDICATORS. Contrary to previous assessments of potential collapse following the fall of Myrnohrad, UAF 7th Corps (DShV) is now confirmed holding the northern industrial sectors of Pokrovsk, establishing a temporary defensive anchor.
  • Technological Shift: NEW CAPABILITY. First confirmed tactical employment of Fiber-Optic FPV Drones by UAF (Signum Bn) in Serebryanske Forest (1416Z), successfully bypassing RF Electronic Warfare (EW). Conversely, RF has deployed "Omich" robotic platforms specifically for water crossings (1002Z).
  • Strategic Threat (Aviation): SAR SURGE. SAR analysis identifies a massive activity spike at AB Shaykovka (Score 44.37 - RISING), contrasting with the previous report's focus on the 2652nd Artillery Base. This indicates imminent heavy bomber activity.

3. THREAT ASSESSMENT

(SAR Score Legend: 0-5 Low/Routine | 5-15 Moderate/Monitor | 15+ High/Critical)

  • Strategic Aerial Strike (THREAT LEVEL: CRITICAL):
    • SAR Analysis: AB Shaykovka (Tu-22M3 base) displays a dramatic surge to Score 44.37 (RISING). Simultaneously, the 183rd Guards AA Regiment dropped to Score 0.00, suggesting it has fully deployed from garrison to operational firing positions.
    • Assessment: (HIGH CONFIDENCE) The surge at Shaykovka strongly correlates with a prepared mass-missile strike, likely timed to coincide with the Zelenskyy-Trump meeting (NLT 2025-12-28 1800Z) to exert maximum psychological pressure.
  • Riverine Breach Capability (THREAT LEVEL: HIGH):
    • Indicator: Deployment of "Omich" amphibious robotic complexes + RF 7th Regiment "clearing" operations.
    • Assessment: (MEDIUM CONFIDENCE) RF is preparing for a mechanized water crossing, likely targeting the Oskil River (Kupyansk) or waterways near Stepnohirsk to bypass blown bridges.
  • Rear Area Sabotage (THREAT LEVEL: MEDIUM):
    • Indicator: Reports of "threatening tendencies" and "sabotage/infiltration" in the Donbas tactical rear (1459Z).
    • Assessment: (MEDIUM CONFIDENCE) RF Special Operations Forces (SOF) are attempting to replicate the "blind and cut" tactics used in Pokrovsk against UAF Ground Lines of Communication (GLOCs) in the wider Donbas sector.

4. OPERATIONAL DEVELOPMENTS

  • Diplomatic/Strategic:
    • Trump-Zelenskyy Meeting: Scheduled for 20:00 Kyiv (13:00 EST). Expected output is a joint call to European leaders. RF Information Operations (IO) pre-positioning narratives of "failure."
  • Eastern Axis:
    • Pokrovsk: UAF 7th Corps (DShV) has stabilized the northern sector. RF counter-narratives claim failed UAF counter-attacks.
    • Lyman: UAF leveraging fiber-optic drones to negate RF EW superiority in forestry combat.
    • Donbas Rear: Increased risk of sabotage against C2 nodes.
  • Southern Axis:
    • Zaporizhzhia: Kinetic activity expanded to Primorske. RF using Unmanned Ground Vehicles (UGVs) west of Huliaipole to preserve infantry.
    • Kherson: Confirmed strike on Kherson Thermal Power Plant (TPP) (1425Z). Heating infrastructure critical damage expected.
  • Northern Axis:
    • Kharkiv/Kupyansk: RF 7th Regiment engaged in high-intensity "clearing," reportedly using incendiary/thermobaric munitions ("burning out"). "Omich" platforms arrived in theater.
  • Russian Rear:
    • Space: Successful Soyuz 2.1b launch (1440Z) replenished RF orbital ISR capabilities ("Lobachevsky" sat).

5. INTELLIGENCE GAPS

  • P1 (New Weapons): "Omich" Location. Urgent geolocation of the "Omich" amphibious robots is required. Are they staged for the Oskil (North) or the Dnipro tributaries (South)?
  • P2 (Enemy Order of Battle): Primorske Offensive. Identification of the RF unit conducting the new push in Primorske. Is it a rotation of the Vostok Group or a commitment of strategic reserves?
  • P3 (Infrastructure): Poltava/Kherson BDA. Battle Damage Assessment on the Poltava energy facility (0939Z) and Kherson TPP to determine rail logistics viability and heating grid islanding risks.

6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)

  • MLCOA (Diplomatic Spoiler Strike): (HIGH CONFIDENCE) Leveraging the readiness at Shaykovka AB (SAR Score 44.37), RF will launch a complex missile/drone strike targeting Kyiv and Western energy hubs between 1700Z and 2100Z today to disrupt the Zelenskyy-Trump diplomatic window and force a "crisis atmosphere."
  • MDCOA (Riverine Breakthrough): (MEDIUM CONFIDENCE) Under cover of the "spoiler strike," RF utilizes the 7th Regiment and "Omich" robots to force a crossing of the Oskil River near Kupyansk, attempting to envelop UAF units currently conducting clearing operations in the city center.
  • Secondary Prediction (IO): (HIGH CONFIDENCE) Regardless of the Miami meeting outcome, RF state media will amplify "failure" narratives and push the "Russian-Chinese Alliance" messaging (Lavrov/Taiwan statements) to deter European cohesion.

7. RECOMMENDATIONS

  1. Air Defense Alert: CONDITION RED. Activate maximum readiness for all Point Defense assets protecting Kyiv government quarters and energy hubs NLT 2025-12-28 1600Z due to Shaykovka bomber indications.
  2. Targeting Priority: HUNT "OMICH". Drone ISR teams in Kupyansk and Stepnohirsk sectors must prioritize the identification and destruction of "Omich" robotic platforms. Their destruction is a Go/No-Go criteria for preventing RF river crossings.
  3. Technology Scaling: FIBER-OPTIC DEPLOYMENT. Based on Signum Battalion's success (1416Z), immediately authorize the transfer of fiber-optic drone stocks to units facing high-density EW environments in the Pokrovsk North sector.
  4. Information Operations: PRE-BUTTAL. Release a preemptive statement highlighting the expected RF "diplomatic spoiler" strike to frame any incoming attacks as a sign of RF desperation regarding the Zelenskyy-Trump meeting, rather than a show of strength.

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

Against the previous report from 27 Dec 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 #517: Pokrovsk (North... 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 517
PlaceCountryLatitude, longitudeCopy
AB ShaykovkaRU50.71069259999999, 37.7533377
KyivUA50.4503596, 30.5245025
KharkivUA50.00201269999999, 36.3073994
PrimorskeUA47.6424248, 35.2962326
Pokrovsk (Northern Industrial Sector)UA48.282193, 37.1847804
Kupyansk Waterways (Oskil River)UA49.7055574, 37.6027997
Kherson Thermal Power Plant (TPP)UA46.635417, 32.616867
Poltava Energy FacilityUA49.58826699999999, 34.551417
Serebryanske ForestUA48.9543976, 38.1358866
Huliaipole VicinityUA47.6607145, 36.2732384

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.