Daily intelligence

Intel Update: The "City-Kill" Phase Begins & Solar Flares Blind Defense

Published Intelligence Summary & Geospatial Analysis
Report number
554

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

It’s -27°C out there, and the timing is brutal. The so-called "Energy Truce" is dead. Russia has shifted tactics, timing mass infrastructure strikes to hit exactly when the freeze is deep enough to burst urban water and heating systems permanently. It’s a "City-Kill" approach—freeze the pipes, kill the city.

To complicate things, an X-class solar flare peaked today. It degraded GPS and radio signals right when they were needed most. Russian aviation seems to be timing glide bomb runs to coincide with these electronic blackouts, hitting while air defense is technically half-blind. It feels like "negotiation by fire" ahead of the Abu Dhabi talks next week.

The situation in Kharkiv is what worries me the most. Authorities are actually draining residential heating pipes to prevent them from bursting in the cold. Think about that for a second—draining the heat when it's nearly thirty degrees below zero just to save the plumbing. That is a desperate move that confirms the local grid can't sustain "keep-warm" circulation anymore. On the ground, the Russian "Sever" Group has seized Zelenoye, expanding their footprint while the city freezes.

In the Pokrovsk sector, the Russians are pulling some nasty tricks. Assault groups are using captured M113 APCs to confuse Ukrainian defenders. They’re also deploying "Rubicon" fiber-optic drones. Since these things are hard-wired, electronic warfare jamming doesn't work on them.

Down in Zaporizhzhia, the front is bending. Pridorozhne fell to the Vostok Group, and they are pushing toward the highway. To top it off, a 5.1 magnitude earthquake hit the Sea of Azov today. I can’t imagine what that felt like for the guys sitting in the trenches.

Satellite data is showing a massive spike in activity at the 260th GRAU Arsenal, while most other depots have gone quiet. In intelligence terms, that "flatline" usually means the reload phase is over; the missiles are already on the trucks. We're also seeing "Kurier" ground robots—basically remote-controlled grenade launchers—clearing trenches so Russian infantry don't have to risk their necks.

I'm not buying the reports about the destroyed Leopard tank—that looks like propaganda to boost morale—but the intent to collapse the grid is undeniable. You don't drain pipes in Kharkiv unless you have zero other options. Moscow is trying to turn the lights out before the diplomats sit down. If the solar interference keeps blinding the radar, tonight is going to be ugly for the Kharkiv-Dnipro axis.

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

Against the previous report from 02 Feb 2026, 15: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

3 visuals
Open full size
Nightwatch daily report #554: Kharkiv area

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 554
PlaceCountryLatitude, longitudeCopy
KharkivUA50.00201269999999, 36.3073994
ZelenoyeUA49.9935, 36.230383
Pokrovsk Sector (Area of Operations)UA48.282193, 37.1847804
PridorozhneUA47.8388, 35.139567
Highway leading from PridorozhneUA47.8388, 35.139567
260th GRAU ArsenalRU0, 0
Kharkiv-Dnipro AxisUA50.00201269999999, 36.3073994

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.