Armed conflict
Drone report in Kirishi, Russia
Kirishi (Кириши) · 09 Nov 2026 · event date · exact location not established
According to a cited source, drones were reported in Kirishi, Russia on 9 November 2026. According to TSN, drones were reported in Kirishi, Russia on 9 November 2026. [1][2]
Drone presence is reported. Consequences are reported. The operator is not established.
DroneLedger editorial team, publisher and editor responsible for this project.
Automatically compiled from cited sources; no individual human review is recorded. Method and corrections
2 source families · a count of sources is not a verification score
Automatically compiled · sources retrieved on 09 Nov 2026 · Dossier updated 09 Nov 2026
What do we know now?
What happened
TSN, citing an official source of an involved party, reported industrial damage in Kirishi on 9 November 2026. RBC-Ukraine, citing an official source of an involved party, reported residential damage and fire.
Facts at a glance
- Drone type
- No named drone type is recorded in this dossier.
- Hit / damaged
- According to TSN, citing an official source of an involved party, the report published on 9 November 2026, 05:45 UTC+02:00 describes industrial damage
- According to RBC-Ukraine, citing an official source of an involved party, the report published on 9 November 2026, 05:15 UTC+02:00 describes residential damage; fire
- Human consequences
- Casualty details are not established in this dossier.
- Who reported what
- RBC-Ukraine: Assessment of drone involvement; hit / damaged
- TSN: Assessment of drone involvement; hit / damaged
- Source families
- 2 source families are recorded; republication is not independent confirmation. Their independence has not yet been established by an editor
Further details are not known from the cited sources.
Timeline
Three clocks, one reading line
Shared calendar-day axis, from left to right. Bars mark days or reporting windows, not durations. Publication and revision clocks are not event clocks. Missing clocks remain unknown; the table gives all available precision and source links. The plot follows recorded calendar dates; time zones may differ. It establishes neither within-day order nor causality.
| Track | Recorded date / time |
|---|---|
| 1 · Event |
|
| 2 · Source publication | |
| 3 · Dossier revisions |
What remains uncertain?
- Was a drone established? A published investigation or identification could resolve this.
- Who operated it, and why? An attributed investigation finding is missing.
Check the evidence
Automatically published from the cited sources; their independence and this dossier have not yet been reviewed by an editor.
For conflict incidents only the city or region is shown, never a precise location, and no operational details. This is not a warning service: for incoming threats, follow official alerts.
How to read this dossier
Automatically compiled and published from 2 cited articles that each report drone presence at this place and date. An automatic check found them to describe the same incident and found claims that appear to come from at least two different sources; that independence has not been established by an editor. Claims are shown as made by the named source; claims by a party to a conflict remain claims. For conflict incidents only the city or region named in the reports is shown, never a precise location, and no operational details; the cited articles may contain more precise details than this dossier. This is not a warning service: for incoming threats, follow official alerts.
Source genealogy
Grouped by recorded original statement, not by publisher. Unmapped sources have unknown dependency; linked statements may also share an earlier origin. This is not an independence score.
Show source graph
Left: publishers; right: recorded original statement. Converging lines show shared origin, not publication order. Dashed nodes have unknown dependency.
Read with a source omitted
Reading aid: switch off a source or family to inspect the remaining visible support below. Evidence status is not recalculated.
No source-indexed claims recorded. No support can be inferred from the number of sources.
What we know
According to an official source of an involved party, via TSN, as of 09 Nov 2026 05:45 UTC+02:00: industrial damage. According to an official source of an involved party, via RBC-Ukraine, as of 09 Nov 2026 05:15 UTC+02:00: residential damage and fire.
Data
- No structured detail recorded
- Fell near · Intercepted (claimed) · Effects
What remains unknown
Not yet assessed by an editor: impact, exact location, operator and intent.
Not assessed in this automatic report; see the cited sources for any claims of responsibility.
How the story changed
Original sources (2)
2 source families · a count of sources is not a verification score
1RBC-Ukraine (9 November 2026)09 Nov 2026 · source family: Rbc2TSN (9 November 2026)09 Nov 2026 · source family: TsnSearch native-language coverage
External Google News search using the recorded place and dossier date. Results may concern other events; they have not been reviewed by DroneLedger.
Editorial changes
- Revision 4 · 09 Nov 2026Updated automatically after the new revision passed the automatic checks. (Source revision 3.)
- Revision 2 · 09 Nov 2026Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.
Cite this dossier
Chicago
DroneLedger editorial team. “Drone report in Kirishi, Russia.” Dossier auto-ru-2026-11-09-e429e61ef7, revision 4, updated 09 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-11-09-e429e61ef7/v4/
APA
DroneLedger editorial team. (09 Nov 2026). Drone report in Kirishi, Russia (Dossier auto-ru-2026-11-09-e429e61ef7, revision 4). https://droneincidents.com/incident/auto-ru-2026-11-09-e429e61ef7/v4/
Cite the revision you used: later revisions may change evidence states.
Cite this version
- Maker
- DroneLedger editorial team
- ID
- auto-ru-2026-11-09-e429e61ef7
- Revision or edition
- 4
- Release
- 20261109T055425778531-1a5294
- Publication date
- 09 Nov 2026
- Accessed
- 09 Nov 2026
- Permanent URL
- https://droneincidents.com/incident/auto-ru-2026-11-09-e429e61ef7/v4/
- Hashed file
- JSON · SHA-256
69bea1932d74197cead587c87285b5b2f44cd56642c24b7800bde428c672c097
Dataset DOI for this exact version: Not yet in a DOI snapshot · DOI binding manifest
Dataset DOI (series, not this revision): 10.5281/zenodo.23345422
DroneLedger editorial team. Drone report in Kirishi, Russia. ID auto-ru-2026-11-09-e429e61ef7; revision or edition 4; release 20261109T055425778531-1a5294; published 09 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-11-09-e429e61ef7/v4/ Accessed 09 Nov 2026. SHA-256 69bea1932d74197cead587c87285b5b2f44cd56642c24b7800bde428c672c097 (https://droneincidents.com/data/citations/incident/auto-ru-2026-11-09-e429e61ef7/r4/69bea1932d74197cead587c87285b5b2f44cd56642c24b7800bde428c672c097/data.json). Not yet in a DOI snapshot.
Citation uses the English reference edition. Access date is the UTC date when this page was built; change it to your consultation date when reusing the citation.
Editorial pack (print / PDF)Follow this dossier (feed)Earlier versions