Daily intelligence

Daily Intel: The "Quiet Depot" Warning & A Shift in the East

Published Intelligence Summary & Geospatial Analysis
Report number
565

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 absolutely freezing out there—temperatures are down to -27°C—and the war has turned into a brutal exchange of infrastructure strikes. Ukraine hit energy nodes in Belgorod, and Russia is pounding Odesa. This dynamic worries me; Russia is making a lot of noise about the Belgorod damage, broadcasting it extensively. To me, that looks like a setup—they’re likely using it as a pretext to hammer the Ukrainian grid in retaliation.

On the ground, the Eastern Front is shifting in ways I didn't expect. We aren't seeing just static trench defense right now; it’s turning into "encounter battles." Ukrainian units are maneuvering aggressively near Pokrovsk, bypassing Russian strongpoints rather than just holding the line. This forces the Russian "Vostok" group into mobile fights, which isn't exactly their strong suit. There are also reports that the Ivan Franko Group caught a Russian convoy trying to cross a frozen river, disrupting a flanking maneuver.

The air war is getting nasty. The strikes on Odesa are clearly timed to freeze the city and cut the grain corridor while repair crews are hamstrung by the cold. Meanwhile, air defenses around Kyiv are on high alert. We’re seeing Shahed drones taking unusual routes through Belarusian airspace, probing for gaps in the capital's shield.

But the thing that genuinely concerns me is the satellite data.

The SAR (radar) readings from the 260th Central Rocket Artillery Base have dropped off a cliff. Activity is almost non-existent compared to the monthly average. In this line of work, silence is often louder than noise. When a logistics hub goes this quiet, it usually means the munitions have already left the building and are sitting on launch platforms. At the same time, another arsenal is spiking in activity, which suggests they are frantically backfilling stock.

A few other notes: there are unconfirmed reports that a Russian colonel, Petrov Igor Igorevich, was killed by a drone near Kursk. More terrifying is the report that Russian units are using thermal-equipped UAVs to hunt personnel. Against this frozen terrain, a human body glows like a beacon.

If I had to call it, I’d say the threat of a massive missile strike is extremely high right now. The combination of the "quiet" GRAU depots, the extreme weather, and the propaganda push out of Belgorod is a classic recipe for escalation. I'm a bit more skeptical about the full extent of Ukrainian maneuver successes in the East—fog of war is thick—but the missile threat feels immediate. If you are in Kyiv or central Ukraine, the next 12 to 24 hours look dangerous.

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 13 Feb 2026, 18:38 UTC
Map revision comparison

Against the previous report from 12 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 #565: Kursk 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 565
PlaceCountryLatitude, longitudeCopy
BelgorodRU50.5997134, 36.5982621
OdesaUA46.4845702, 30.7326047
PokrovskUA48.282193, 37.1847804
Frozen River CrossingUA/Contested0, 0
Kyiv AirspaceUA50.4503596, 30.5245025
Belarusian Airspace (UAV Route)BY53.709807, 27.953389
260th Central Rocket Artillery Base (GRAU Depot)RU0, 0
KurskRU51.7482395, 36.1947023
Russian Arsenal (Unspecified)RU61.52401, 105.318756
Vostok Group PositionUA/Contested55.74670219999999, 37.5409378

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.