Daily intelligence

Intel Update: The Starlink "White List" & The Battle for Heat

Published Intelligence Summary & Geospatial Analysis
Report number
556

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

It’s -27°C out there, and the strategy is obvious: Moscow is trying to freeze Kyiv into submission while the diplomats talk in Abu Dhabi. The hit on TPP-4 wasn't just infrastructure damage; it was leverage.

But Kyiv played a smart card today. The Ministry of Defense finally implemented a "White List" for Starlink terminals. This effectively bricks any Russian-captured terminals on the frontline. Russian FPV teams and artillery spotters have been freeloading on SpaceX connectivity for months—cutting that feed severs a major nerve for them.

On the Ground and In the Air

The Starlink Blackout This is the big news. Russian channels are already screaming about lost connectivity. This hurts their ability to coordinate "Rubicon" fiber-optic drone strikes and messes up their local command and control. It’s a massive digital headache for them right when they need coordination most.

Strikes in the Russian Rear Ukraine isn't just taking hits; they sent a swarm of 95 UAVs deep into Russia. They hit the Kapustin Yar testing range (Site 105), which is where the ICBMs live. Also, the T-Bank (Tinkoff) payment system crashed. That matters because it disrupts the crowdfunding logistics for Russian volunteer supplies.

Kyiv is Freezing Mayor Klitschko confirmed TPP-4 is destroyed. Repair crews in the Darnytskyi district are racing the weather. If the water in those pipes freezes and bursts, the damage isn't a quick fix—it’s permanent.

Confusion in the South Russia claims they took Stepanovka and Staroukrainka. I’d treat that with extreme skepticism until we see visual proof. It’s chaotic down there—Russian assault groups are driving captured M113 APCs, making identification a nightmare for defenders.

Satellite Intel (SAR)

The radar imagery on the logistics hubs is flashing red.

We’re seeing a massive activity spike at the "Missile Arsenal" and the 260th Central Rocket Artillery Base. When ammo depots go from dormant to active like this, it usually means the logistics are moving from storage to transport. Historically, this signature precedes a massive missile wave by about 24 to 48 hours. Pskov Airbase is lighting up, too.

The Reality Check

What holds up: The Starlink blockade is real—confirmed by angry Russian milbloggers. The damage to Kyiv's grid is also confirmed. What’s shaky: The Russian territorial gains in the south look like single-source propaganda for now.

Final Thoughts

This next 12 hours looks ugly. The combination of the TPP-4 destruction and the depot activity suggests Moscow wants to turn the lights out completely tonight. The only silver lining is the Starlink blackout—blinding their frontline comms might buy Ukrainian defenders just enough chaos to hold the line while the skies are contested.

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

Against the previous report from 04 Feb 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 #556: TPP-4

Geospatial Analysis

7 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 7 places with coordinates
Geocoded places in report 556
PlaceCountryLatitude, longitudeCopy
TPP-4Ukraine50.4153964, 30.69359919999999
Darnytskyi District Heating & Water NetworkUkraine0, 0
Kapustin Yar Testing Range (Site 105)Russia48.5752669, 45.76617539999999
Undisclosed Missile DepotRussia61.52401, 105.318756
260th Central Rocket Artillery BaseRussia61.52401, 105.318756
Pskov AirbaseRussia57.8166994, 28.3344734
Stepanovka / Staroukrainka AreaUkraine47.6693345, 36.1448887

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.