Nightwatch
HomeMapNewsMilitary PulseSituation ReportsDaily ReportsList ViewVideosCyber Threats
Sign In
Contact Support
Intelligence archive
Historical intelligence

Situation Report

Archived operational intelligence briefing retained for historical analysis.

Intelligence brief / archived issue

Situation Update (UTC)

Key reported developments

  • Ulyanovsk, Ulyanovsk Oblast, Russia — Governor’s statement relayed by ТАСС and Треш Ульяновск 😱 said a UAV attack injured eight people, including one child: seven adults and one child; five adults were in moderate condition and the rest in light condition; the child was in moderate condition; all were receiving medical care; medical services were placed on high readiness with additional hospital beds; the attack threat persisted. (Event time not supplied; message timestamps 2026-09-25 04:01:30 and 04:01:56 UTC; senders ТАСС and Треш Ульяновск 😱; MEDIUM that the official statement was made and relayed, LOW for independently verified casualty figures.)

  • Ulyanovsk, Ulyanovsk Oblast, Russia — The city administration, relayed by Треш Ульяновск 😱, said preliminary information indicated that Ulyanovsk life-support systems and utility supply were not disrupted. The same sender reported that in-person classes at UlGTU were cancelled for the day and would be held remotely. (Event time not supplied; message timestamps 2026-09-25 03:44:01 and 03:39:06 UTC; sender Треш Ульяновск 😱; MEDIUM for the relayed local statements, LOW for the full operational picture.)

  • Zaporizhzhia city, Zaporizhzhia Oblast, Ukraine — Zaporizhzhia OVA, relayed by РБК-Україна and posted by Михайло Семікін - Запорізька ОВА and Оперативний ЗСУ, reported a morning Russian attack with a hit on a medical facility and a fire there. Later preliminary information said five people were evacuated from the damaged medical facility, one man received light injuries, and no other injured people were reported as of that time. Official photo albums showed exterior and interior damage at a multi-story building. (Event time described only as morning, exact time not supplied; message timestamps 2026-09-25 03:41:40, 03:46:31, 03:58:20, and 03:58:37 UTC; senders РБК-Україна, Михайло Семікін - Запорізька ОВА, and Оперативний ЗСУ; MEDIUM for the official reports, LOW for independent verification of cause, target status, and casualty count.)

  • Voronezh, Voronezh Oblast, Russia — Exilenova+ posted a photo caption claiming that “Voronezhsintezkauchuk” was burning after an attack. The source’s own accompanying assessment rates reliability LOW, noting that the single photo shows dark smoke over an urban intersection but no visible attack, facility signage, timestamp, geolocation, or independent confirmation. (Event time not supplied; message timestamps 2026-09-25 03:39:39–03:39:40 UTC; sender Exilenova+; LOW.)

  • Ulyanovsk, Ulyanovsk Oblast, Russia — Exilenova+ posted a photo caption claiming a hit on the research and production enterprise “Zavod Iskra” in Ulyanovsk. The source’s own accompanying text rates reliability LOW and says the image does not identify the facility, date, or geolocation, and has no official confirmation. (Event time not supplied; message timestamps 2026-09-25 03:42:35–03:42:36 UTC; sender Exilenova+; LOW.)

  • Ukrainian General Staff posted an infographic claiming cumulative Russian combat losses from 24.02.22 to 25.09.26, including personnel ~1,525,570 (+1,590), UAVs 532,575 (+1,223), artillery systems 50,275 (+35), tanks 12,369 (+2), and armored combat vehicles 25,415 (+13). The accompanying source assessment rates the substantive loss claims LOW and flags the 25.09.2026 reporting period as inconsistent with its stated collection date. (Event time not supplied; message timestamps 2026-09-25 03:45:08–03:45:09 UTC; sender Генеральний штаб ЗСУ; LOW for substantive loss claims; HIGH only that the official graphic was posted, per the source assessment.)

  • Moscow, Russia — Новости Москвы reported restricted movement on MCD-2 and MCD-4 sections because of works after a beam fell onto the tracks at Kalachyovskaya. MCD-2 was to follow a shortened route to Maryina Roshcha, Krasny Baltiets, Rizhskaya, and Kursky station; MCD-4 was to run to Belorussky and Kursky stations and to Ploshchad Trekh Vokzalov. (Event time not supplied; message timestamp 2026-09-25 04:00:12 UTC; sender Новости Москвы; MEDIUM that the post appeared, LOW for the full operational picture.)

  • Orikhiv area / Dnieper direction, Zaporizhzhia Oblast, Ukraine — Дневник Десантника🇷🇺 posted a video summary claiming that Ulyanovsk paratroopers set ambushes using loitering drones on approaches to Orikhiv and that a Lancet crew of the 98th Guards Airborne Division struck a military transport vehicle and a supply truck. The same source posted an accompanying assessment describing the video as thermal footage of a drone engagement but saying unit attribution and exact location remain unverified. (Event time not supplied; message timestamps 2026-09-25 04:01:01–04:01:02 UTC; sender Дневник Десантника🇷🇺; MEDIUM that the channel posted the video and claims, LOW for independent verification of location, unit, and outcome.)

Reported situation by area

  • Ulyanovsk, Ulyanovsk Oblast, Russia (new evidence): New official/local statements add an injury total of eight people, including one child, and say medical services were on high readiness with additional beds and that the UAV threat persisted. The city administration said preliminary information indicated life-support and utility supply were not disrupted, and UlGTU in-person classes were cancelled. An unverified Exilenova+ photo claims a hit on the Zavod Iskra research and production enterprise, but the source rates that claim LOW and supplies no geolocation or timestamp. The previous situation report had already described a “massive” UAV attack, infrastructure damage, injured people, an operational headquarters, and local transport restrictions; those baseline items receive no independent corroboration in this batch. (Message timestamps 2026-09-25 03:39:06–04:01:56 UTC; senders Треш Ульяновск 😱, ТАСС, and Exilenova+; MEDIUM for relayed official/local statements, LOW for independently verified scale, damage, and casualties.)

  • Zaporizhzhia city, Zaporizhzhia Oblast, Ukraine (updated official reports): New official reporting says a morning Russian attack hit a medical facility, causing a fire; five people were evacuated, one man was preliminarily lightly injured, and no other injured people were reported as of the latest message. Official photo albums posted by Михайло Семікін - Запорізька ОВА and relayed by Оперативний ЗСУ show exterior and interior damage at a multi-story building. The previous situation report already described a morning attack, hits on city objects, a fire in a medical facility, and one preliminary injured man; the new batch adds evacuation and casualty-severity details and more official imagery. No exact event time, facility name, or independent verification is supplied. (Message timestamps 2026-09-25 03:41:40–03:58:38 UTC; senders РБК-Україна, Михайло Семікін - Запорізька ОВА, and Оперативний ЗСУ; MEDIUM for the official reports, LOW for independent battle-damage assessment.)

  • Voronezh, Voronezh Oblast, Russia (new but unverified): Exilenova+ posted a single photo caption claiming a fire at Voronezhsintezkauchuk after an attack. The source’s own assessment says the image shows smoke but cannot tie it to the named plant or to an attack, and has no timestamp or geolocation. No independent or official confirmation appears in this batch. (Message timestamps 2026-09-25 03:39:39–03:39:40 UTC; sender Exilenova+; LOW.)

  • Moscow, Russia (new administrative/transport report): Новости Москвы reported restricted movement on MCD-2 and MCD-4 because of works after a beam fell onto tracks at Kalachyovskaya, with shortened routes and station changes. The supplied message does not link the incident to the war or to any attack. (Message timestamp 2026-09-25 04:00:12 UTC; sender Новости Москвы; MEDIUM that the post appeared, LOW for full operational picture.)

  • Orikhiv area / Dnieper direction, Zaporizhzhia Oblast, Ukraine (new but attributed claim): Дневник Десантника🇷🇺 claimed that Ulyanovsk paratroopers used loitering drones to ambush enemy targets on approaches to Orikhiv and that a Lancet crew of the 98th Guards Airborne Division struck a military transport vehicle and a supply truck. The channel’s own accompanying assessment describes the video as thermal footage of a drone engagement but says the location and affiliation remain unverified. No independent confirmation appears in this batch. (Message timestamps 2026-09-25 04:01:01–04:01:02 UTC; sender Дневник Десантника🇷🇺; MEDIUM that the channel posted the video and claims, LOW for independent verification.)

  • No new ground-fighting evidence: This batch contains no new evidence of ground fighting, territorial control, or unit-level activity in the Kharkiv, Donetsk, Kherson, Luhansk, or other land sectors. The previous baseline’s areas receive no new evidence here. Absence from this batch does not establish that any area is quiet or unchanged.

Reported strikes and air-defense activity

  • Ulyanovsk, Ulyanovsk Oblast, Russia: The governor’s statement, relayed by ТАСС and Треш Ульяновск 😱, said a UAV attack injured eight people, including one child; medical services were on high readiness and the threat persisted. No interception count, launch origin, weapon type, casualty total beyond the reported breakdown, or independent battle-damage assessment was supplied. Because ТАСС and Треш Ульяновск 😱 cite the same governor, they are not independent corroboration of each other. (Message timestamps 2026-09-25 04:01:30 and 04:01:56 UTC; senders ТАСС and Треш Ульяновск 😱; MEDIUM for the relayed official statement, LOW for independently verified effects.)

  • Zaporizhzhia city, Zaporizhzhia Oblast, Ukraine: Zaporizhzhia OVA, relayed by РБК-Україна and posted by Михайло Семікін - Запорізька ОВА and Оперативний ЗСУ, reported a morning Russian attack with a hit on a medical facility and a fire there; five people were evacuated and one man was preliminarily lightly injured. No munition type, interception, impact remnant, or independent battle-damage assessment was supplied. (Message timestamps 2026-09-25 03:41:40–03:58:38 UTC; senders РБК-Україна, Михайло Семікін - Запорізька ОВА, and Оперативний ЗСУ; MEDIUM for the official reports, LOW for independent verification.)

  • Voronezh, Voronezh Oblast, Russia: Exilenova+ claimed, in a photo caption, a fire at Voronezhsintezkauchuk after an attack. The source’s own assessment rates the claim LOW, saying the single image shows smoke but no visible attack, facility, timestamp, or geolocation. (Message timestamps 2026-09-25 03:39:39–03:39:40 UTC; sender Exilenova+; LOW.)

  • Ulyanovsk, Ulyanovsk Oblast, Russia: Exilenova+ claimed, in a photo caption, a hit on the Zavod Iskra research and production enterprise. The source’s own assessment rates the claim LOW and says the image cannot identify the facility, date, or location, and has no official confirmation. (Message timestamps 2026-09-25 03:42:35–03:42:36 UTC; sender Exilenova+; LOW.)

  • No new Ukrainian Air Force alerts or air-defense engagement reports: This batch contains no new Ukrainian Air Force warning messages or air-defense engagement reports. The previous situation report’s alerts receive no new evidence here. No interception counts or outcomes are supplied for the reported Ulyanovsk or Zaporizhzhia events.

Reported Russian activity

  • Ulyanovsk Oblast official statements: The governor’s statement, relayed by ТАСС and Треш Ульяновск 😱, said a UAV attack injured eight people, including one child; five adults were in moderate condition and the rest in light condition; the child was in moderate condition; medical services were on high readiness with additional beds; the threat persisted. The city administration, relayed by Треш Ульяновск 😱, said preliminary information indicated life-support and utility supply were not disrupted. The previous situation report had described a governor’s statement about repelling a “massive” UAV attack, infrastructure damage, injured people, an operational headquarters, and a prohibition on distributing UAV imagery; the new batch adds the injury breakdown and utility/education details. (Message timestamps 2026-09-25 03:39:06, 03:44:01, 04:01:30, and 04:01:56 UTC; senders ТАСС and Треш Ульяновск 😱; MEDIUM for the relayed statements, LOW for independent verification.)

  • Russian diplomatic reporting: ТАСС, citing CNN, reported that Dmitriev discussed with Witkoff and Kushner “cooperation between Russia and the USA and a peaceful settlement of the conflict in Ukraine” on 24 September. No further details or independent confirmation were supplied. (Event time reported as 24 September, exact time not supplied; message timestamp 2026-09-25 03:42:01 UTC; sender ТАСС; LOW for independent verification.)

  • Russian VDV channel claims: Дневник Десантника🇷🇺 claimed that Ulyanovsk paratroopers used loitering drones to ambush enemy targets on approaches to Orikhiv and that a Lancet crew of the 98th Guards Airborne Division struck a military transport vehicle and a supply truck. The channel’s accompanying assessment describes the video as thermal footage of a drone engagement but says attribution and exact location remain unverified. This is a pro-Russian military-themed channel item, not an independently confirmed combat report. (Message timestamps 2026-09-25 04:01:01–04:01:02 UTC; sender Дневник Десантника🇷🇺; MEDIUM that the post appeared, LOW for independent verification.)

  • No Russian Ministry of Defense statement: No Russian Ministry of Defense statement, unit designation, or official casualty statement appears in this batch beyond the described governor’s statements, ТАСС diplomatic report, and the VDV-themed channel material.

Reported Ukrainian activity

  • Zaporizhzhia OVA reporting and imagery: Zaporizhzhia OVA, via Михайло Семікін - Запорізька ОВА and relayed by РБК-Україна and Оперативний ЗСУ, reported a morning Russian attack on a medical facility, a fire, five evacuated people, and one preliminarily lightly injured man. Official photo albums showed exterior and interior damage at a multi-story building. The cause and target status remain attributed to Ukrainian official sources and lack independent verification in this batch. (Message timestamps 2026-09-25 03:41:40–03:58:38 UTC; senders РБК-Україна, Михайло Семікін - Запорізька ОВА, and Оперативний ЗСУ; MEDIUM for the official reports, LOW for independent verification.)

  • Ukrainian General Staff loss infographic: Генеральний штаб ЗСУ posted an infographic claiming cumulative Russian losses through 25.09.2026, including personnel ~1,525,570 (+1,590), UAVs 532,575 (+1,223), artillery systems 50,275 (+35), tanks 12,369 (+2), and armored combat vehicles 25,415 (+13). The accompanying source assessment rates the substantive loss claims LOW and flags the 25.09.2026 reporting period as inconsistent with its stated collection date. (Message timestamps 2026-09-25 03:45:08–03:45:09 UTC; sender Генеральний штаб ЗСУ; LOW for substantive loss claims; HIGH only that the official graphic was posted, per the source assessment.)

  • No Ukrainian official claim of ground operations or deep strikes: This batch contains no Ukrainian General Staff or Ministry of Defense claim of ground operations, territorial control, or deep strikes on Russian territory. No Ukrainian official source in this batch confirms the Exilenova+ claims about Voronezh or Zavod Iskra. The RBC-Україна item about Democratic senators is a media relay of a foreign political statement, not a Ukrainian military report.

Civilian and infrastructure impact

  • Ulyanovsk, Ulyanovsk Oblast, Russia: The governor’s statement, relayed by ТАСС and Треш Ульяновск 😱, reported eight injured people, including one child; seven adults and one child, with five adults in moderate condition and the rest in light condition, and the child in moderate condition. Medical services were placed on high readiness with additional beds. The city administration said preliminary information indicated life-support systems and utility supply were not disrupted. UlGTU cancelled in-person classes and moved them online. (Message timestamps 2026-09-25 03:39:06, 03:44:01, 04:01:30, and 04:01:56 UTC; senders ТАСС and Треш Ульяновск 😱; MEDIUM for the relayed official/local statements, LOW for independently confirmed casualty and impact details.)

  • Zaporizhzhia city, Zaporizhzhia Oblast, Ukraine: Official Ukrainian reports said a medical facility was hit and caught fire; five people were evacuated, one man was preliminarily lightly injured, and no other injured people were reported as of the latest message. Official photos showed exterior and interior damage at a multi-story building, including blown-out windows, smoke, debris, and damaged hospital-style furniture. No fatality figure, facility name, or consolidated damage assessment was supplied. (Message timestamps 2026-09-25 03:41:40–03:58:38 UTC; senders РБК-Україна, Михайло Семікін - Запорізька ОВА, and Оперативний ЗСУ; MEDIUM for the official reports, LOW for independent verification.)

  • Voronezh, Voronezh Oblast, Russia: Exilenova+ claimed a fire at Voronezhsintezkauchuk after an attack, but the source’s own assessment rates the claim LOW, with no visible facility, timestamp, geolocation, casualty, or independent confirmation. (Message timestamps 2026-09-25 03:39:39–03:39:40 UTC; sender Exilenova+; LOW.)

  • Moscow, Russia: Новости Москвы reported restricted movement on MCD-2 and MCD-4 because of works after a beam fell onto tracks at Kalachyovskaya, with shortened routes and station changes. No casualties or link to the war were supplied in the message. (Message timestamp 2026-09-25 04:00:12 UTC; sender Новости Москвы; MEDIUM that the post appeared, LOW for full operational picture.)

  • No additional displacement reports: Beyond the reported Ulyanovsk education and utility statements, this batch contains no new displacement, service-restoration, or utility-disruption reports for other areas.

Information environment and disputed claims

  • Ulyanovsk official/local framing: ТАСС and Треш Ульяновск 😱 relay the same governor’s statement on eight injured people, including one child. Because they cite the same official source, they are not independent corroboration of the scale, damage, or casualty figures. The city administration’s statement on utilities is also a relayed official claim. (Message timestamps 2026-09-25 03:44:01, 04:01:30, and 04:01:56 UTC; senders ТАСС and Треш Ульяновск 😱; MEDIUM for the statements, LOW for independent verification.)

  • Exilenova+ imagery: Exilenova+ posted two single-photo claims: a fire at Voronezhsintezkauchuk after an attack, and a hit on Zavod Iskra in Ulyanovsk. The source’s own accompanying text rates both LOW, notes no geolocation or timestamp, and says the images cannot independently tie the smoke or fireball to the named facility or to an attack. (Message timestamps 2026-09-25 03:39:39–03:39:40 and 03:42:35–03:42:36 UTC; sender Exilenova+; LOW.)

  • Zaporizhzhia official account: Zaporizhzhia OVA provided an official Ukrainian account of a morning attack on a medical facility, a fire, five evacuated people, and one preliminarily lightly injured man, with multiple watermarked photos. The source assessment rates the visible damage and emergency response as HIGH for the official imagery, but the cause, casualty count, and attribution as MEDIUM and not independently confirmed in this batch. (Message timestamps 2026-09-25 03:41:40–03:58:38 UTC; senders РБК-Україна, Михайло Семікін - Запорізька ОВА, and Оперативний ЗСУ; MEDIUM for official reports, LOW for independent verification.)

  • Ukrainian General Staff loss infographic: The infographic claims extraordinary cumulative Russian losses through 25.09.2026. The accompanying source assessment rates the substantive numbers LOW, notes the future-dated reporting period as inconsistent with its stated collection date, and says the post provides no methodology, geolocation, or primary evidence. (Message timestamps 2026-09-25 03:45:08–03:45:09 UTC; sender Генеральний штаб ЗСУ; LOW for substantive loss claims; HIGH only that the official graphic was posted, per the source assessment.)

  • Russian VDV channel framing: Дневник Десантника🇷🇺 used pro-Russian military terminology and claimed effective drone ambushes and Lancet strikes. The accompanying assessment describes the video as thermal footage of a drone engagement but says the location and affiliation remain unverified and notes that the channel’s framing aligns with Russian military information themes. (Message timestamps 2026-09-25 04:01:01–04:01:02 UTC; sender Дневник Десантника🇷🇺; MEDIUM that the post appeared, LOW for independent verification.)

  • Diplomatic and political claims: ТАСС, citing CNN, reported Dmitriev-Witkoff-Kushner discussions on 24 September about Russia-U.S. cooperation and a peaceful settlement of the Ukraine conflict. Separately, РБК-Україна relayed a claim that unnamed Democratic senators urged Trump to implement sanctions against Russia and Iran and criticized Chinese dual-use exports and Russian oil purchases; the RBC item uses a generic Senate hearing photo and the accompanying source assessment rates it LOW. No primary documents, named senators, or official confirmation appear in the batch. (Message timestamps 2026-09-25 03:42:01 and 03:51:01–03:51:02 UTC; senders ТАСС and РБК-Україна; LOW for independent verification.)

  • Analytic support: The supplied Dempster-Shafer beliefs place the largest single mass on “Uncertainty” (0.626067), with smaller masses on a healthcare-infrastructure attack in Zaporizhzhia (0.103798), Ukrainian information warfare (0.056002), infrastructure damage in Zaporizhzhia (0.052471), transportation damage at Kalachyovskaya (0.031045), and related hypotheses. These are analytic support values only and are not independent corroboration of any event in this batch.

Evidence limitations and unresolved questions

  • No exact event times are supplied for the reported Ulyanovsk UAV attack or the reported Zaporizhzhia attack; the latter is described only as “morning.”

  • No independent geolocation, official consolidated casualty total, or battle-damage assessment is supplied for the Ulyanovsk events, the Zaporizhzhia medical-facility damage, the claimed Voronezh industrial fire, or the claimed Zavod Iskra hit.

  • The Ulyanovsk injury figures come from the governor’s statement relayed by ТАСС and Треш Ульяновск 😱. Because both relay the same official source, they are not independent corroboration of each other. The figures remain preliminary, and no independent casualty count is supplied.

  • The Zaporizhzhia medical-facility claim lacks a facility name, precise address, munition type, impact remnant, or independent confirmation. The five evacuated people and one preliminarily lightly injured man are official Ukrainian reports and remain subject to revision.

  • No interception counts, engagement results, or damage outcomes are supplied for the reported Ulyanovsk attack. This batch contains no new Ukrainian Air Force alert messages.

  • The Ukrainian General Staff loss infographic contains a reporting period ending 25.09.2026 that the accompanying source assessment flags as inconsistent with its stated collection date; the substantive figures are unverified.

  • The Exilenova+ claims about Voronezhsintezkauchuk and Zavod Iskra have no geolocation, timestamp, original metadata, official confirmation, or independent corroboration; the source rates them LOW.

  • The Moscow MCD-2 and MCD-4 disruption is reported as caused by works after a beam fell onto tracks, but no cause beyond that statement is supplied, and no link to the war is established in the message.

  • No new evidence in this batch covers ground fighting, territorial control, equipment losses beyond the Ukrainian General Staff infographic claim, prisoner exchanges, occupation administration, or service restoration in Ukraine. The previous baseline’s areas receive no new evidence here. Silence in this batch does not establish that any of those situations is unchanged.

  • The supplied weather context as of 2026-09-25T04:00 UTC records numeric observations at five reference points; no message in this batch ties those observations to a specific event.

Previous (2026-09-25 03:40:39.393177+00)