Russian strikes disrupt power in Dnipropetrovsk and Odesa oblasts; Zaporizhzhia begins restoration
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
- Follow-up investigation
- Inconclusive · 22 of 26 sources have no stored URL
- Claim records by status
- 8 records: 6 Single-source claim, 2 Official claim.
- Claim records by confidence
- 0 HIGH, 6 MEDIUM, 2 LOW.
- Records at LOW confidence
- One civilian killed and four injured in Taganrog per reported strikes (Single-source claim)
- Railway section from Taganrog to Mikhaylovka de-energized after strikes on traction substations (Single-source claim)
- 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 42.0 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
Analyst briefMachine-generated narrative. Labels inside it are written by the model. How to read these labels
Strategic Overview
Russian strikes caused new electricity disruptions in Dnipropetrovsk and Odesa oblasts, while Zaporizhzhia reported partial restoration by 14:51 UTC. DTEK, through RBC-Ukraine, reported damaged trunk lines affecting Dnipro and Kamianske, Dnipropetrovsk Oblast. Odesa regional reporting attributed outages affecting 41,000 households to damage at a DTEK facility. A subsequent strike in Odesa, Odesa Oblast, destroyed a car dealership and damaged warehouses, including grain storage. These are documented service and infrastructure effects; their duration remains unresolved.
Ukraine also reported strikes on Russian industrial facilities. Russian authorities acknowledged an overnight drone attack on Nizhnekamsk, Republic of Tatarstan, with industrial and residential damage. Ukrainian General Staff reporting identified industrial targets there, but production effects remain unverified. No independently verified territorial change is established in the supplied reporting.
Reporting window: 14 November, 15:05 UTC–15 November 2026, 15:05 UTC. Publication time does not necessarily establish event time.
Operational Updates
Ground sectors
- Pokrovsk–Kostiantynivka, Donetsk Oblast — MEDIUM: Unconfirmed: Ukraine’s General Staff reported 17 Russian attacks on the Pokrovsk axis and 10 on the Kostiantynivka axis within its daily accounting of 171 engagements. These are single-party figures, not independently audited engagement counts.
- Lyman–Sloviansk–Kramatorsk and Oleksandrivka axes — MEDIUM for attributed reporting: General Staff reporting, relayed through Liveuamap, recorded fighting on these axes without a verified territorial outcome. Unconfirmed: a Telegram source claimed Ukrainian forces expelled Russian infantry from Filya, Donetsk Oblast, and nearby woodland toward Dachne, Donetsk Oblast. No geolocated confirmation supports the claimed recapture.
- South Slobozhansky axis, Kharkiv Oblast — MEDIUM: Unconfirmed: relayed General Staff reporting recorded clashes, without establishing a positional change. The daily release reported no offensive activity on the Kupiansk axis during its accounting period.
- Huliaipole–Orikhiv, Zaporizhzhia Oblast — LOW for territorial claims: Unconfirmed: Russia’s MoD claimed capture of Tersyanka, Zaporizhzhia Oblast. Separately, Ukraine’s Center for Countering Disinformation denied Russian capture of Voskresenka, Zaporizhzhia Oblast, presenting footage attributed to the 142nd Separate Mechanized Brigade. The footage was not independently geolocated. These are distinct settlements; the denial does not resolve the Tersyanka claim. Relayed General Staff reporting recorded Huliaipole-axis fighting but no offensive activity on Orikhiv during its accounting period.
- Kherson/lower Dnipro — MEDIUM for the warning: Unconfirmed: Kherson, Kherson Oblast, authorities warned of possible explosive devices on Ivan Vazov Street. Munition type, origin and disposal status were not supplied. The General Staff reported no offensive activity on the Prydniprovskyi axis during its accounting period.
Defensive infrastructure and communications
- Kyiv — MEDIUM for the reported statement: Unconfirmed: Operatyvnyi ZSU relayed a ministerial statement that two of eight planned rapid-assembly crossings were under construction. This adds a construction-progress assertion to yesterday’s planning-and-preparation account, but physical construction remains independently unverified. A separate Patrol Police advisory restricted traffic toward Pivnichnyi Bridge; no cause was supplied, and no connection to strike damage or crossing construction is established.
- Frontline satellite communications — MEDIUM for the reported exchange: Unconfirmed: RBC-Ukraine and Operatyvnyi ZSU, citing reporter Nick Schifrin and Ukrainian diplomat Senik, reported that SpaceX characterized Starshield terminal speed restrictions as a “technical problem.” Ukraine reportedly said restrictions had persisted for five days. Both outlets relay the same account; no technical logs establish the mechanism or interception effects.
Deep Strikes & Air Defense
Russian strikes on Ukraine
- Dnipropetrovsk Oblast: RBC-Ukraine, citing DTEK at 13:05 UTC, reported damaged trunk power lines and outages in parts of Dnipro, Kamianske and surrounding districts. Critical infrastructure restoration was prioritized. Unconfirmed: a later Operatsiya Z relay claimed a complete Kamianske blackout, stopped boiler houses and disrupted water supply; this expanded scope lacks direct Ukrainian-source confirmation in the supplied material.
- Odesa Oblast: Unconfirmed: OVA-sourced reporting stated that an overnight attack damaged a DTEK facility, disconnected 41,000 households and injured six people. Multiple relays share that official origin rather than independently corroborating the figures. Afternoon strike damage is now assessed more specifically: OVA reporting and photographs document a destroyed car dealership, damaged warehouses including grain storage, and burning vehicles in Odesa and surrounding districts. No casualty figure was supplied for the afternoon attack as of 14:17 UTC. Weapon types remain unspecified.
- Zaporizhzhia, Zaporizhzhia Oblast: The OVA reported partial electricity restoration in Zavodskyi, Shevchenkivskyi and Dnipro districts at 14:51 UTC. Earlier official reporting established outages and backup power at critical facilities; a Telegram claim of oblast-wide loss of electricity, water and heating remains Unconfirmed: and exceeds the official evidence. Unconfirmed: ASTRA, citing the OVA, reported six injured in an overnight strike; DSNS reporting separately described an injured 39-year-old man, a damaged two-story building, a fire and five evacuees. Another OVA account reported a hospitalized woman in Dnipro district. These accounts cannot safely be combined or treated as revisions to yesterday’s casualty report.
- Pavlohrad, Dnipropetrovsk Oblast: The OVA reported one killed, ten injured and at least nine houses damaged following a missile strike on 14 November. Official reporting and imagery support residential damage. Unconfirmed: a Russian channel identified an Iskander-M and alleged military use of an abandoned kindergarten. The missile system and alleged target function are not established; residential damage alone does not resolve the intended target.
- Poltava Oblast: RBC-Ukraine and Operatyvnyi ZSU reported a drone strike and substantial fire at a Naftogaz facility; damage extent and supply effects were not assessed. Unconfirmed: Russian-channel footage was separately captioned as strikes on the Kremenchuk, Poltava Oblast, refinery. The refinery identification, timing and cause are unverified; no connection to the Naftogaz incident is established.
- Vyshhorod district, Kyiv Oblast: RBC-Ukraine published DSNS imagery documenting warehouse damage and firefighting. Unconfirmed: the accompanying account reported one injured man. The fire was extinguished, with cooling and debris clearance continuing. Weapon type and exact impact time were not supplied.
- Zhytomyr and Kirovohrad oblasts: Unconfirmed: OVA-sourced relays reported energy-infrastructure and four-house damage in Zhytomyr Oblast, and a drone strike on a residential house in Kropyvnytskyi, Kirovohrad Oblast. No casualties were reported in those accounts.
- Kharkiv, Donetsk and Luhansk oblasts: Named-journalist footage from Kramatorsk, Donetsk Oblast, shows major building destruction and an apartment-block fire, but does not date the damage-producing strikes. Unconfirmed: Russian channels alleged Geran strikes in Kharkiv and Chuhuiv, Kharkiv Oblast, without independently established locations or weapons. Unconfirmed: Mash reported one woman killed and one man wounded after a drone struck an apartment building in Lysychansk, Luhansk Oblast; photographs support structural damage, not responsibility or the casualty figures.
- Other Russian target claims: Unconfirmed: Russia’s MoD claimed a substation strike in Rivne Oblast, specific port facilities at Chornomorsk, Odesa Oblast, two locomotives near Dnipro station, and a cargo vessel bound for Odesa. Ukrainian reporting does not verify those specific targets or the alleged military cargo. Earlier Russian-origin accounts differed between one vessel and five; repeated relays do not resolve that disagreement.
Strikes reported in Russia
- Nizhnekamsk, Tatarstan: Russian municipal and regional authorities acknowledged a drone attack and industrial-zone damage. Mayor Belyaev’s latest reported toll was six injured, including a hospitalized Rosgvardiya officer; residential electricity and water were restored. Unconfirmed: Ukraine’s General Staff claimed strikes on Nizhnekamskneftekhim and the TAIF-NK ELOU-AVT-7 installation. The official Russian acknowledgment supports the attack’s occurrence, not every claimed target or damage outcome. Later fire footage does not establish a second attack or additional damage.
- Trubchevsk, Bryansk Oblast: Unconfirmed: Ukraine’s General Staff claimed a strike on JSC Monolit. No Russian acknowledgment or independent damage assessment was supplied.
- Akhtubinsk, Astrakhan Oblast: Unconfirmed: Ukrainian-affiliated channels claimed an airfield strike and ammunition-depot detonations, initially sharing the same Exilenova+ footage. A later sitrep references a General Staff claim, but supplies no detailed statement or independent damage evidence. Aircraft losses are not established.
- Taganrog, Rostov Oblast: Governor-sourced reporting described damage to two substations and the R-280 road corridor, with railway and road disruption. Unconfirmed: relayed casualty accounts reported one killed and differed between four and five injured. Reports also differed over whether the damaged road structure was a bridge; its exact nature remains unresolved.
- Kursk and Bryansk oblasts: Unconfirmed: Governor-sourced accounts relayed by ASTRA reported three injured in Kursk city and one in Prilepy, Kursk Oblast, and four civilians injured near Pervomayskoye and Dareevsk, Bryansk Oblast. The governors attributed these incidents to Ukrainian drones; independent attribution and casualty verification were not supplied.
Air-defense reporting
- Ukraine: Unconfirmed: the Air Force reported 132 incoming Shahed-type, Gerbera and Parodiya UAVs, including 78 jet-powered aircraft; 106 were destroyed or suppressed, including 61 jet-powered, with impacts at 20 locations. These are official operational claims, not independently verified counts. The infographic’s 2026 date matches the report date and is not itself an anomaly.
- Russia: Unconfirmed: the latest MoD daily aggregate claimed interception of 1,065 fixed-wing UAVs, three guided bombs and one HIMARS rocket. It covers a different period from the earlier 533-UAV overnight statement and must not be added to it. A separate MoD claim of more than 50 UAVs downed in Zaporizhzhia region is also unverified and may overlap.
- Continuing warnings: Air Force alerts extended across northern, central, southern and western Ukraine, including Chernihiv, Sumy, Kyiv, Cherkasy, Poltava, Kirovohrad, Dnipropetrovsk, Kharkiv, Donetsk, Zaporizhzhia, Odesa, Mykolaiv, Vinnytsia, Zhytomyr, Khmelnytskyi and Ternopil oblasts. Missile warnings included Kryvyi Rih, Nikopol, Zaporizhzhia and Okhtyrka. Kyiv’s latest municipal all-clear was issued at 14:35 UTC. Tracking messages do not establish separate aircraft, impacts or interceptions; alerts continued through 14:58 UTC without corresponding outcomes for most vectors.
SAR Intelligence (Satellite Data)
- Imagery Review: No validated exact-track measurements from acquisitions within the last 24 hours were supplied. No acquisition family, score or review priority can be reported.
- Assessment: Historical anomaly assessment is unavailable. This absence establishes neither unchanged conditions nor inactivity.
Equipment & Losses
- Russian personnel — Unconfirmed: Ukraine’s General Staff reported 2,230 Russian personnel losses over its preceding daily accounting period. The figure is unaudited and does not establish a killed-only count.
- Ukrainian personnel — Unconfirmed: Russia’s MoD claimed approximately 1,120 Ukrainian personnel losses in 24 hours, without independent verification.
- Equipment — Unconfirmed: Russian unit compilations claimed Ukrainian vehicle, UAV and communications-equipment losses, but lacked sufficient geolocation, dating and post-strike evidence to establish a daily equipment-loss tally. No aircraft losses at Akhtubinsk are verified.
Confidence Check
- HIGH: Odesa afternoon infrastructure damage, Vyshhorod warehouse damage and Zaporizhzhia’s partial electricity restoration are supported by official imagery or direct official updates. This does not establish weapon types or complete damage totals.
- HIGH for occurrence; MEDIUM for detailed effects: The Nizhnekamsk drone attack is supported by Russian official acknowledgment and fire imagery. Unconfirmed: Ukrainian claims concerning individual industrial installations and production damage remain unverified.
- MEDIUM — Unconfirmed: DTEK-sourced Dnipropetrovsk outages, Odesa’s 41,000-household figure, and the Air Force’s 132 incoming/106 destroyed-or-suppressed summary remain attributed, principally single-origin accounts. Multiple relays do not establish source independence.
- MEDIUM — Unconfirmed: General Staff sector counts, Kyiv crossing construction and the reported SpaceX exchange lack independent operational verification.
- LOW — Unconfirmed: Filya recapture, Tersyanka capture, Akhtubinsk ammunition-depot effects, the Kremenchuk refinery identification, Kamianske’s complete-blackout scope, Russian interception aggregates and both sides’ personnel-loss figures remain unverified.
Evidence-support masses are uncalibrated diagnostics, not factual probabilities or corroboration. Unknown source independence and conflicting accounts remain unresolved rather than being averaged into a single finding.
The Bottom Line
The clearest operational development is new disruption to Ukrainian power supply and civilian infrastructure, with restoration already underway in parts of Zaporizhzhia. Ground reporting establishes continued fighting but no independently verified territorial change.
Watch over the next 24 hours:
- DTEK/OVA restoration updates for Dnipro, Kamianske and Odesa, and the remaining outage footprint in Zaporizhzhia.
- Independent damage evidence for Nizhnekamsk’s industrial installations, Monolit and the claimed Akhtubinsk strike.
- Geolocated evidence resolving Filya and Tersyanka control claims.
Follow-up investigation
InconclusiveMachine-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 the reported traction-power damage between Taganrog-Passazhirsky and Mikhailovka interrupt rail traffic, and when was service restored, according to public railway notices and independently verifiable evidence?
Answer
Yes—public railway statements quoted by Interfax document an interruption, not merely loss of traction power: seven suburban services were cancelled, fourteen services were shortened to Morskaya, and the Taganrog–Novorossiysk Lastochka was delayed three hours [external-48ffc1422209e9bc]. Passenger trains were subsequently operating under a temporary scheme on the Taganrog–Rostov and Taganrog–Uspenskaya routes by the Interfax update published at 10:55 UTC on 15 November 2026; some trains had already passed the affected sections, while repairs continued [external-e7e2a8c9acc2a564]. This establishes reported partial resumption by that publication time—not the exact reopening time, restoration of traction power, or return to the normal timetable. The reviewed evidence does not independently verify those operational milestones or establish when full service was restored.
Findings
- InconclusiveLow confidence
Observation: Interfax quotes the North Caucasus Railway press service reporting seven suburban-service cancellations, fourteen services shortened to Morskaya, and a three-hour delay to the Taganrog–Novorossiysk Lastochka following substation and contact-network damage. These specific operating effects substantiate the reported rail interruption beyond the original Telegram account of de-energization.
Confirmation concerns the documented railway announcement. Interfax relays the railway operator's statement; it is not independent observation of train movements or physical damage. The original governor-sourced Telegram account also explicitly says railway traffic was suspended. A definitive answer requires at least two independent external source groups.
Sources named for this finding: [23] Interfax.ru, [1] Два майора
- InconclusiveLow confidence
Observation: An Interfax update published at 10:55 UTC on 15 November 2026 quotes the railway saying passenger traffic on the Taganrog–Rostov and Taganrog–Uspenskaya routes was operating under a temporary scheme and some trains had passed the affected sections. Inference: partial passenger service had resumed by that publication time, but normal service was not established.
The publication timestamp is an upper bound for the reported partial resumption, not its exact start time. The announcement says repair crews continued working and does not establish re-energization, unrestricted operation, freight-service status, or restoration of the normal timetable. A definitive answer requires at least two independent external source groups.
Sources named for this finding: [24] Interfax.ru
- InconclusiveLow confidence
The reviewed evidence does not establish when full service or traction power was restored, nor independently verify the actual interruption and reopening through observed train movements. The later railway account describes temporary operation with repairs continuing; the Rybar material supplies no independently verified railway imagery.
The railway notices are available here through media quotations, not direct operator records. Rybar's accompanying bridge images are described as illustrative or location-unverified and cannot verify railway operating status. These limitations do not prove that full restoration did not subsequently occur. A definitive answer requires at least two independent external source groups.
Sources named for this finding: [24] Interfax.ru, [23] Interfax.ru, [6] Рыбарь
Remaining gaps
- A direct railway notice specifying the exact time passenger operations resumed and when the normal timetable was restored.
- An operator or infrastructure-repair notice establishing when traction power was re-energized and whether temporary operation used alternative traction.
- Timestamped, geolocated train-movement evidence or independently accessible operational records verifying interruption and reopening on the affected section.
- Freight-service restrictions and restoration milestones, which the passenger-service updates do not establish.
Investigation sources (26)
22 of 26 sources have no stored URL and cannot be opened from this page.
- External web page: 4, of which 0 without a URL
- Source observation behind a claim record: 8, of which 8 without a URL
- Nightwatch archive item: 14, of which 14 without a URL
The generator placed these sources in 18 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]A power substation serving the railway was damaged in Taganrog; power lines from Taganrog-Passazhirsky station to Mikhailovka station were de-energized.Два майораNo URL storedSource observation behind a claim recordGroup 1Published Retrieved
В Таганроге повреждена электроподстанция, обслуживающая железную дорогу.
- [6]Railway section from Taganrog to Mikhaylovka de-energized after strikes on traction substationsРыбарьNo URL storedSource observation behind a claim recordGroup 3Published Retrieved
two electrical substations hit (railway section Taganrog–Mikhaylovka de-energized;
- [23]Семь пригородных поездов отменили в Ростовской области из-за повреждения контактной сети Interfax.ruExternal web pageGroup 16Published Retrieved
Семь пригородных поездов отменили в Ростовской области из-за повреждения контактной сети Москва. 15 ноября. INTERFAX.RU - Отменены семь пригородных поездов в Ростовской области из-за нарушения работы контактной сети после повреждения электроподстанции из-за падения обломков БПЛА на станции Таганрог, сообщает пресс-служба Северо-Кавказской железной дороги (СКЖД, филиал ОАО "РЖД") в своем канале в Max. "Отменены пригородные поезда: №6071 Таганрог - Ростов, №6301 Успенская - Таганрог, №6302 Таганрог - Успенская, №6501 Таганрог - Ростов, №6507 Таганрог - Ростов, №6303 Успенская - Ростов, №6304 Таганрог - Успенская", - говорится в сообщении. Кроме того, сообщается, что на три часа задержан поезд №805 "Ласточка" Таганрог - Новороссийск. По данным пресс-службы, график движения 14 поездов, курсирующих между Ростовом и Таганрогом, сокращен до станции Морская. Они будут ходить по маршрутам Ростов - Морская и Морская - Ростов. "В настоящее время на месте работают специалисты аварийно-восстановительной бригады. Железнодорожники делают все необходимое для возобновления движения в штатном режиме", - отмечает СКЖД. Как сообщалось, в ночь на воскресенье из-за атаки БПЛА на Ростовскую область в Таг
Full stored excerpt
Семь пригородных поездов отменили в Ростовской области из-за повреждения контактной сети Москва. 15 ноября. INTERFAX.RU - Отменены семь пригородных поездов в Ростовской области из-за нарушения работы контактной сети после повреждения электроподстанции из-за падения обломков БПЛА на станции Таганрог, сообщает пресс-служба Северо-Кавказской железной дороги (СКЖД, филиал ОАО "РЖД") в своем канале в Max. "Отменены пригородные поезда: №6071 Таганрог - Ростов, №6301 Успенская - Таганрог, №6302 Таганрог - Успенская, №6501 Таганрог - Ростов, №6507 Таганрог - Ростов, №6303 Успенская - Ростов, №6304 Таганрог - Успенская", - говорится в сообщении. Кроме того, сообщается, что на три часа задержан поезд №805 "Ласточка" Таганрог - Новороссийск. По данным пресс-службы, график движения 14 поездов, курсирующих между Ростовом и Таганрогом, сокращен до станции Морская. Они будут ходить по маршрутам Ростов - Морская и Морская - Ростов. "В настоящее время на месте работают специалисты аварийно-восстановительной бригады. Железнодорожники делают все необходимое для возобновления движения в штатном режиме", - отмечает СКЖД. Как сообщалось, в ночь на воскресенье из-за атаки БПЛА на Ростовскую область в Таг
- External web pageGroup 16Published Retrieved
Движение поездов в Ростовской области организовано по временной схеме Москва. 15 ноября. INTERFAX.RU - Пассажирские поезда на направлениях Таганрог - Ростов и Таганрог - Успенская в Ростовской области пустили по временной схеме из-за нарушения работы контактной сети после повреждения электроподстанции из-за падения обломков БПЛА на станции Таганрог, сообщает пресс-служба Северо-Кавказской железной дороги (СКЖД, филиал ОАО "РЖД") в своем канале в Max. "Движение пассажирских поездов на направлениях Таганрог - Ростов и Таганрог - Успенская организовано по временной схеме. Ряд поездов уже проследовал через барьерные участки", - говорится в сообщении. Отмечается, что специалисты аварийно-восстановительных бригад продолжают устранять последствия инцидента. Как сообщалось, в ночь на воскресенье из-за атаки БПЛА на Ростовскую область в Таганроге пострадала электроподстанция, обслуживающая железную дорогу, линия электропередачи от станции Таганрог-Пассажирский до станции Михайловка обесточена, движение поездов было приостановлено. В результате атаки погиб инженер электроподстанции. Сообщалось о четырех пострадавших мирных жителях, затем число пострадавших увеличилось до пяти человек. В Тага
Full stored excerpt
Движение поездов в Ростовской области организовано по временной схеме Москва. 15 ноября. INTERFAX.RU - Пассажирские поезда на направлениях Таганрог - Ростов и Таганрог - Успенская в Ростовской области пустили по временной схеме из-за нарушения работы контактной сети после повреждения электроподстанции из-за падения обломков БПЛА на станции Таганрог, сообщает пресс-служба Северо-Кавказской железной дороги (СКЖД, филиал ОАО "РЖД") в своем канале в Max. "Движение пассажирских поездов на направлениях Таганрог - Ростов и Таганрог - Успенская организовано по временной схеме. Ряд поездов уже проследовал через барьерные участки", - говорится в сообщении. Отмечается, что специалисты аварийно-восстановительных бригад продолжают устранять последствия инцидента. Как сообщалось, в ночь на воскресенье из-за атаки БПЛА на Ростовскую область в Таганроге пострадала электроподстанция, обслуживающая железную дорогу, линия электропередачи от станции Таганрог-Пассажирский до станции Михайловка обесточена, движение поездов было приостановлено. В результате атаки погиб инженер электроподстанции. Сообщалось о четырех пострадавших мирных жителях, затем число пострадавших увеличилось до пяти человек. В Тага
Retrieved, not named by any finding (22)
- [2]Two locomotives used for transporting military cargo were destroyed near Dnipropetrovsk stationKotsnewsNo URL storedSource observation behind a claim recordGroup 2Published Retrieved
Около станции Днепропетровск поражены два локомотива, на которых возили грузы для ВСУ.
- [3]One civilian killed and four injured in Taganrog per reported strikesРыбарьNo URL storedSource observation behind a claim recordGroup 3Published Retrieved
## Key observations - **Text scope:** Claims one civilian killed and four injured in Taganrog;
- [4]Missile reported heading toward ZaporizhzhiaПовітряні Сили ЗС України / Air Force of the Armed Forces of UkraineNo URL storedSource observation behind a claim recordGroup 4Published Retrieved
🚀 Бандероль на Запоріжжя.
- [5]Drone struck an apartment in a residential building in Nizhnekamsk causing window damage; 6 injured reported overall from the attack including 1 Rosgvardiya officer hospitalizedASTRANo URL storedSource observation behind a claim recordGroup 5Published Retrieved
- **Residential damage visible:** Final frames show a multi-story panel building (green/maroon facade) with a dark protruding object on an upper floor and broken/missing windows — consistent with the text's claim that a drone struck an apartment.
Full stored excerpt
- **Residential damage visible:** Final frames show a multi-story panel building (green/maroon facade) with a dark protruding object on an upper floor and broken/missing windows — consistent with the text's claim that a drone struck an apartment.
- [7]A PRV-13 radio altimeter system was reportedly hit at Akhtubinsk airfield, degrading local airfield operationsОперативний ЗСУNo URL storedSource observation behind a claim recordGroup 6Published Retrieved
- A PRV-13 radio altimeter system was reportedly also hit — a niche air-defense/ground-control asset whose loss would degrade local airfield operations.
- [8]Guided aerial bombs (KABs) reported on ZaporizhzhiaПовітряні Сили ЗС України / Air Force of the Armed Forces of UkraineNo URL storedSource observation behind a claim recordGroup 4Published Retrieved
💣 КАБи на Запоріжжя
- [9]Nightwatch content 181876ТАССNo URL storedNightwatch archive itemGroup 7Published Retrieved
No title is stored for this source; the text above is a placeholder.
🚨 В Таганроге повреждена электроподстанция, обслуживающая железную дорогу. Возгорания нет, сообщил губернатор Слюсарь. Обесточены линии электропередачи от
- [10]Nightwatch content 172572ColonelcassadNo URL storedNightwatch archive itemGroup 8Published Retrieved
No title is stored for this source; the text above is a placeholder.
## Russian Telegram channel @lost_armour publishes strike chronicle for Nov 3–4, 2026 with video of fire in Odessa **One-line summary:** Russian military Telegram channel @lost_armour posted a detailed timeline of strikes across Ukraine on November 3, 2026, accompanied by video showing a large
Full stored excerpt
## Russian Telegram channel @lost_armour publishes strike chronicle for Nov 3–4, 2026 with video of fire in Odessa **One-line summary:** Russian military Telegram channel @lost_armour posted a detailed timeline of strikes across Ukraine on November 3, 2026, accompanied by video showing a large
- [11]Nightwatch content 167193Оперативний ЗСУNo URL storedNightwatch archive itemGroup 9Published Retrieved
No title is stored for this source; the text above is a placeholder.
## Russian Drone Attack on Dnipro Train Station — DSNS Ukraine Media Package **Summary:** Telegram post from a Ukrainian-affiliated channel shares video and photos attributed to DSNS Ukraine (State Emergency Service) depicting the aftermath of a drone strike on a passenger train platform in
Full stored excerpt
## Russian Drone Attack on Dnipro Train Station — DSNS Ukraine Media Package **Summary:** Telegram post from a Ukrainian-affiliated channel shares video and photos attributed to DSNS Ukraine (State Emergency Service) depicting the aftermath of a drone strike on a passenger train platform in
- [12]Nightwatch content 176131ЦАПЛІЄНКО_UKRAINE FIGHTSNo URL storedNightwatch archive itemGroup 10Published Retrieved
No title is stored for this source; the text above is a placeholder.
## Ukraine reportedly struck a bridge over the Mius River in Rostov Oblast — video shows nighttime explosion near an illuminated bridge on a highway ### Key Observations - **First video (~70s):** Filmed from a moving vehicle on a highway at dusk. Camera pans upward showing a small aircraft or
Full stored excerpt
## Ukraine reportedly struck a bridge over the Mius River in Rostov Oblast — video shows nighttime explosion near an illuminated bridge on a highway ### Key Observations - **First video (~70s):** Filmed from a moving vehicle on a highway at dusk. Camera pans upward showing a small aircraft or
- [13]Nightwatch content 23444Треш Ульяновск 😱No URL storedNightwatch archive itemGroup 11Published Retrieved
No title is stored for this source; the text above is a placeholder.
[Video message] Caption: ❗️ Резервный состав с пассажирами поезда Москва — Челябинск отправился из Ульяновска. Специальный поезд № 902 проследует до Челябинска с
- [14]Nightwatch content 167433ColonelcassadNo URL storedNightwatch archive itemGroup 8Published Retrieved
No title is stored for this source; the text above is a placeholder.
## Video Claim: Russian "Geran" Drone Strikes on Four Ukrainian Locomotives Across Zaporizhzhia and Dnipropetrovsk Regions **Summary:** A Russian military Telegram channel posts a video compilation claiming four successful "Geran" (Shahed-type) drone strikes on railway locomotives at separate
Full stored excerpt
## Video Claim: Russian "Geran" Drone Strikes on Four Ukrainian Locomotives Across Zaporizhzhia and Dnipropetrovsk Regions **Summary:** A Russian military Telegram channel posts a video compilation claiming four successful "Geran" (Shahed-type) drone strikes on railway locomotives at separate
- [15]Nightwatch content 124653Военкор КотенокNo URL storedNightwatch archive itemGroup 12Published Retrieved
No title is stored for this source; the text above is a placeholder.
Russian milblogger claims Geran-2 strike on railway traction substation in Oleksandriia, Kirovohrad Oblast. **1. Summary** - A Telegram post by @voenkorKotenok, a Russian military correspondent channel, claims that a video shows the moment of a Geran-2 loitering munition striking a 150/35/27.5 kV
Full stored excerpt
Russian milblogger claims Geran-2 strike on railway traction substation in Oleksandriia, Kirovohrad Oblast. **1. Summary** - A Telegram post by @voenkorKotenok, a Russian military correspondent channel, claims that a video shows the moment of a Geran-2 loitering munition striking a 150/35/27.5 kV
- [16]Nightwatch content 77344ТАССNo URL storedNightwatch archive itemGroup 7Published Retrieved
No title is stored for this source; the text above is a placeholder.
🚨 Отключение тяговой подстанции произошло в Ростове-на-Дону из-за непогоды. Задерживаются 27 поездов, сообщили в СКЖД.
- [17]Nightwatch content 90903ЦАПЛІЄНКО_UKRAINE FIGHTSNo URL storedNightwatch archive itemGroup 10Published Retrieved
No title is stored for this source; the text above is a placeholder.
Russian strike on passenger train locomotive in Odesa region kills crew, evacuates 340 passengers. **Key Observations:** - **Visual Evidence of Damage:** The video footage clearly shows a locomotive (number 2ТЭ10У-1540 visible in some frames, though blurry) that has sustained severe damage. The
Full stored excerpt
Russian strike on passenger train locomotive in Odesa region kills crew, evacuates 340 passengers. **Key Observations:** - **Visual Evidence of Damage:** The video footage clearly shows a locomotive (number 2ТЭ10У-1540 visible in some frames, though blurry) that has sustained severe damage. The
- [18]Nightwatch content 18778Exilenova+No URL storedNightwatch archive itemGroup 13Published Retrieved
No title is stored for this source; the text above is a placeholder.
[Video message] Caption: Працює весь спектр ППО над Таганрогом.
- [19]Nightwatch content 77876ТАССNo URL storedNightwatch archive itemGroup 7Published Retrieved
No title is stored for this source; the text above is a placeholder.
🚊 В Ростовской области из-за непогоды задерживаются 111 пассажирских поездов. Об этом сообщается в Telegram-канале РЖД.
- [20]Nightwatch content 31948WarArchiveNo URL storedNightwatch archive itemGroup 14Published Retrieved
No title is stored for this source; the text above is a placeholder.
[Video message] Caption: 🔥Партизани «Атеш» підпалили тепловоз, що забезпечував логістику російської армії, який стояв на станції Ліховська в Ростовській області. 🔥 Atesh
- [21]Nightwatch content 77557ТАССNo URL storedNightwatch archive itemGroup 7Published Retrieved
No title is stored for this source; the text above is a placeholder.
🚊 Число задерживающихся поездов в Ростовской области возросло до 89, сообщается в официальном новостном канале РЖД. Уточняется, что задержки составляют до 8
- [22]Nightwatch content 140716ASTRANo URL storedNightwatch archive itemGroup 15Published Retrieved
No title is stored for this source; the text above is a placeholder.
Occupied Donetsk and Makiivka districts reportedly lose power and water after overnight strikes on energy facilities. **Attachments and relation to caption** - The post contains a single video message with a Russian-language caption; no photo album or separate media items are present. - The video's
Full stored excerpt
Occupied Donetsk and Makiivka districts reportedly lose power and water after overnight strikes on energy facilities. **Attachments and relation to caption** - The post contains a single video message with a Russian-language caption; no photo album or separate media items are present. - The video's
- [25]Три поезда из Таганрога отменены утром 15 ноября после атаки БПЛА | Интересный контент в группе Блокнот Ростов-на-Дону в ОК (Одноклассники) Социальная сеть OK (Одноклассники)External web pageGroup 17Published Retrieved
Блокнот Ростов-на-Дону Три поезда из Таганрога отменены утром 15 ноября после атаки БПЛА В Ростовской области отменены три электрички из-за повреждения электроподстанции, обслуживающей железную дорогу, сообщил утром губернатор Юрий Слюсарь.- Обесточены линии электропередачи от станции Таганрог-Пассажирский до станции Михайловка. Движение железнодорожного транспорта приостановлено, написал глава региона.Как уточнили в пресс-службе СКЖД, в 01:40 обломки БПЛА упали на перегоне Неклиновка – Марцево СКЖД, что вызвало повреждение контактной сети. Сейчас на место направлены аварийно-восстановительные бригады.Отменены пригородные поезда №6071 Таганрог – Ростов (отправление в 04:34), №6301 Успенская – Таганрог (04:50) и №6302 Таганрог – Успенская (отправление 06:44).Также в Таганроге получила повреждения электроподстанция в квартале Шубин. Возникло возгорание. Специальные службы обеспечивают ликвидацию последствий. Нет комментариев Блокнот Ростов-на-Дону Присоединяйтесь — мы покажем вам много интересного Присоединяйтесь к ОК, чтобы подписаться на группу и комментировать публикации.
Full stored excerpt
Блокнот Ростов-на-Дону Три поезда из Таганрога отменены утром 15 ноября после атаки БПЛА В Ростовской области отменены три электрички из-за повреждения электроподстанции, обслуживающей железную дорогу, сообщил утром губернатор Юрий Слюсарь.- Обесточены линии электропередачи от станции Таганрог-Пассажирский до станции Михайловка. Движение железнодорожного транспорта приостановлено, написал глава региона.Как уточнили в пресс-службе СКЖД, в 01:40 обломки БПЛА упали на перегоне Неклиновка – Марцево СКЖД, что вызвало повреждение контактной сети. Сейчас на место направлены аварийно-восстановительные бригады.Отменены пригородные поезда №6071 Таганрог – Ростов (отправление в 04:34), №6301 Успенская – Таганрог (04:50) и №6302 Таганрог – Успенская (отправление 06:44).Также в Таганроге получила повреждения электроподстанция в квартале Шубин. Возникло возгорание. Специальные службы обеспечивают ликвидацию последствий. Нет комментариев Блокнот Ростов-на-Дону Присоединяйтесь — мы покажем вам много интересного Присоединяйтесь к ОК, чтобы подписаться на группу и комментировать публикации.
- External web pageGroup 18Published Retrieved
За последние 20 дней аварии на железной дороге привели к задержкам не менее 220 поездов, сегодня, 7 августа, в РЖД сообщили об очередном инциденте в Краснодарском крае. Согласно данным, опубликованным в официальном телеграм-канале РЖД, 7 августа в 05:12 напряжение в контактной сети пропало из-за падения обломков БПЛА между станциями Величковка и Ангелинская. По состоянию на 9:30 7 пассажирских поездов задерживаются в пути до 3 часов: №289 Екатеринбург – Анапа №11 Москва – Анапа №121 Санкт-Петербург – Новороссийск №473 Смоленск – Симферополь №97 Москва – Симферополь №507 Ижевск – Новороссийск №255 Сосногорск – Анапа Этот инцидент стал уже седьмым подобным подряд за последние 20 дней. Первая крупная авария такого рода произошла 19 июля на перегоне Лихая – Замчалово в Ростовской области, 21 июля пожар возник на станции Каменоломни, 25 июля – на станции Песчанокопская (обе в Ростовской области). Также 25 июля пострадала станция Тимашевская (Краснодарский край), 29 июля – станция Сальск (Ростовская область), 31 июля – станция Арчеда (Волгоградская область), 7 августа – участок ж/д Величковка – Ангелинская (Краснодарский край). В результате этих аварий были задержаны не менее 220 пассажи
Full stored excerpt
За последние 20 дней аварии на железной дороге привели к задержкам не менее 220 поездов, сегодня, 7 августа, в РЖД сообщили об очередном инциденте в Краснодарском крае. Согласно данным, опубликованным в официальном телеграм-канале РЖД, 7 августа в 05:12 напряжение в контактной сети пропало из-за падения обломков БПЛА между станциями Величковка и Ангелинская. По состоянию на 9:30 7 пассажирских поездов задерживаются в пути до 3 часов: №289 Екатеринбург – Анапа №11 Москва – Анапа №121 Санкт-Петербург – Новороссийск №473 Смоленск – Симферополь №97 Москва – Симферополь №507 Ижевск – Новороссийск №255 Сосногорск – Анапа Этот инцидент стал уже седьмым подобным подряд за последние 20 дней. Первая крупная авария такого рода произошла 19 июля на перегоне Лихая – Замчалово в Ростовской области, 21 июля пожар возник на станции Каменоломни, 25 июля – на станции Песчанокопская (обе в Ростовской области). Также 25 июля пострадала станция Тимашевская (Краснодарский край), 29 июля – станция Сальск (Ростовская область), 31 июля – станция Арчеда (Волгоградская область), 7 августа – участок ж/д Величковка – Ангелинская (Краснодарский край). В результате этих аварий были задержаны не менее 220 пассажи
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
A power substation serving the railway was damaged in Taganrog; power lines from Taganrog-Passazhirsky station to Mikhailovka station were de-energized.
Single-source claimMEDIUM confidenceSource published:
A power substation serving the railway was damaged in Taganrog; power lines from Taganrog-Passazhirsky station to Mikhailovka station were de-energized.
Source published:
No source link is stored for this record. Origins are shown by sender name.
Two locomotives used for transporting military cargo were destroyed near Dnipropetrovsk station
Single-source claimMEDIUM confidenceSource published:
Two locomotives used for transporting military cargo were destroyed near Dnipropetrovsk station
Source published:
No source link is stored for this record. Origins are shown by sender name.
One civilian killed and four injured in Taganrog per reported strikes
Single-source claimLOW confidenceSource published:
One civilian killed and four injured in Taganrog per reported strikes
Source published:
No source link is stored for this record. Origins are shown by sender name.
Missile reported heading toward Zaporizhzhia
Official claimMEDIUM confidenceSource published:
Missile reported heading toward Zaporizhzhia
Source published:
No source link is stored for this record. Origins are shown by sender name.
Drone struck an apartment in a residential building in Nizhnekamsk causing window damage; 6 injured reported overall from the attack including 1 Rosgvardiya officer hospitalized
Single-source claimMEDIUM confidenceSource published:
Drone struck an apartment in a residential building in Nizhnekamsk causing window damage; 6 injured reported overall from the attack including 1 Rosgvardiya officer hospitalized
Source published:
No source link is stored for this record. Origins are shown by sender name.
Railway section from Taganrog to Mikhaylovka de-energized after strikes on traction substations
Single-source claimLOW confidenceSource published:
Railway section from Taganrog to Mikhaylovka de-energized after strikes on traction substations
Source published:
No source link is stored for this record. Origins are shown by sender name.
A PRV-13 radio altimeter system was reportedly hit at Akhtubinsk airfield, degrading local airfield operations
Single-source claimMEDIUM confidenceSource published:
A PRV-13 radio altimeter system was reportedly hit at Akhtubinsk airfield, degrading local airfield operations
Source published:
No source link is stored for this record. Origins are shown by sender name.
Guided aerial bombs (KABs) reported on Zaporizhzhia
Official claimMEDIUM confidenceSource published:
Guided aerial bombs (KABs) reported on Zaporizhzhia
Source published:
No source link is stored for this record. Origins are shown by sender name.
Frontline context
Territorial control and recent changes shown by DeepState.
Against the previous report from 14 Nov 2026, 15:09 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.
The latest control-map interval ended 42.0 hours before this report. These map dates may differ from the reporting period and do not establish when territorial changes occurred.
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
5 visualsGeospatial Analysis
38 locations identified
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 38 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Dnipro | UA | 48.464717, 35.046183 | |
| Kamianske | UA | 48.516033, 34.6128617 | |
| Odesa | UA | 46.4845702, 30.7326047 | |
| Zaporizhzhia | UA | 47.83928419999999, 35.13870970000001 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Kostiantynivka | UA | 48.52394289999999, 37.7075811 | |
| Lyman | UA | 48.9897585, 37.8049964 | |
| Sloviansk | UA | 48.8532, 37.6053 | |
| Kramatorsk | UA | 48.738967, 37.58435 | |
| Dachne | UA | 48.4245004, 37.8789634 | |
| South Slobozhansky axis | UA | 49.5944382, 36.5290231 | |
| Huliaipole | UA | 47.6607145, 36.2732384 | |
| Orikhiv | UA | 47.5658802, 35.7876745 | |
| Tersyanka | UA | 47.8853395, 35.8918537 | |
| Voskresenka | UA | 47.47032309999999, 36.3613708 | |
| Ivan Vazov Street, Kherson | UA | 46.635417, 32.616867 | |
| Kyiv | UA | 50.4503596, 30.5245025 | |
| Pivnichnyi Bridge | UA | 50.4928545, 30.5432049 | |
| Pavlohrad | UA | 48.5294478, 35.9032574 | |
| Kremenchuk refinery | UA | 49.065783, 33.410033 | |
| Kropyvnytskyi | UA | 48.5070977, 32.2641984 | |
| Kharkiv | UA | 50.00201269999999, 36.3073994 | |
| Chuhuiv | UA | 49.8321564, 36.6865124 | |
| Lysychansk | UA | 48.9110806, 38.4264294 | |
| Chornomorsk | UA | 46.2952236, 30.6480855 | |
| Nizhnekamsk | RU | 55.613196, 51.8469974 | |
| TAIF-NK | RU | 55.619055, 51.9306913 | |
| JSC Monolit, Trubchevsk | RU | 52.5801951, 33.7619462 | |
| Akhtubinsk airfield | RU | 48.2838171, 46.1718889 | |
| Taganrog | RU | 47.2125752, 38.9159658 | |
| R-280 road corridor near Taganrog | RU | 47.2755857, 38.8568672 | |
| Kursk | RU | 51.7482395, 36.1947023 | |
| Prilepy | RU | 51.8482353, 35.2619445 | |
| Pervomayskoye | RU | 52.896888, 33.5987229 | |
| Dareevsk | RU | 52.42685239999999, 33.2063496 | |
| Kryvyi Rih | UA | 47.910483, 33.391783 | |
| Nikopol | UA | 47.56746, 34.394815 | |
| Okhtyrka | UA | 50.3150962, 34.9005644 |
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.