Daily intelligence

Daily Intel: The 1,750km Drone Strike & The "Quiet Depot" Warning

Published Intelligence Summary & Geospatial Analysis
Report number
563

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

The war has effectively turned into a race against the thermometer. With temperatures hitting -27°C, the ice is acting as a bridge for Russian infantry to bypass choke points, while simultaneous strikes on infrastructure threaten to freeze Kyiv. The hits on TPP-5 and TPP-6 were clearly timed to maximize the cold snap, though Prime Minister Shmyhal claims they can restore function within 24 to 48 hours.

The battlefield is also getting much bigger. Ukraine just demonstrated reach into the Komi Republic—about 1,750km from the border. Hitting a refinery that deep inside Russia effectively kills the idea of a "safe rear" for energy logistics.

Operational updates

Strikes deep inside Russia The SBU's strike on the Lukoil refinery in Ukhta, Komi, is a significant range expansion. We also have confirmation that the Volgograd refinery has suspended operations after yesterday's hits. The message is pretty clear: distance isn't protection anymore.

Donetsk sector The "Vostok" grouping, specifically Buryat units, is pushing hard on the Pokrovsk axis. The frozen Siverskyi Donets river is the main problem here; Russian infantry are using the ice to flank Ukrainian strongpoints, forcing defenders into close-quarters fights they'd rather avoid.

Kyiv and the north Repair crews are working on the thermal plants, but the air raid sirens aren't helping. Constant alerts for MiG-31Ks and "Oreshnik" scares are keeping air defenses saturated and slowing down the restoration work.

SAR intelligence

Nothing to report.

Equipment and losses

There are confirmed sightings of Be-12 "Chaika" amphibians operating in the Black Sea. These airframes are from the 1960s, which suggests the modern naval aviation fleet is running on fumes.

On the personnel side, reports from Tomsk indicate bailiffs are pressuring homeless people and debtors into signing military contracts to meet recruitment quotas. Meanwhile, Ukraine is formally integrating the International Legion into Ground Forces assault formations to fix command and control issues.

Assessment confidence

  • Komi refinery strike (1,750km): High. Confirmed by multiple sources including SBU.
  • Impending missile strike: High. The SAR silence at the depots combined with the freezing weather makes this the logical next move.
  • Russian "Flamingo" missile claims: Low. This reads like disinformation to justify strikes on Ukrainian production facilities.

The bottom line

The empty GRAU arsenals are the loudest signal in this report. Russia is likely racking missiles for a follow-up blow to keep Kyiv frozen while the thermal plants are down. On the flip side, the strike in Komi proves that no Russian oil facility is safe, regardless of how much snow covers it.

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

Against the previous report from 11 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

4 visuals
Open full size
Nightwatch daily report #563: Siverskyi Donet... area

Geospatial Analysis

8 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 8 places with coordinates
Geocoded places in report 563
PlaceCountryLatitude, longitudeCopy
TPP-5/TPP-6 Power StationsUA50.4503596, 30.5245025
Lukoil Refinery, UkhtaRU63.56509759999999, 53.6721055
Volgograd RefineryRU48.708048, 44.5133034
Pokrovsk Axis Area of OperationsUA48.282193, 37.1847804
Siverskyi Donets River CrossingsUA48.56872389999999, 39.3152291
23rd & 55th GRAU ArsenalsRU0, 0
Black Sea Operational AreaInternational Waters0, 0
TomskRU56.4884295, 84.9480469

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.