Daily intelligence

Intel Update: "Moscow or Nothing" & The City-Kill Ultimatum

Published Intelligence Summary & Geospatial Analysis
Report number
549

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

The Diplomatic Front

Anyone hoping for a diplomatic breakthrough in Abu Dhabi on Feb 1 just got a reality check. Dmitry Peskov explicitly rejected neutral venues today, insisting that any meeting with President Zelensky happen in Moscow. That isn't an invitation; it’s a demand for surrender.

This confirms what looks like a "Negotiation by Fire" strategy—using kinetic brutality to force a summit on impossible terms. While the diplomats talk, the ground reality is shifting. Russia is weaponizing the "Orange Level" frost, targeting heating infrastructure in Kyiv and Kryvyi Rih. They're betting a humanitarian collapse will break Ukrainian resolve before Western aid can stabilize the grid.

On the Ground

Donbas Sector: The situation around Kostyantynivka is ugly. UAF "Phoenix" drone units are fighting off constant infiltration, and supply lines are straining. The 63rd Brigade did good work neutralizing a Russian platoon near Lyman, but I'm worried about the reports of an 80,000-man reserve in the Serebryanske Forest. While that number is unconfirmed—and frankly sounds high—the sheer volume of smoke screens suggests a major push is coming.

Southern Sector: The tech war just escalated. We now have confirmation that Russian forces are using fiber-optic guided FPV drones. Because these are hard-wired, they are immune to electronic warfare jamming, effectively neutralizing a key Ukrainian defense. Meanwhile, Vilniansk and Kryvyi Rih are taking hits from Shaheds aimed at civilian heating grids.

Rear Areas: Russia’s "Rubicon" unit claimed they killed an F-16 today. They didn't. They expended precision munitions on a mockup at Kanatovo airfield. It was a successful UAF deception operation, though the "Rezerv+" mobilization app suffering a major outage today complicates the personnel situation.

Satellite Intelligence (SAR)

The satellite imagery from the last 12 hours is flashing red. We are seeing massive activity spikes at deep-rear logistics hubs, which usually indicates a reload phase is nearly done.

  • GRAU Missile Arsenal: The activity score spiked to 30.36. This is a massive anomaly. When I see numbers this high at an arsenal, it almost always means missiles are moving from storage to launch platforms.
  • Air Defense: The 1532nd Regiment is hardening its positions. They are likely anticipating the UAF retaliation that will follow the Russian missile wave.

My read: The logistics don't lie. Russia is likely preparing a mass missile strike to coincide with the diplomatic talks on Feb 1.

Equipment & Losses

  • A Russian Su-34 fighter-bomber crashed, killing the crew. Whether it was technical failure or friendly fire, that's a significant loss for their glide-bombing capabilities.
  • Russia is officially formalizing drone warfare into a separate service branch ("Unmanned Systems Troops").
  • SpaceX and the Ukrainian MoD finally closed the loophole allowing Russians to use Starlink terminals on long-range drones.

Assessment

Ignore the noise about peace talks. You don't demand a meeting in Moscow while simultaneously loading missile arsenals unless you intend to break things. I am skeptical of the single-source report regarding 80,000 troops near Slovyansk, but the intention is clear. Watch the Kyiv energy grid over the next 48 hours. The Kremlin wants a humanitarian crisis to use as leverage, even if their targeting intelligence—evidenced by the F-16 decoy strike—is still struggling.

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

Against the previous report from 28 Jan 2026, 15:05 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 #549: Slovyansk 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 549
PlaceCountryLatitude, longitudeCopy
KyivUA50.4503596, 30.5245025
Kryvyi RihUA47.910483, 33.391783
KostyantynivkaUA48.52394289999999, 37.7075811
LymanUA48.9897585, 37.8049964
Serebryanske ForestUA48.9543976, 38.1358866
VilnianskUA47.94032259999999, 35.4328125
Kanatovo AirfieldUA48.50793300000001, 32.262317
GRAU Missile ArsenalRU (Logistics Hub)0, 0
1532nd Regiment Air Defense PositionUA (Occupied)0, 0
SlovyanskUA48.8532, 37.6053

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.