Daily intelligence

Daily Intel: The "Geneva Freeze" & Rear Area Chaos

Published Intelligence Summary & Geospatial Analysis
Report number
570

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 suits are talking in Geneva, but the real leverage is being built in the mud and deep in the Russian rear. Moscow tried to "set the table" for negotiations with a massive missile armada last night. Ukraine just shrugged and fired back harder—hitting targets as far out as Perm (1,600km range) and messing up a mobilization hub near Leningrad.

The weather is currently the third participant in this war. A hard freeze (-6.1°C) in the north has turned the ground into concrete, which finally opens the door for heavy armor. Meanwhile, a snowstorm in the Donbas threatens to ground the FPV drone fleets that have been holding the line. The next 24 hours aren't about diplomacy; they're about who can move fastest before the snow blinds the battlefield.

Operational Updates

Northern Front (Kharkiv/Sumy): The ground is frozen hard. The Russians secured Pokrovka, but their breakout attempt stalled at the Svinoe and Garkavsky forest belts. Keep an eye on this sector: frozen ground favors tanks, but that explosion at the Sertolovo Training Center (Leningrad district) is going to choke their reinforcement lines.

Eastern Front (Donbas): The 15th Motor Rifle Brigade looks like it's cracking internally, with reports of unrest filtering out. But the immediate threat is environmental. It's -1.4°C and snow is coming. If visibility drops, the "drone shield" protecting Ukrainian infantry evaporates. If the drones can't fly, Russian armor can creep up close without getting blown apart.

Rear Area (Strategic Strikes): Ukraine's reach is getting scary. They hit the Metafrax Chemicals plant in Gubakha (Perm Krai), targeting methanol production—which is vital for the Russian military industry. Closer to the front, Starlink is now hooked into Nova Poshta and Ukrposhta branches. Good luck jamming postal logistics now.

SAR Intelligence (Satellite Data)

The 15th Anti-Aircraft Missile Brigade (near Minsk) has spiked to an activity score of 8.56. Combined with a surge at a Navy Repair-Technical Base (Score: 15.95), this looks like a frantic scramble. That wave of 150+ Ukrainian drones overnight has forced them to move air defense assets around desperately to plug holes.

Equipment & Losses

  • Leningrad Rear: Something broke bad at the 56th District Training Center in Sertolovo. Structural collapse and 2 dead. Likely sabotage or just gross negligence.
  • Perm Krai: Confirmed hit on the methanol unit at Metafrax Chemicals.
  • New Tech: Russian forces are trying out a "Yolka" drone interceptor system. They know they are losing the UAV fight.
  • Logistics: Starlink terminals are officially whitelisted for civilian postal infrastructure.

Confidence Check

  • Sertolovo Explosion: High confidence. Even the Russian Investigative Committee admitted it.
  • "Budanov vs. Yermak" Rift: Low confidence. Looks like a Russian info-op timed for Geneva.
  • Pantsir-S1 Attrition: Unconfirmed. The claim that 50% of the fleet is gone comes from a single SBU source, so take it with a grain of salt.

Outlook

While they talk in Switzerland, soldiers in the Donbas are watching the sky turn gray. The forecasted snow is the critical variable tonight. If it grounds the FPV drones, we might finally see the mechanized push Moscow has been hoarding equipment for. Watch Pokrovsk—the freeze is here, and the armor is waiting.

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

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

5 visuals
Open full size
Nightwatch daily report #570: Svinoe and Gark... 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 570
PlaceCountryLatitude, longitudeCopy
Gubakha (Metafrax Chemicals Plant)Russia58.8389476, 57.5544263
Sertolovo Training CenterRussia60.1406406, 30.2091585
PokrovkaUkraine49.9110603, 35.2851616
Svinoe and Garkavsky Forest BeltsUkraine50.89804580000001, 34.8202098
Donbas Operational AreaUkraine48.015883, 37.80285
PokrovskUkraine48.282193, 37.1847804
Vicinity of MinskBelarus53.9006011, 27.558972
Undisclosed Navy Repair-Technical BaseBelarus53.9475861, 27.4848989
Key Nova Poshta/Ukrposhta Logistics HubsUkraine48.379433, 31.16558
Mobilization Hub near LeningradRussia60.0793208, 31.8926644

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.