Armed conflict · Single source · unverified
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. [1]
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
1 source family · 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
RBC-Ukraine, citing an official source of an involved party, reported residential damage and fire in Kirishi on 9 November 2026.
Facts at a glance
- Drone type
- No named drone type is recorded in this dossier.
- Hit / damaged
- 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
- Source families
- One source family is recorded; there is no second independent confirmation
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
One source, not yet confirmed by a second independent source; automatically published, not yet reviewed by an editor. The report may be incomplete or wrong.
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
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.
- Unknown dependency
- RBC-Ukraine (9 November 2026) [1]
Show source graph
Left: publishers; right: recorded original statement. Converging lines show shared origin, not publication order. Dashed nodes have unknown dependency.
What we know
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
RBC-Ukraine published a report on this incident. [1]
Original sources (1)
1 source family · a count of sources is not a verification score
1RBC-Ukraine (9 November 2026)09 Nov 2026 · source family: RbcSearch 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 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 2, updated 09 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-11-09-e429e61ef7/v2/
APA
DroneLedger editorial team. (09 Nov 2026). Drone report in Kirishi, Russia (Dossier auto-ru-2026-11-09-e429e61ef7, revision 2). https://droneincidents.com/incident/auto-ru-2026-11-09-e429e61ef7/v2/
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
- 2
- Release
- 20261109T055425778531-1a5294
- Publication date
- 09 Nov 2026
- Accessed
- 09 Nov 2026
- Permanent URL
- https://droneincidents.com/incident/auto-ru-2026-11-09-e429e61ef7/v2/
- Hashed file
- JSON · SHA-256
0536167a6713f76d34b45c365deb4ed8990d3b7335bf9ed61f5182de2bb4f3f7
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 2; release 20261109T055425778531-1a5294; published 09 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-11-09-e429e61ef7/v2/ Accessed 09 Nov 2026. SHA-256 0536167a6713f76d34b45c365deb4ed8990d3b7335bf9ed61f5182de2bb4f3f7 (https://droneincidents.com/data/citations/incident/auto-ru-2026-11-09-e429e61ef7/r2/0536167a6713f76d34b45c365deb4ed8990d3b7335bf9ed61f5182de2bb4f3f7/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