Daily intelligence

Russian 128-UAV Overnight Saturation Assault and Ukrainian Counter-Strikes on Occupied Crimea Drone Infrastructure

Published Intelligence Summary & Geospatial Analysis
Report number
774

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
to
Claim records by status
8 records: 6 Single-source claim, 2 Official claim.
Claim records by confidence
0 HIGH, 8 MEDIUM, 0 LOW.
SAR measurements
None supplied to this report. No SAR measurements for this period does not mean that monitored sites were unchanged.
Frontline map data
Newest map data is 20.3 h older than this report.

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

In the last 24 hours, the most significant verified operational change is a large-scale Russian unmanned aerial vehicle (UAV) saturation assault and confirmed Ukrainian strikes on Russian drone infrastructure in occupied Crimea and Kherson. The Ukrainian Air Force reports 128 strike UAVs launched overnight (18:00 16 Aug – 08:30 17 Aug UTC) from Kursk, Orel, Primorsko-Akhtarsk, and temporarily occupied Donetsk. 106 targets were shot down or suppressed, with 14 confirmed impact locations and 2 debris fall zones. This represents a sustained escalation of the Russian aerospace campaign, shifting emphasis from the previous day's concentrated Dnipropetrovsk industrial strikes to a broader multi-axis barrage across at least nine oblasts.

The Ukrainian General Staff confirmed coordinated strikes on Russian drone launch/storage and ground-control infrastructure in occupied Crimea and Kherson, including the Hvardiiskyi launch/storage site, an Orion ground control station in Novofedorivka, a Geran/Gerbera relay in Olenivka, and a communication/power node on Tendrivska Spit. Updated damage assessments also indicate the Kombynat Kamensky solid-fuel plant in Rostov Oblast sustained 2 workshops destroyed and 4 damaged — a continuation of the previous day's strike. Ground lines remain static; all Russian territorial claims in the reporting window remain unverified.

Operational Updates

  • Kharkiv / Lyman / Kupiansk: Kharkiv Oblast sustained an overnight mixed assault comprising 1 KAB, 2 Geran-2, 3 Molniya, 2 FPV, and 35 unidentified drones. Six civilians were injured in Izium and Zlatopil; infrastructure damage was confirmed across Bohodukhiv, Kupiansk, Izium, Kharkiv, and Lozova districts. Lozova transit point processed 78 evacuees. UAF repelled 17 assaults in South Slobozhansky direction near Liman, Kozacha Lopan, Izbytske, Okhrimivka, Kruhloho, and Dvorichanske, plus 3 assaults near Kupyansk/Kurylivka/Novoplatonivka. Positions held. Near Lyman/Kupiansk, contact persists with no verified change; a Russian 27th Separate Guards Motor Rifle Brigade video claiming drone interception/EW was assessed as inflated/low confidence due to visual mismatch.

  • Donetsk / Pokrovsk / Kostiantynivka: The UAF General Staff reports 236 combat clashes in the previous 24-hour cycle, with high attrition concentrated on Pokrovsk/Kostiantynivka. The 3rd Special Operations Forces Regiment claimed a combined-arms clearing operation in Andriivka-Klevtsove, Donetsk Oblast, with approximately 30 Russian personnel captured; independent geolocation pending. Pro-Russian claims of a >600 m advance across the Kazenny Torets River toward Krasny Kut and liberation of Andriivska Obshchyna remain unverified. Command restructuring proposals target this sector: appointment of Brigadier General Serhii Sobka as Deputy Commander-in-Chief and transfer of Emiliia Ishkulova to command the 11th Army Corps responsible for Kramatorsk/Sloviansk.

  • Zaporizhzhia / Orikhiv: Zaporizhzhia Oblast saw a reactive Geran strike on an AZS fueling station in Zaporizhzhia and FPV/drone strikes on a bread delivery vehicle and residential fire in Bileneke Pershe (no casualties). KAB glide bombs and a missile vector from the east were tracked; air raid alerts were repeatedly declared and reversed. Pro-RF claims of capturing Novosoloshyne by the 39th MRB and a 24.2 km² territorial gain remain unverified, assessed as propaganda/inflated. UAF defensive lines holding.

  • Dnipropetrovsk / Kryvyi Rih: A strike on Bohdanivka community, Pavlohrad Raion, killed one civilian (52M), injured one (47M), and caused a fire at an industrial enterprise. A confirmed strike on an industrial facility in Kryvyi Rih caused damage with no casualties. Reactive UAV vectors were tracked toward Kryvyi Rih and Pavlohrad; metallurgical facilities continue operating despite harassment. Russian MoD claims of UAV warehouse strikes in the region remain unconfirmed.

  • Odesa / Mykolaiv / Kherson: The SBU detained a 27-year-old female operative in Odesa tasked with planting three IEDs near administrative buildings; modified fragmentation casings and detonating phones were seized. An explosion near Langeron Beach in Odesa was captured on video; origin and weapon type unconfirmed. Multiple X-31P cruise missiles were tracked toward Chornomorsk and Odesa, and a residential building in Chornomorsk sustained roof destruction and fire; suspected cruise missile but munition type unverified. A loitering munition ("Bandrol") originating from Odesa region airspace crossed into Moldova and reportedly impacted ~30 km from the border — a significant cross-border trajectory incident. Mykolaiv Oblast saw a reactive jet UAV heading north and a Shahed-type drone departing Kinburn Spit toward Ochakiv. Romanian MoD reports >100 drone attacks on Danube ports in recent days.

  • Sumy / Chernihiv / Northern Border: A confirmed Russian strike on Sumy killed 2 civilians and injured 1, with residential and non-residential structural damage. UAV vectors from Kursk were tracked toward Sumy. Chernihiv Oblast saw reactive UAVs from Bryansk along the Belarus border; an energy facility hit caused power outage for >10 subscribers and 1 injury earlier in the reporting window.

  • Crimea / Rostov / RF Interior: UAF General Staff confirmed strikes on Russian drone infrastructure in occupied Crimea/Kherson: Hvardiiskyi launch/storage site (fire confirmed), Orion ground control station in Novofedorivka, Geran/Gerbera relay in Olenivka, and communication/power node on Tendrivska Spit. Sevastopol declared air raid alerts. The Kombynat Kamensky solid-fuel plant in Kamensk-Shakhtinskaya sustained 2 workshops destroyed and 4 damaged, halting propellant production.

  • Moscow / Belgorod / Russian Rear: Commercial imagery confirmed total structural collapse of the Wildberries Kolodino logistics hub (~229,500 m² footprint). Belgorod Oblast governor claimed 152 overnight attacks and 8 civilian fatalities, including 6 in Koloskovo, but these figures are assessed as inflated/low confidence. Satellite imagery confirmed industrial-scale expansion of a Geran droneport in Tsymbulovo, Oryol Oblast, with ≥15 launch pads for Geran-4/5 UAVs, hangars, and solar arrays — indicating sustained Russian drone campaign capacity growth.

Deep Strikes & Air Defense

  • Russian Aerospace/Maritime Campaign: The overnight barrage comprised 128 strike UAVs (Shahed incl. jet-powered variants, Gerbera, Parodia imitators) from Kursk, Orel, Primorsko-Akhtarsk, and TOT Donetsk; 106 intercepted/suppressed, 14 impacts, 2 debris falls. Additional tracked threats included KAB glide bombs, X-31P cruise missiles toward Odesa, reactive jet UAVs, and loitering munitions; a Tu-22M3 strategic bomber operated in the Black Sea with potential Kh-22 missile threat. Russian MoD claims of 13 Naftogaz strikes, A-50U-enabled Flamingo interceptions, and Su-34 strikes on command posts remain unconfirmed/low confidence.

  • Ukrainian Deep Strikes: Confirmed UAF General Staff strikes on Russian drone infrastructure (Hvardiiskyi, Novofedorivka, Olenivka, Tendrivska Spit) and the Kamensky Combine (2 workshops destroyed, 4 damaged). The Wildberries Kolodino hub collapse is confirmed. Unverified claims persist regarding the first use of UK-manufactured Nyan drones against Russian refineries and the use of new domestically produced "Dovbush T40" strategic UAV and "Vyrivnyuvach" guided aerial bomb; specifications remain unconfirmed.

  • Air Defense Status: UAF air defense engaged across multiple oblasts, with reported interception of 106 of 128 UAVs. Civil defense managed recovery operations. Dempster-Shafer analytics continue to reflect moderate uncertainty, reinforcing reliance on confirmed interception telemetry over open-source claims.

SAR Intelligence (Satellite Data)

  • Imagery Review: No validated exact-track SAR measurements available from imagery acquired in the last 24 hours.
  • Assessment: Nothing significant to report.

Equipment & Losses

  • Russian: Confirmed UAF strikes disabled Russian drone infrastructure: launch/storage site near Hvardiiskyi, Orion ground control station in Novofedorivka, Geran/Gerbera relay in Olenivka, and communication/power node on Tendrivska Spit. The Kamensky Combine solid-fuel plant is a defense-industrial target, not a direct equipment loss. UAF preliminary claims of 36 Russian personnel killed and 10 wounded in the Pokrovsk direction were reported but unverified.

  • Ukrainian: No confirmed Ukrainian military equipment losses in the reporting window. Unconfirmed: Pro-RF claim that the 1st Tank Army destroyed a British L-119 howitzer and a Canadian LAV-25 "Coyote" IFV; RF MoD-aligned channels claim 1,450 Ukrainian personnel losses overnight, assessed as inflated/low confidence.

Confidence Check

  • HIGH: Russian 128-UAV overnight barrage with 106 intercepted/suppressed (UAF official).
  • HIGH: Sumy strike killed 2 civilians, injured 1.
  • HIGH: UAF confirmed strikes on Russian drone infrastructure in occupied Crimea/Kherson.
  • HIGH: Kamensky Combine strike updated damage: 2 workshops destroyed, 4 damaged.
  • MEDIUM: Odesa residential strike and cross-border loitering munition into Moldova (tracking high, impact location medium).
  • MEDIUM: SBU Odesa IED plot neutralization.
  • MEDIUM: Andriivka-Klevtsove clearing operation and ~30 POWs.
  • UNCONFIRMED: Territorial claims at Novosoloshyne, Krasny Kut, Kudievka, Pershomariivka, and Orikhiv.
  • UNCONFIRMED: RF MoD claims of 13 Naftogaz strikes, A-50U interceptions, 1,450 UAF losses, Belgorod casualty figures.
  • UNCONFIRMED: Specifications/combat readiness of Dovbush T40 and Vyrivnyuvach systems.
  • UNCONFIRMED: DroneSec/Telegraph claim of 59 new Russian long-range drone launch tracks.
  • UNCONFIRMED: L-119/LAV-25 destruction claim and Ukrainian use of UK-manufactured Nyan drones.

The Bottom Line

The conflict continues to feature mutual deep-strike and counter-logistics warfare with a static ground front. Russia sustained a high-volume, multi-axis UAV/KAB/missile saturation campaign overnight, while Ukraine expanded confirmed strikes to Russian drone infrastructure in occupied territories and updated damage to the Kamensky solid-fuel plant. The cross-border loitering munition trajectory into Moldova introduces a potential regional spillover incident.

Watch items for the next 24 hours:

  1. Diplomatic/regional fallout from the Moldovan airspace breach and any formal response from Chișinău.
  2. Follow-on Ukrainian strikes against Russian drone launch sites and the operational impact of the Tsymbulovo droneport expansion.
  3. Verification of UAF SSO claims at Andriivka-Klevtsove and any Russian territorial assertions near Krasny Kut or Novosoloshyne.
  4. Official confirmation of personnel restructuring (Sobka/Ishkulova) and its effect on Kramatorsk/Sloviansk defense tempo.
  5. Continued Russian missile/drone waves, given optimal weather conditions (clear skies, light winds, zero precipitation at frontline reference points).

Follow-up investigation

Inconclusive

Machine-run follow-up on one selected claim record. Sources listed include material that was retrieved and not used. How to read these labels

Question

Did a drone strike damage the entrance of the Annino metro station and a public bus in Moscow on 17 August 2026, causing three casualties, and has any official Russian source confirmed or denied the incident?

Go to the claim record this investigation examined

Answer

A single SOTA video documents physical damage to the Annino metro station entrance and a public bus in Moscow, but the drone strike cause, three casualties, and any official Russian confirmation/denial are not independently verified in the frozen evidence pack. The exact incident date is also not established; the source was published on 17 August 2026 but describes the damage as occurring the previous day.

Findings

  • ConfirmedMedium confidence

    SOTA video footage shows physical damage to the Annino metro station entrance and a public bus in Moscow.

    Based solely on a single Telegram source (SOTA) with video analysis. The footage shows shattered glass at the metro entrance and bus window damage with a protruding object, but does not show the strike itself. No independent corroboration or geolocation metadata.

    Sources named for this finding: [4] SOTA, [27] SOTA, [26] SOTA, [25] SOTA

  • InconclusiveLow confidence

    The observed damage was caused by a drone strike.

    SOTA reports the damage as following a reported drone strike, but no independent evidence or official confirmation establishes the cause. The video only shows aftermath; it does not capture the impact.

    Sources named for this finding: [4] SOTA, [27] SOTA

  • InconclusiveLow confidence

    The incident caused three casualties.

    SOTA cites Moscow Mayor Sergei Sobyanin as confirming three casualties, but the official statement is not present in the evidence pack and no independent casualty reporting exists. This is hearsay, not direct confirmation.

    Sources named for this finding: [4] SOTA

  • InconclusiveLow confidence

    An official Russian source has confirmed or denied the incident.

    The evidence pack contains no direct statement from any official Russian source (e.g., Mayor Sobyanin, Russian MoD, EMERCOM) addressing the Annino incident. The only mention of Sobyanin is through SOTA's attribution, which is not official confirmation. Absence of evidence in this pack is not proof of denial.

    Sources named for this finding: [4] SOTA, [27] SOTA

  • InconclusiveLow confidence

    The drone strike occurred on 17 August 2026.

    The SOTA source was published on 17 August 2026, but its analysis states the damage is attributed to a drone strike 'the previous day' (likely 16 August). Raw observation fields for event_time_start and event_time_end are empty, with time_precision UNKNOWN.

    Sources named for this finding: [4] SOTA

Remaining gaps

  • No independent corroboration from official Russian sources or additional OSINT for the Annino incident
  • Exact date and time of the strike not established
  • Casualty figure not independently verified

Investigation sources (29)

28 of 29 sources have no stored URL and cannot be opened from this page.

  • External web page: 1, of which 0 without a URL
  • Source observation behind a claim record: 8, of which 8 without a URL
  • Nightwatch archive item: 20, of which 20 without a URL

The generator placed these sources in 19 groups. Sources with the same group number were treated as one origin. Different group numbers do not establish that sources are independent of each other.

Named by a finding or the answer (4)

  1. [4]Drone strike damages Moscow metro station entrance and public bus in Anino district, causing three casualties.SOTA
    No URL storedSource observation behind a claim recordGroup 4Published Retrieved

    Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district.

  2. [25]Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district.SOTA
    No URL storedNightwatch archive itemGroup 16Published Retrieved

    Title: Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district. Analysis: Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district.

    Full stored excerpt

    Title: Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district. Analysis: Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district.

  3. [26]Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district.SOTA
    No URL storedNightwatch archive itemGroup 16Published Retrieved

    Title: Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district. Analysis: Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district.

    Full stored excerpt

    Title: Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district. Analysis: Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district.

  4. [27]Nightwatch content 93722SOTA
    No URL storedNightwatch archive itemGroup 17Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district. **Key Observations:** - **Location & Context:** The caption identifies the location as the vestibule of the 'Anino' metro station in the Southern Chertanovo

    Full stored excerpt

    Video documentation of damage to a Moscow metro station entrance and a public bus following a reported drone strike in the Anino district. **Key Observations:** - **Location & Context:** The caption identifies the location as the vestibule of the 'Anino' metro station in the Southern Chertanovo

Retrieved, not named by any finding (25)

  1. [1]Strike by a reactive Geran drone on an oil depot in ZaporizhzhiaColonelcassad
    No URL storedSource observation behind a claim recordGroup 1Published Retrieved

    On video, a strike by a reactive Geran on an AZS in Zaporizhzhia.

  2. [2]Russian strikes on Naftogaz energy infrastructure causing equipment damage and reduced production.Операция Z: Военкоры Русской Весны
    No URL storedSource observation behind a claim recordGroup 2Published Retrieved

    - **Caption Corroboration:** The Russian caption confirms the Ukrainian text, stating that the Russian Army struck 13 'Naftogaz' objects in a week using missiles and drones across various Ukrainian regions.

  3. [3]Russian attack on port infrastructure damaged civilian vessel and injured fourСевер.Реалии
    No URL storedSource observation behind a claim recordGroup 3Published Retrieved

    Глава Одесской ОВА Олег Кипер сообщил, что ночью российская армия снова атаковала портовую инфраструктуру, повреждено гражданское судно под флагом Того. Пострадали четыре человека, трое из которых доставлены в больницу.

  4. [5]Russian FPV drone strike damaged a vehicle transporting bread in Bilenke.🇺🇦 Запорізька обласна військова адміністрація 🇺🇦
    No URL storedSource observation behind a claim recordGroup 5Published Retrieved

    росіяни атакували fpv- дроном авто, що везло хліб мешканцям Біленького.

  5. [6]Russian forces struck logistics centers, energy objects, and transport targets of the Ukrainian Armed Forces.Дневник Десантника🇷🇺
    No URL storedSource observation behind a claim recordGroup 6Published Retrieved

    🪖 ВС РФ за сутки поразили логистические центры, объекты энергетики и транспорта ВСУ;

  6. [7]Shipment moved into Moldova territory.Николаевский Ванёк
    No URL storedSource observation behind a claim recordGroup 7Published Retrieved

    бандероль ушла на территорию Молдовы

  7. [8]UAVs reported approaching Zaporizhzhia from the south.Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
    No URL storedSource observation behind a claim recordGroup 8Published Retrieved

    🛵 БпЛА на Запоріжжя з півдня.

  8. [9]Nightwatch content 27914MoD Russia
    No URL storedNightwatch archive itemGroup 9Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    [Video message] Caption: 💥 Air surveillance posts of the Tsentr Group of Forces repelled an AFU strike drone attack over the territory of the Donetsk People's Republic. 🔹 Russian Defence Ministry

  9. [10]Nightwatch content 20123MoD Russia
    No URL storedNightwatch archive itemGroup 9Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    [Video message] Caption: The Zapad Group's Pantsir-S crews protect the sky around the clock in their area of responsibility. 💥 During the duty, the servicemen detected and destroyed an enemy drone. 🔹 Russian Defence Ministry

  10. [11]Nightwatch content 526MoD Russia
    No URL storedNightwatch archive itemGroup 9Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    [Video message] Caption: Successful ramming of enemy's Baba Yaga. Sever Group of Forces drone teams are on round-the-clock duty in the sky above Kharkov region and detect hostile strike drones. 💥Objective control footage demonstrates elimination of another Baba Yaga unmanned aerial vehicle.

    Full stored excerpt

    [Video message] Caption: Successful ramming of enemy's Baba Yaga. Sever Group of Forces drone teams are on round-the-clock duty in the sky above Kharkov region and detect hostile strike drones. 💥Objective control footage demonstrates elimination of another Baba Yaga unmanned aerial vehicle.

  11. [12]Nightwatch content 17064MoD Russia
    No URL storedNightwatch archive itemGroup 9Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    [Video message] Caption: 💥 Specialists of the Unmanned Systems Forces hit a UAV control post of the enemy near Dumovka in Sumy region by a Geran drone. 🔹 Russian Defence Ministry

  12. [13]Nightwatch content 26640MoD Russia
    No URL storedNightwatch archive itemGroup 9Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    [Video message] Caption: Varyag's drones leave no chance for the enemy 💥 In the course of combat missions, UAV teams of the Varyag Separate Brigade hit: ▫️motor vehicles, ▫️UAV command posts, ▫️temporary deployment areas of AFU personnel. 🔹 Russian Defence Ministry

    Full stored excerpt

    [Video message] Caption: Varyag's drones leave no chance for the enemy 💥 In the course of combat missions, UAV teams of the Varyag Separate Brigade hit: ▫️motor vehicles, ▫️UAV command posts, ▫️temporary deployment areas of AFU personnel. 🔹 Russian Defence Ministry

  13. [14]Nightwatch content 53680Новости Москвы
    No URL storedNightwatch archive itemGroup 10Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    ⚡️ Москва подвергалась массированной атаке БПЛА С полуночи средства ПВО сбили 45 беспилотников В аэропортах Шереметьево, Внуково, Домодедово и Жуковский

  14. [15]Nightwatch content 84662ТАСС
    No URL storedNightwatch archive itemGroup 11Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    🚨 4 августа в период с 08:30 до 22:00 в сторону Московского региона летели 184 БПЛА, сообщил Собянин. 18 беспилотников уничтожены на подлете к Москве. ✔ Подпишись на ТАСС

  15. [16]Nightwatch content 15613Операция Z: Военкоры Русской Весны
    No URL storedNightwatch archive itemGroup 12Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    ‼️🇷🇺🏴‍☠️Враг атакует Москву: в Троицком округе пожар, пострадал человек ▪️Обломки вражеского дрона рухнули в районе села Кленово в Троицком округе Москвы

  16. [17]Nightwatch content 19407MoD Russia
    No URL storedNightwatch archive itemGroup 9Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    [Video message] Caption: Russia's Unmanned Systems Forces used Geran drones to annihilate personnel and a temporary deployment area of the 114th Territorial Defence Brigade close to Mamekino, Chernigov region. 🔹 Russian Defence Ministry

  17. [18]Nightwatch content 49303ТАСС
    No URL storedNightwatch archive itemGroup 11Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    🚨 Системы ПВО сбили два беспилотника, летевших на Москву, сообщил Собянин. ✔ Подпишись на ТАСС в "Максе"

  18. [19]Nightwatch content 11273ТАСС
    No URL storedNightwatch archive itemGroup 11Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    🚨 За последний час уничтожены 19 БПЛА на подлете к Москве, сообщил Собянин. ✔ Подпишись на ТАСС в Max

  19. [20]Nightwatch content 23708Exilenova+
    No URL storedNightwatch archive itemGroup 13Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    [Video message] Caption: Момент прильоту БПЛА FP-1/2

  20. [21]Nightwatch content 65898Новости Москвы
    No URL storedNightwatch archive itemGroup 10Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    ⚡️С вечера до 6 утра в направлении Московского региона летело более 430 беспилотников, — Собянин 36 вражеских БПЛА уничтожено на подлёте к Москве

  21. [22]Nightwatch content 28777MoD Russia
    No URL storedNightwatch archive itemGroup 9Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    [Video message] Caption: 💥 Geran UAV teams of the Unmanned Systems Forces hit an AFU mobile base of fire. 📍 vicinity of Poltava 🔹 Russian Defence Ministry

  22. [23]Nightwatch content 66274Поддубный |Z|О|V| edition
    No URL storedNightwatch archive itemGroup 14Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    Два человека пострадали в результате атаки украинского FPV-дрона на рейсовый автобус в Таврово Белгородской области. По данным регионального оперштаба

  23. [24]Nightwatch content 63478Дневник Десантника🇷🇺
    No URL storedNightwatch archive itemGroup 15Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    ⚡️ Дрон ВСУ атаковал пассажирский автобус в Брянской области, два человека пострадали Инцидент произошел на погранпереходе «Красный камень». Автобус следовал

  24. [28]Nightwatch content 19120Оперативный штаб - Краснодарский край
    No URL storedNightwatch archive itemGroup 18Published Retrieved

    No title is stored for this source; the text above is a placeholder.

    [Video message] Caption: На видео – последствия попадания БПЛА в один из многоквартирных домов в Прикубанском округе Краснодара.

  25. External web pageGroup 19Published Retrieved

    Explosion reported at Moscow metro station [VIDEO] An explosion was reported at the Bitsevsky Park station of the Moscow Metro, according to local media cited by AzerNEWS. Videos circulating on Telegram channels show the blast occurring at the station, though no further details about casualties, damage, or the cause of the explosion have been released at this time. Authorities have not yet provided official statements, and emergency services are reportedly on alert. Updates are expected as more information becomes available. Your browser doesn't support video. Please download the file: video/mp4 Tags: Moscow explosions incident metro stations Here we are to serve you with news right now. It does not cost much, but worth your attention. Choose to support open, independent, quality journalism and subscribe on a monthly basis. By subscribing to our online newspaper, you can have full digital access to all news, analysis, and much more. You can also follow AzerNEWS on Twitter @AzerNewsAz or Facebook @AzerNewsNewspaper Thank you!

    Full stored excerpt

    Explosion reported at Moscow metro station [VIDEO] An explosion was reported at the Bitsevsky Park station of the Moscow Metro, according to local media cited by AzerNEWS. Videos circulating on Telegram channels show the blast occurring at the station, though no further details about casualties, damage, or the cause of the explosion have been released at this time. Authorities have not yet provided official statements, and emergency services are reportedly on alert. Updates are expected as more information becomes available. Your browser doesn't support video. Please download the file: video/mp4 Tags: Moscow explosions incident metro stations Here we are to serve you with news right now. It does not cost much, but worth your attention. Choose to support open, independent, quality journalism and subscribe on a monthly basis. By subscribing to our online newspaper, you can have full digital access to all news, analysis, and much more. You can also follow AzerNEWS on Twitter @AzerNewsAz or Facebook @AzerNewsNewspaper Thank you!

Evidence and freshness

8 current-window claims

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. How to read these labels

16 Aug 2026, 15:06 UTC
to 17 Aug 2026, 15:06 UTC

Strike by a reactive Geran drone on an oil depot in Zaporizhzhia

Single-source claimMEDIUM confidence

Source published:

Source origin: Colonelcassad

No source link is stored for this record. Origins are shown by sender name.

The source was published inside the reporting window; the event occurrence time was not specified. Only one source origin supports this claim.
Link to this record

Russian strikes on Naftogaz energy infrastructure causing equipment damage and reduced production.

Single-source claimMEDIUM confidence

Source published:

Source origin: Операция Z: Военкоры Русской Весны

No source link is stored for this record. Origins are shown by sender name.

The source was published inside the reporting window; the event occurrence time was not specified. Only one source origin supports this claim.
Link to this record

Russian attack on port infrastructure damaged civilian vessel and injured four

Single-source claimMEDIUM confidence

Source published:

Source origin: Север.Реалии

No source link is stored for this record. Origins are shown by sender name.

The source was published inside the reporting window; the event occurrence time was not specified. Only one source origin supports this claim.
Link to this record

Drone strike damages Moscow metro station entrance and public bus in Anino district, causing three casualties.

Single-source claimMEDIUM confidence

Source published:

Source origin: SOTA

No source link is stored for this record. Origins are shown by sender name.

The source was published inside the reporting window; the event occurrence time was not specified. Only one source origin supports this claim.
Link to this record

Russian FPV drone strike damaged a vehicle transporting bread in Bilenke.

Official claimMEDIUM confidence

Source published:

Source origin: 🇺🇦 Запорізька обласна військова адміністрація 🇺🇦

No source link is stored for this record. Origins are shown by sender name.

The source was published inside the reporting window; the event occurrence time was not specified. This is an attributed official statement, not independent confirmation.
Link to this record

Russian forces struck logistics centers, energy objects, and transport targets of the Ukrainian Armed Forces.

Single-source claimMEDIUM confidence

Source published:

Source origin: Дневник Десантника🇷🇺

No source link is stored for this record. Origins are shown by sender name.

The source was published inside the reporting window; the event occurrence time was not specified. Only one source origin supports this claim.
Link to this record

Shipment moved into Moldova territory.

Single-source claimMEDIUM confidence

Source published:

Source origin: Николаевский Ванёк

No source link is stored for this record. Origins are shown by sender name.

The source was published inside the reporting window; the event occurrence time was not specified. Only one source origin supports this claim.
Link to this record

UAVs reported approaching Zaporizhzhia from the south.

Official claimMEDIUM confidence

Source published:

Source origin: Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine

No source link is stored for this record. Origins are shown by sender name.

The source was published inside the reporting window; the event occurrence time was not specified. This is an attributed official statement, not independent confirmation.
Link to this record

Frontline context

Territorial control and recent changes shown by DeepState.

Report 17 Aug 2026, 15:15 UTCLagged by 20.3 h
Map revision comparison

Against the previous report from 16 Aug 2026, 15:52 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

The latest control-map interval ended 20.3 hours before this report. The daily change covers 26.9 h. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
+1.6 km²
27 h ending 16 Aug 2026, 18:59 UTC
Daily net
+1.6 km²
26.9 h comparison
Seven-day net
-99 km²
168.0 h comparison
Largest changes in the latest measured interval
Near Pokrovsk
1.6 km² changed · RF-held gained 1.6 / lost 0.0 km²

Positive values indicate an increase in Russian-occupied area; negative values indicate a decrease. Yellow marks DeepState's infiltration area (gray zone), which is not included in occupied-area totals.

Report Visuals

4 visuals
Open full size
Nightwatch daily report #774: Izium area

Geospatial Analysis

39 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 39 places with coordinates
Geocoded places in report 774
PlaceCountryLatitude, longitudeCopy
KharkivUkraine50.00201269999999, 36.3073994
IziumUkraine49.2121445, 37.2665006
ZlatopilUkraine49.39500049999999, 36.2154518
KupianskUkraine49.7055574, 37.6027997
LozovaUkraine48.8902362, 36.308001
BohodukhivUkraine50.1636245, 35.5402444
LymanUkraine48.9897585, 37.8049964
Kozacha LopanUkraine50.33647329999999, 36.1851358
IzbytskeUkraine50.2060448, 36.7446399
OkhrimivkaUkraine50.3390596, 37.2121161
DvorichanskeUkraine50.0255357, 37.7614347
KurylivkaUkraine49.6589399, 37.7018417
NovoplatonivkaUkraine49.42994030000001, 37.6451069
PokrovskUkraine48.282193, 37.1847804
KostiantynivkaUkraine48.52394289999999, 37.7075811
Andriivka-KlevtsoveUkraine48.0466814, 36.5923009
Krasny KutUkraine48.556392, 37.405249
KramatorskUkraine48.738967, 37.58435
SlovianskUkraine48.8532, 37.6053
ZaporizhzhiaUkraine47.83928419999999, 35.13870970000001
Bileneke PersheUkraine47.6346785, 35.066866
NovosoloshyneUkraine47.7504938, 35.9207434
OrikhivUkraine47.5658802, 35.7876745
BohdanivkaUkraine48.2797752, 35.9412587
PavlohradUkraine48.5294478, 35.9032574
Kryvyi RihUkraine47.910483, 33.391783
OdesaUkraine46.4845702, 30.7326047
ChornomorskUkraine46.2952236, 30.6480855
OchakivUkraine46.61876669999999, 31.5387942
SumyUkraine50.9077, 34.7981
DonetskUkraine48.015883, 37.80285
NovofedorivkaUkraine45.0912763, 33.575602
Tendrivska SpitUkraine46.241389, 31.630833
SevastopolUkraine44.61665, 33.525367
Kamensk-ShakhtinskayaRussia48.3141177, 40.2689543
KoloskovoRussia50.241869, 37.9964159
KurskRussia51.7482395, 36.1947023
OrelRussia52.9668468, 36.06248980000001
Primorsko-AkhtarskRussia46.0444267, 38.1661077

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.