Daily intelligence

Daily Intel: The "Deep Freeze" Offensive & The 69-Drone Swarm

Published Intelligence Summary & Geospatial Analysis
Report number
560

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

We've officially hit the "Deep Freeze." With temperatures dropping to -27°C, the cold is doing as much damage as the artillery. Moscow is trying to freeze Kyiv by hammering the power grid, but Ukraine just fired back with a massive 69-drone swarm targeting the Russian rear—specifically Bryansk and Volgograd. They're trying to sever the logistical umbilical cord feeding the front lines.

The geopolitical pressure is ramping up, too. The US military seized the sanctioned oil tanker Aquila II in the Indian Ocean. That hits the "Shadow Fleet" right where it hurts: fuel logistics. We're watching this shift from a pure ground war to a battle for infrastructure survival. You can see it in Belgorod, where authorities are draining water systems to stop pipes from bursting. That's a sign of total municipal failure.

Operational Updates

North (Sumy/Bryansk) The "Deep Battle" is active. Ukraine sent at least 27 fixed-wing UAVs over Bryansk to starve out the Northern Grouping of Forces. In Belgorod, the infrastructure is cracking under the frost.

East (Pokrovsk/Donbas) Things are deteriorating near Pokrovsk. Russian forces are leaning heavily on high-volume artillery (152mm Giatsint-B) to support infantry assaults. I'm also seeing confirmed reports of "Gerbera" Carrier UAVs—motherships that deploy smaller FPV drones deep behind lines. That's a nasty evolution. Note that Russian claims of capturing Hlushkivka are false.

South (Zaporizhzhia/Odesa) A rare tactical win in the snow: UAF forces successfully retook Ternuvate, pushing back against the Russian creep. However, Russian aviation is still pounding the area with KAB glide bombs. The seizure of Aquila II should disrupt fuel flow to this southern theater soon.

SAR Intelligence (Satellite Data)

The data on the 260th GRAU Arsenal (Main Missile Directorate) is worrying. Activity dropped significantly (score down to 4.09 from a 7-day average of 12.63). Usually, a drop after a massive spike means the munitions have been loaded and moved out. I'd expect a missile wave in the next 24 to 48 hours.

Meanwhile, the 60th Radio-Technical Regiment is lighting up the sensors (10.17 score). Russian long-range radar is on high alert, likely hunting for that next wave of Ukrainian deep-strike drones.

Equipment & Losses

  • New Threat: The "Gerbera" mothership UAVs are validated. This extends the FPV threat range significantly.
  • Confirmed Kills: The 147th Artillery Brigade wiped out a Russian sabotage group north of Pokrovsk.
  • Logistics Hits: The Falcon Battalion (FPV units) is having a field day hunting Russian "Bukhanka" vans and transports in the snow. The Russians are struggling to move supplies with light vehicles right now.

Confidence Check

I'm confident about the scale of the Ukrainian drone swarm and the Aquila II seizure. The status of GRU Lt. Gen. Alekseev is harder to pin down; the disruption to his command is real, but his long-term condition is opaque.

I'd disregard the Russian claims of 1,000+ Ukrainian casualties in 24 hours. That looks like "victory capping"—trying to hide the embarrassment of the drone strikes.

The Bottom Line

The next 12 hours are going to be brutal for the energy grid. The "Deep Freeze" is a major factor now. Keep an eye on that 260th GRAU Arsenal data—if the ammo left the depot, the launch platforms are being loaded now. Stay warm.

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 09 Feb 2026, 15:02 UTC
Map revision comparison

Against the previous report from 08 Feb 2026, 15:02 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 #560: Pokrovsk Area 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 560
PlaceCountryLatitude, longitudeCopy
KyivUA50.0529506, 30.7667133
BryanskRU53.2635306, 34.41611
VolgogradRU48.708048, 44.5133034
BelgorodRU50.5997134, 36.5982621
Pokrovsk AreaUA48.282193, 37.1847804
HlushkivkaUA48.015883, 37.80285
TernuvateUA47.8301304, 36.1267969
260th GRAU ArsenalRU61.52401, 105.318756
60th Radio-Technical Regiment SiteRU61.52401, 105.318756
North of Pokrovsk Engagement AreaUA48.282193, 37.1847804
Indian OceanN/A0, 0

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.