Daily Intel: The 123-Drone Swarm & The "Silent" Signal
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
Analyst briefMachine-generated narrative. Labels inside it are written by the model. How to read these labels
Strategic Overview
We're seeing a major shift in tempo. Ukraine just sent a massive wave of over 120 drones deep into Russia, hammering logistics hubs in Moscow and Vladimir. It looks like a race to disrupt supply lines before the blizzard shuts down transport.
Ukrenergo is scheduling blackouts starting tomorrow. They aren't saying it explicitly, but this feels like pre-emptive defense—they know a retaliatory missile strike is coming.
The weather is currently the biggest variable. It's just above freezing (0.9°C) in Kharkiv. Once that drops and the mud freezes into concrete, the heavy armor is going to start moving.
Operational Updates
- Zaporizhzhia: The situation near Huliaipole is bad. Video confirms the 218th Tank Regiment has taken Tsvetkovoye. The Russian push stalled out after capturing the village, but the breach exposes the defensive lines. To make matters worse, high winds (6.7 m/s) are grounding our defensive drones.
- Donbas: Fighting has reached the streets of Myrnohrad. The 79th Air Assault Brigade is running "search-and-strike" ops to clear Russian infantry filtering into the outskirts. Further south in Pokrovsk, the ground is already freezing (4.3°C), which means Russian armor is moving faster.
- Deep Strike: That 123-drone swarm specifically targeted the distribution network for the 260th GRAU Arsenal. The goal is pretty clear: starve the Russian "Sever" group of ammo before the storm messes up their logistics.
SAR Intelligence (Satellite Data)
The data from the 1st Anti-Aircraft Missile Regiment HQ is worrying. We saw a massive spike in activity recently, but today the score crashed to 1.70—way below the weekly average. When a unit goes dark like this after a burst of activity, it usually means they're done shuffling assets and are in position to launch.
Losses & Tech
- Strikes: Ukraine landed 12 confirmed hits on Russian infrastructure out of that 123-drone wave.
- Defense: Russian air defense is porous right now. Conversely, while we intercepted 55 Shaheds overnight, 25 still got through to hit infrastructure in Dnipropetrovsk and Kharkiv.
- Tactical: FPV operators near Pokrovsk had a good run, wiping out a squad of 12 Russians in a single engagement.
Assessment
I'm treating the Tsvetkovoye capture and the scale of the drone swarm as confirmed facts. The reports about Russians switching to the "MAX" comms platform because they don't trust Telegram are plausible, but I haven't seen hard proof yet.
The Bottom Line
The silence at the Russian missile HQs combined with the scheduled blackouts tells me a coordinated strike is hours away. Keep a close watch on the Zaporizhzhia sector. If the 218th pushes past Tsvetkovoye once the ground hardens, the southern defense is going to fracture.
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.
Against the previous report from 14 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.
Report Visuals
4 visualsGeospatial Analysis
11 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 11 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Moscow | RU | 55.7568721, 37.6150527 | |
| Vladimir | RU | 56.1428026, 40.3895795 | |
| Kharkiv | UA | 50.00201269999999, 36.3073994 | |
| Huliaipole Sector | UA | 47.6607145, 36.2732384 | |
| Tsvetkovoye | UA | 47.8388, 35.139567 | |
| Myrnohrad | UA | 48.2962118, 37.2700035 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| 260th GRAU Arsenal Distribution Network | RU | 61.52401, 105.318756 | |
| 1st Anti-Aircraft Missile Regiment HQ | RU | 61.52401, 105.318756 | |
| Dnipropetrovsk | UA | 48.464717, 35.046183 | |
| Zaporizhzhia Sector Command Area | UA | 47.83928419999999, 35.13870970000001 |
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.
