Daily intelligence

UAF Strikes Belgorod Energy Node as Russian Forces Target Northern Security Infrastructure and Adapt Artillery Posture

Published Intelligence Summary & Geospatial Analysis
Report number
613

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

Strategic Overview

The Ukrainian Armed Forces (UAF) expanded their deep-strike campaign by successfully targeting a thermal power plant in Belgorod, demonstrating a sustained capability to degrade Russian border logistics. Concurrently, Russian forces are increasingly targeting Ukrainian rear-area security infrastructure in the north, evidenced by a lethal UAV strike on a Chernihiv checkpoint.

In the eastern operational zone, high wind conditions have temporarily degraded light FPV operations. This environmental constraint has prompted a tactical shift by Russian forces, who are now deploying heavy 152mm tube artillery to sustain offensive momentum along the Pokrovsk axis.

Operational Updates

  • Northern Sector (Chernihiv/Sumy/Kharkiv): A Russian UAV precision strike targeted a static security checkpoint in Novoselivka (Chernihiv Oblast), resulting in 1 military fatality and 6 injuries (5 military, 1 police). Secondary explosions at the site suggest localized ammunition or fuel storage. Russian information operations are falsely framing this as an attack on "TCK" (mobilization) personnel. In Kharkiv, a high-speed aerial target (likely ballistic) struck the city. Clear weather (9.4°C, 3.7 m/s wind) continues to facilitate high-altitude ISR. The UAF 114th Territorial Defense Brigade successfully utilized an FPV interceptor drone to down a Russian Shahed-type loitering munition.
  • Eastern Sector (Pokrovsk): Russian forces maintain high offensive pressure, specifically attacking to capture Hryshyne in an effort to widen the salient west of Pokrovsk. Due to high winds (7.4 m/s) degrading light FPV drone stability, the Russian "Tsentr" Group has deployed 152mm 2A36 Giatsint-B towed howitzers to maintain suppression on UAF strongholds. Frontline Russian Spetsnaz units in this sector report critical communication failures and severe disruptions to civilian-reliant logistics networks (such as "Ozon").
  • Southern Sector (Zaporizhzhia): Despite sustained winds (7.8 m/s) in Orikhiv, the UAF 210th Separate Assault Regiment continues systematic FPV strikes against Russian infantry and equipment.
  • Rear / Maritime Depth: UAF executed an aerial strike on an industrial thermal power plant (TЭЦ) in Belgorod, Russia. In the maritime domain, UAF naval drones successfully destroyed a Russian Raptor-class patrol boat at an unspecified port facility. In Iran, visual evidence confirmed a major fire at an IRGC space research facility in Tehran, potentially threatening the Russo-Iranian loitering munition pipeline.

SAR Intelligence (Satellite Data)

  • High Priority: The 689th Command Intelligence Center GRU (49th Combined Arms Army) registered a CRITICAL anomaly with a Z-score of -0.87, representing a significant drop below baseline activity.
  • Moderate Priority: The 8th Guards Combined Arms Army HQ registered a notable anomaly with a Z-score of +1.26, indicating an increase in localized activity.
  • Analysis: The stark activity drop at the GRU intelligence center suggests a sudden relocation of personnel or an operational stand-down. Conversely, the heightened activity at the 8th CAA HQ indicates elevated C2 coordination, likely linked to the ongoing offensive operations and localized communication breakdowns in the Eastern sector. Standard baseline activity (scores near 0) continues at over 300 other monitored installations.

Equipment & Losses

  • Confirmed Russian Loss: Raptor-class patrol boat destroyed by a UAF naval drone.
  • Confirmed Russian Loss: Belgorod thermal power plant (TЭЦ) damaged by a UAF aerial strike.
  • Confirmed Russian Loss: Six senior Russian military officers killed in combat operations (verified via OSINT visual evidence).
  • Unconfirmed UAF Loss: One M113 APC reportedly destroyed by Russian FPVs near Novoaleksandrovka.

Confidence Check

  • HIGH: UAF Belgorod TЭЦ strike; Chernihiv checkpoint strike casualties; 114th TPO Shahed interception; Raptor-class boat destruction.
  • MEDIUM: Russian C2 and logistics degradation in the Pokrovsk sector; extent of structural damage at the Tehran IRGC facility.
  • LOW: Russian claims of destroying a UAF M113; reports of Serbia lifting its arms export ban.

The Bottom Line

The UAF continues to demonstrate proficiency in multi-domain deep strikes, neutralizing maritime assets and targeting critical dual-use infrastructure in Belgorod. In the short term, expect Russian forces to exploit high winds in the Eastern sector by leveraging heavy artillery over FPVs, while sustaining opportunistic long-range UAV harassment of Northern Ukrainian security and mobilization infrastructure.

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 15 Mar 2026, 15:01 UTC
Map revision comparison

Against the previous report from 14 Mar 2026, 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 #613: Belgorod area

Geospatial 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
Geocoded places in report 613
PlaceCountryLatitude, longitudeCopy
NovoselivkaUkraine51.5305957, 31.3839338
KharkivUkraine50.00201269999999, 36.3073994
HryshyneUkraine48.31771209999999, 37.0903532
OrikhivUkraine47.5658802, 35.7876745
BelgorodRussia50.5997134, 36.5982621
TehranIran35.7218583, 51.3346954
689th Command Intelligence Center GRURussia61.52401, 105.318756
8th Guards Combined Arms Army HQRussia48.3321569, 39.9653797

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.