DroneLedger

Armed conflict · Single source · unverified

Drone report in Starodub, Russia

Starodub (Стародуб) · 30 Oct 2026 · event date · exact location not established

According to DW, drones were reported in Starodub, Russia on 30 October 2026. [1]

Evidence status: drone reported; impact not established; operator not established.

Drone presenceReported[1]
ImpactNot established
AttributionNot established

1 source family · a count of sources is not a verification score

Automatically compiled · sources retrieved on 03 Nov 2026 · Dossier updated 03 Nov 2026

You are viewing revision 2 as published on 03 Nov 2026. The dossier text, evidence states, claims and sources of this revision are fixed; catalogue context such as cost estimates is not shown here. View the current version

What do we know now?

What happened

DW reported a drone incident in Starodub on 30 October 2026.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Human consequences
  • Casualty details are not established in this dossier.
Who reported what
  • DW: Assessment of drone involvement
Source families
  • One source family is recorded; there is no second independent confirmation
No structured detail recorded
  • Hit / damaged · Fell near · Intercepted (claimed) · Effects

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.

Three clocks, one reading line
TrackRecorded date / time
1 · Event
  • · Calendar day; time unknown
2 · Source publication
3 · Dossier revisions

What remains uncertain?

  • Was a drone established? A published investigation or identification could resolve this.
  • What were the consequences? Source-bound impact reporting is missing.
  • 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.

  1. Unknown dependency
    • DW (30 October 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

No eligible attributed impact claim is included; this does not mean no impact occurred.

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

  1. DW published a report on this incident. [1]

Original sources (1)

1 source family · a count of sources is not a verification score

1DW (30 October 2026)30 Oct 2026 · source family: Dw

Search 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

  1. Revision 2 · 03 Nov 2026Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.

Cite this dossier

Permanent page · Revision 2

Chicago

DroneLedger. “Drone report in Starodub, Russia.” Dossier auto-ru-2026-10-30-0c022286ea, revision 2, updated 03 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-10-30-0c022286ea/v2/

APA

DroneLedger. (03 Nov 2026). Drone report in Starodub, Russia (Dossier auto-ru-2026-10-30-0c022286ea, revision 2). https://droneincidents.com/incident/auto-ru-2026-10-30-0c022286ea/v2/

Dataset DOI: 10.5281/zenodo.23345422

Cite the revision you used: later revisions may change evidence states.

Editorial pack (print / PDF)Follow this dossier (feed)Earlier versions