Daily Intelligence Report
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
SUBJECT: DAILY INTELLIGENCE SUMMARY – 2026-01-01 DTG: 2026-01-01T15:00Z AOR: Eastern Europe / Ukraine / Russian Federation Rear
1. EXECUTIVE SUMMARY
(CRITICAL WARNING) SATURATION STRIKE IMMINENT: All indications point to a massive Russian Federation (RF) aerial offensive commencing NLT 2026-01-01T1900Z. The 260th GRAU Arsenal logistics activity has spiked to an unprecedented Score 48.22 (CRITICAL), nearly doubling yesterday's high, confirming the staging of heavy munitions. While Ukrainian Armed Forces (UAF) successfully executed deep strikes into Tatarstan (~1,000km) and exposed RF intelligence failures regarding the RDK commander, the RF has established a specific "retaliation" narrative centered on the "Tarasovka/Khorly" incidents to justify targeting Ukrainian energy and decision-making centers tonight.
2. CHANGES FROM PREVIOUS REPORT
- Logistics Indicators: SIGNIFICANT ESCALATION. The Synthetic Aperture Radar (SAR) score for the 260th GRAU Arsenal surged from 27.24 (yesterday) to 48.22 today. This represents the highest recorded logistics throughput in recent reporting, indicating maximum missile loading.
- Myrnohrad Status: CLARIFICATION. Yesterday's assessment of "probable seizure" has been revised to CONTESTED/GREY ZONE. RF sources report engaging UAF reconnaissance groups attempting to raise flags, confirming the city center is not fully under RF control.
- Hybrid Threat: VECTOR SHIFT. The hybrid threat has moved from maritime (cables) to logistics/transit. An Improvised Explosive Device (IED) was neutralized on the Budapest-Kyiv international train (1356Z), signaling a direct threat to Western ground lines of communication (GLOC).
- Counter-Intelligence: SUCCESS. The "assassinated" RDK Commander Denis Kapustin has been confirmed alive by UAF Main Directorate of Intelligence (HUR), exposing a failed RF FSB/GRU liquidation plot.
3. THREAT ASSESSMENT
(SAR Score Legend: 0-5 Low/Routine | 5-15 Moderate/Monitor | 15+ High/Critical)
- Strategic Aerial Strike (THREAT LEVEL: CRITICAL)
- Indicators: 260th GRAU Arsenal (Score 48.22); AB Voronezh Malshevo (Score 25.74); Multi-vector UAV ingress (Chernihiv, Sumy, Zaporizhzhia) currently acting as pathfinders; "Retaliation" narrative established via RF MFA.
- Assessment: (HIGH CONFIDENCE) A coordinated strike package involving Shahed OWA-UAVs (One-Way Attack Unmanned Aerial Vehicles) followed by Kalibr/Kh-101/Iskander missiles will target the Kyiv energy ring and potentially the Odesa port infrastructure between 1800Z and 0200Z.
- Ground Offensive - Eastern Ukraine (THREAT LEVEL: HIGH)
- Indicators: RF tactical aviation launching Guided Aerial Bombs (KAB) against the Dnipropetrovsk administrative border; deployment of "Kurier" Unmanned Ground Vehicles (UGV) to support infantry.
- Assessment: (MEDIUM CONFIDENCE) RF forces are attempting to bypass the stalled urban fight in Myrnohrad by pushing the Dobropillia salient and widening the breach toward the Dnipro oblast border.
- Hybrid/Sabotage (THREAT LEVEL: RISING)
- Indicators: IED on Budapest-Kyiv train; claimed strikes on Volyn energy infrastructure.
- Assessment: (MEDIUM CONFIDENCE) RF Special Services are activating assets to disrupt Western aid corridors and energy transit in Western Ukraine to complicate logistics during the New Year transition.
4. OPERATIONAL DEVELOPMENTS
- Deep Strike Campaign (Blue Force):
- Strategic Reach: UAF conducted a strike on Almetyevsk, Tatarstan (~1,000km range), hitting the "Severny Tovarny Park" oil facility.
- Refinery Impact: Confirmed strikes on Ilsky Refinery (Krasnodar) and Lyudinovo oil depot (Kaluga).
- Battlefield Technology:
- UAF Adaptation: Confirmed use of Yak-52 trainer aircraft and dedicated "anti-aircraft drones" to intercept RF reconnaissance UAVs (BM-35), preserving high-value AD missiles.
- RF Innovation: First confirmed sighting of "Kurier" UGVs on the frontline, likely used for logistical resupply or mine-clearing to mitigate high infantry attrition.
- Information Operations (Red Force):
- Narrative Pretext: RF state media is aggressively promoting the "Tarasovka Incident" (alleged UAF strike on a civilian vehicle with child casualties) and "Khorly Cafe" strike as a casus belli for the upcoming missile barrage.
- Northern Axis:
- Kharkiv/Sumy: Intense KAB bombardment recorded on the Feldman Eco Park and Sumy staging areas. RF is finalizing preparations for a potential January offensive targeting Vovchansk and Lyman.
5. INTELLIGENCE GAPS
- P1 (Tech Capabilities): "Kurier" UGV Payload. Is the newly sighted UGV platform armed (suicide/suppression) or purely logistical? This determines the engagement rules for frontline FPV (First Person View) operators.
- P2 (Forensics): Tarasovka Incident. Urgent need to determine if the explosion in Tarasovka was a UAF errant strike, an RF false flag (IED), or unrelated ordnance. This is critical for countering the RF "retaliation" narrative.
- P3 (Hybrid): Train Sabotage Attribution. Was the IED on the Budapest-Kyiv train placed by a local partisan cell or an infiltrated GRU asset? This impacts rear-area security protocols for Western aid.
6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)
- MLCOA (Saturation Strike): (HIGH CONFIDENCE) Commencing NLT 1900Z, RF will launch a saturation strike. Shahed waves (currently entering airspace) will attempt to deplete Mobile Fire Group ammunition. Main effort will be cruise missile strikes on Kyiv (decision centers), Lutsk/Volyn (logistics), and Odesa (energy). RF ground forces in Pokrovsk will launch spoiling attacks to fix UAF units during the bombardment.
- MDCOA (Zaporizhzhia Breakthrough): (MEDIUM CONFIDENCE) Utilizing the diversion of the air campaign, RF forces launch a mechanized push in the Zaporizhzhia/Bilohir'ya sector (where KABs were active at 0400Z) to exploit the "grey zone" confusion and breach the secondary defensive line.
7. RECOMMENDATIONS
- Air Defense Optimization: TRIGGER: Immediate. ACTION: All static AD systems (Patriot/SAMP-T) hold fire on UAV targets; authorize Yak-52 and Mobile Fire Groups (MFG) for all Subsonic/UAV threats. Preserve interceptors for Ballistic/Cruise threats expected post-1800Z.
- Strategic Communications: TRIGGER: Immediate. ACTION: Pre-emptively release intelligence regarding the "Tarasovka" incident forensics (if favorable) or highlight the "False Flag" nature of the narrative to international partners to blunt the RF justification for tonight's strikes.
- Rail Security Alert: TRIGGER: Immediate until 2026-01-04. ACTION: Suspend non-critical civilian traffic on the Budapest-Kyiv line; deploy K-9 and engineering teams to sweep all culverts and bridges on the Western GLOC.
- Tactical ISR: TRIGGER: Daylight 2026-01-02. ACTION: Task high-resolution imagery to Myrnohrad city center to confirm the "Grey Zone" status and identify if the 33rd GMRR (RF) has hardened positions.
//END OF REPORT//
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 31 Dec 2025, 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.
Report Visuals
5 visualsGeospatial Analysis
15 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 15 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| 260th GRAU Arsenal | RU | 55.1802364, 50.7263945 | |
| AB Voronezh Malshevo | RU | 51.6869563, 39.1083952 | |
| Kyiv Energy Ring | UA | 50.0529506, 30.7667133 | |
| Odesa Port Infrastructure | UA | 46.4852408, 30.7480612 | |
| Dobropillia Salient | UA | 48.4691324, 37.0871223 | |
| Myrnohrad City Center | UA | 48.2962118, 37.2700035 | |
| Zaporizhzhia/Bilohir'ya Sector | UA | 47.52617739999999, 35.9992804 | |
| Budapest-Kyiv GLOC (Rail Segment) | UA | 50.4503596, 30.5245025 | |
| Lutsk Logistics Node | UA | 50.7518548, 25.3299206 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Ilsky Refinery | RU | 44.8460025, 38.5603309 | |
| Lyudinovo Oil Depot | RU | 53.8619036, 34.4444084 | |
| Almetyevsk Oil Facility | RU | 54.9013725, 52.2969552 | |
| Vovchansk | UA | 50.284234, 36.9329429 | |
| Sumy Staging Areas | UA | 50.9077, 34.7981 |
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.
