DroneLedger

Armed conflict

Residential damage reported after drone attack in Yaroslavl

Yaroslavl (Ярославль) · 03 Nov 2026 · event date · city reference point on the map; exact location not yet known

According to Ukrainska Pravda, drones were reported in Yaroslavl, Russia on 3 November 2026. According to RBC-Ukraine, drones were reported in Yaroslavl, Russia on 3 November 2026. [1][2][3]

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

Drone presenceReported[1][2][3]
ImpactReported[3]
AttributionNot established

3 source families · a count of sources is not a verification score

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

Latest material change

Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.

Revision 4

What do we know now?

What happened

RBC-Ukraine reported a hit or damage to industrial sites and a hit or damage to oil facilities in Yaroslavl on 3 November 2026. Interfax, citing Mikhail Evraev, reported a hit or damage to oil facilities, a hit or damage to industrial sites, a hit or damage to apartment buildings, a hit or damage to residential property and a hit or damage to cars.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Hit / damaged
  • According to RBC-Ukraine, a hit or damage was reported to an object in the category “industrial sites” (source wording: підприємстві)
  • According to RBC-Ukraine, a hit or damage was reported to an object in the category “oil facilities” (source wording: нпз)
  • According to Interfax, citing Mikhail Evraev, a hit or damage was reported to an object in the category “oil facilities” (source wording: нефтеперерабатывающего)
  • According to Interfax, citing Mikhail Evraev, a hit or damage was reported to an object in the category “industrial sites” (source wording: завода)
  • According to Interfax, citing Mikhail Evraev, a hit or damage was reported to an object in the category “apartment buildings” (source wording: многоквартирных)
  • According to Interfax, citing Mikhail Evraev, a hit or damage was reported to residential property
  • According to Interfax, citing Mikhail Evraev, a hit or damage was reported to an object in the category “cars” (source wording: автомобили)
  • According to Interfax, citing an official source of an involved party, the report published on 3 November 2026, 08:37 UTC+03:00 describes civilian infrastructure damage; damage; residential damage; vehicle damage
Human consequences
  • Casualty details are not established in this dossier.
Who reported what
Source families
  • 3 source families are recorded; republication is not independent confirmation. Their independence has not yet been established by an editor
No structured detail recorded
  • 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

Citable archive context

50 km / 90 days
Point-distance context is not established: this dossier has no usable own coordinates. Display reference points are not substituted.

Region / category / 30 days
Other Armed conflict single-event dossiers in Europe during 04 Oct 2026–02 Nov 2026: 174; currently labelled drone-confirmed: 0.

Counted dossiers (current revisions)

Archive snapshot 03 Nov 2026, 07:02 UTC; release 20261103T070210236002-1d4f50. Current evidence labels, not what was known on the event date. Earlier calendar days only; waves, reporting windows and statement dates are excluded. Coverage is selective; these are not world totals, risk estimates or evidence of a common cause.

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 3 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 passage
  • RBC-Ukraine · “підприємстві” RBC-Ukraine
  • RBC-Ukraine · “нпз” RBC-Ukraine
  • Mikhail Evraev · “нефтеперерабатывающего” Interfax
  • Mikhail Evraev · “завода” Interfax
  • Mikhail Evraev · “многоквартирных” Interfax
  • Mikhail Evraev · “частных домах” Interfax
  • Mikhail Evraev · “автомобили” Interfax

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
    • Ukrainska Pravda (3 November 2026) [1]
    • RBC-Ukraine (3 November 2026) [2]
    • Interfax (3 November 2026) [3]
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.

Drones involved

The cited sources do not name the type of drone.

What we know

According to an official source of an involved party, via Interfax, as of 3 November 2026, 08:37 UTC+03:00: civilian infrastructure damage, damage, residential damage and vehicle damage.

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. Ukrainska Pravda published a report on this incident. [1]

  2. RBC-Ukraine published a report on this incident. [2]

  3. Interfax published a report on this incident. [3]

Original sources (3)

3 source families · a count of sources is not a verification score

1Ukrainska Pravda (3 November 2026)03 Nov 2026 · source family: Pravda

First observed:

2RBC-Ukraine (3 November 2026)03 Nov 2026 · source family: Rbc

First observed:

3Interfax (3 November 2026)03 Nov 2026 · source family: Interfax

First observed:

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.

Recorded fetches only; no exact edit time or interpretation. Unavailable does not mean removed.

Editorial changes

  1. Revision 4 · 03 Nov 2026Status change Impact: Not established → ReportedPublished automatically after passing the automatic checks (pilot); not yet reviewed by an editor.
  2. Revision 2 · 03 Nov 2026Same note as Revision 4

Story timeline

Published revisions; dates are revision dates, not event dates.

  1. Revision 4 · Current dossier ·

    Drone presence: Reported · Impact: Reported · Attribution: Not established

  2. Revision 2 ·

    Drone presence: Reported · Impact: Not established · Attribution: Not established

Current dossier

Earlier in this archive

Published single-event dossiers with an earlier established event date only. Counts describe this archive, not frequency, risk or a common cause.

Same country: 86
Same category: 238

Cite this dossier

Permanent page · Revision 4

Chicago

DroneLedger. “Residential damage reported after drone attack in Yaroslavl.” Dossier auto-ru-2026-11-03-be5ae3e387, revision 4, updated 03 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-11-03-be5ae3e387/v4/

APA

DroneLedger. (03 Nov 2026). Residential damage reported after drone attack in Yaroslavl (Dossier auto-ru-2026-11-03-be5ae3e387, revision 4). https://droneincidents.com/incident/auto-ru-2026-11-03-be5ae3e387/v4/

Dataset DOI: 10.5281/zenodo.23345422

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

YaroslavlMoscow
Approximate: city level
Reference marker and schematic precision area; not an incident position or measured error radius. Natural Earth boundaries; reference cities: GeoNames, CC BY 4.0.
Embed this dossier

No cookies, tracking or scripts. Reader browsers request this card from DroneLedger; standard server logs may record requests. This card updates with the next site release; reload to see changes.

Press graphics

SVG 16:9 SVG 1:1 SVG 9:16

What would help verify this dossier

  • A primary source or verifiable evidence that clarifies whether the reported object was a drone. Evidence for another explanation is welcome too.
  • A source identifying the event area at city or region level. A destination or reference point does not establish where an event occurred.

These are research questions based on the public dossier, not a checklist that guarantees confirmation. Editors review new sources and record any change as a new revision.

Suggest a public source

Share links to published material. Do not send private names, exact coordinates, live positions or flight paths.

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

Incident archive

Newest first. Select an incident to open its dossier.

D = was there a drone? · I = impact (closure, damage, injuries) · A = attribution (who was behind it). Solid = confirmed · striped = reported · grey = not established · struck through = debunked.

RU03 Nov 2026·Armed conflictNew

Residential damage reported after drone attack in Yaroslavl

YaroslavlAuto-compiledRU02 Nov 2026·Armed conflictNew

Drones shot down over Moscow, reports say

MoscowSingle source · unverifiedRU02 Nov 2026·Armed conflictNew

Drones shot down over Voronezh Oblast, governor says

Voronezh OblastSingle source · unverifiedRU02 Nov 2026·Armed conflictNew

Drones shot down over Samara Oblast, governor says

Samara OblastAuto-compiledRU01 Nov 2026·Armed conflictNew

Residential damage reported after drone attack in Rostov region

Rostov regionSingle source · unverifiedRU01 Nov 2026·Armed conflictNew

Fire reported after drone attack in Kstovo

KstovoAuto-compiledRU31 Oct 2026·Airport disruptionNew

Fire reported after drone attack in Sheremetyevo International Airport

Sheremetyevo International AirportSingle source · unverifiedRU31 Oct 2026·Armed conflict

Drones shot down over Rostov region, reports say

Rostov regionSingle source · unverifiedRU31 Oct 2026·Armed conflict

Drone report in Ufa, Russia

UfaSingle source · unverifiedRUduring the reporting window 29 Oct 2026–30 Oct 2026·Armed conflictNew

Drone report in Bryansk Oblast, Russia

Bryansk OblastSingle source · unverifiedRU30 Oct 2026·Armed conflictNew

Drone report in Starodub, Russia

StarodubSingle source · unverifiedRU30 Oct 2026·Armed conflict

Residential building damaged in reported drone attack in Bryansk Oblast

Bryansk OblastSingle source · unverifiedRU30 Oct 2026·Armed conflict

Drones shot down over Smolensk Oblast, governor says

Smolensk OblastSingle source · unverifiedRU30 Oct 2026·Armed conflictNew

Drone report in Penza, Russia

PenzaSingle source · unverifiedRU30 Oct 2026·Armed conflict

Fire reported after drone attack in Novokuybyshevsk

NovokuybyshevskAuto-compiledRU30 Oct 2026·Armed conflict

Drones shot down over Tula Oblast, reports say

Tula OblastSingle source · unverifiedRU30 Oct 2026·Armed conflict

Drones shot down over Moscow, reports say

MoscowAuto-compiledRU29 Oct 2026·Armed conflict

Drones shot down over Perm Krai, reports say

Perm KraiSingle source · unverifiedRU29 Oct 2026·Armed conflictNew

Drone wave reported in Russia

RussiaSingle source · unverifiedRUbetween the evening of 28 Oct 2026 and the morning of 29 Oct 2026·Armed conflict

Drone report in Bashkortostan Republic, Russia

Bashkortostan RepublicSingle source · unverifiedRU29 Oct 2026·Armed conflict

Flight disruption after drone alert in Orenburg

OrenburgSingle source · unverifiedRUbetween the evening of 28 Oct 2026 and the morning of 29 Oct 2026·Armed conflictNew

Drone report in Tula Oblast, Russia

Tula OblastSingle source · unverifiedRU29 Oct 2026·Armed conflict

Drone report in Penza Oblast, Russia

Penza OblastSingle source · unverifiedRU28 Oct 2026·Armed conflict

Flight disruption after drone alert in Moscow region

Moscow regionSingle source · unverifiedRU28 Oct 2026·Armed conflict

1 person injured in reported drone attack in Kursk Oblast

Kursk OblastSingle source · unverifiedRU28 Oct 2026·Armed conflict

Explosions reported during drone attack on Belgorod

BelgorodSingle source · unverifiedRU28 Oct 2026·Armed conflict

Fire reported after drone attack in Kursk

KurskSingle source · unverifiedRU28 Oct 2026·Armed conflict

Drones shot down over Voronezh Oblast, governor says

Voronezh OblastSingle source · unverifiedRU28 Oct 2026·Armed conflict

Drone crash reported in Lipetsk Oblast

Lipetsk OblastSingle source · unverifiedRU28 Oct 2026·Armed conflict

Residential building damaged in reported drone attack in Novomoskovsk

NovomoskovskSingle source · unverified

Showing the newest 30 of 395 dossiers. Open the full archive

Global drone incident observatory

What happened.What we actually know.

Drone incidents worldwide, each traced to its original sources. We keep what was reported apart from what is confirmed, and show how the story changed.

395dossiers
46countries
19with drone presence confirmed
Curated dossiers and automatic reports · no live detection
Curated dossiers updated
Automatic reports updated
Dossier update dates, not incident dates. Automatic reports are not editorial approval.

Recorded two-source editorial review:

Editorial country/category selection; not a live or legal safety boundary.
Drone wave reported in Russia≈ RussiaDrones shot down over Voronezh Oblast, governor says≈ Voronezh OblastDrones shot down over Samara Oblast, governor says≈ Samara OblastResidential damage reported after drone attack in Rostov region≈ Rostov regionDrones shot down over Rostov region, reports say≈ Rostov regionDrone report in Bryansk Oblast, Russia≈ Bryansk OblastResidential building damaged in reported drone attack in Bryansk Oblast≈ Bryansk OblastDrones shot down over Smolensk Oblast, governor says≈ Smolensk OblastDrones shot down over Tula Oblast, reports say≈ Tula OblastDrones shot down over Perm Krai, reports say≈ Perm KraiDrone report in Bashkortostan Republic, Russia≈ Bashkortostan RepublicDrone report in Tula Oblast, Russia≈ Tula OblastDrone report in Penza Oblast, Russia≈ Penza OblastFlight disruption after drone alert in Moscow region≈ Moscow region1 person injured in reported drone attack in Kursk Oblast≈ Kursk OblastDrones shot down over Voronezh Oblast, governor says≈ Voronezh OblastDrone crash reported in Lipetsk Oblast≈ Lipetsk OblastDrones shot down over Moscow, reports say≈ MoscowFire reported after drone attack in Kstovo≈ KstovoFire reported after drone attack in Sheremetyevo International Airport≈ Sheremetyevo International AirportDrone report in Ufa, Russia≈ UfaDrone report in Starodub, Russia≈ StarodubDrone report in Penza, Russia≈ PenzaFire reported after drone attack in Novokuybyshevsk≈ NovokuybyshevskDrones shot down over Moscow, reports say≈ MoscowFlight disruption after drone alert in Orenburg≈ OrenburgExplosions reported during drone attack on Belgorod≈ BelgorodFire reported after drone attack in Kursk≈ KurskResidential building damaged in reported drone attack in Novomoskovsk≈ NovomoskovskResidential damage reported after drone attack in Yaroslavl≈ Yaroslavl
Shape: dossier category. Colour and fill: drone evidence. White outer ring: confirmed impact; this does not confirm a drone or an operator.ConfirmedReportedInconclusiveDebunkedDashed: location not yet known (city, region, sea or country)Natural Earth · approximate locations
Shape: dossier category. Colour and fill: drone evidence. White outer ring: confirmed impact; this does not confirm a drone or an operator.
Shape: dossier category. Colour and fill: drone evidence. White outer ring: confirmed impact; this does not confirm a drone or an operator.
  • Airport disruption
  • Maritime attack
  • Critical infrastructure
  • Military site
  • Armed conflict
  • Public safety
  • Reported sightings

Event age: <48 h / 48 h–14 days / >14 days. Date-only reports near a boundary and statement dates stay unshaded. Colours still show evidence status.

Latest editor-reviewed dossiers

Full archive ↓

Newer automatic reports (unverified) are in the strip above and in the archive.

SD30 Oct 2026Drone attack and blackout reported in ShendiSD26 Oct 2026Drone attacks reported in Gedaref State, Sudan; electricity supply disruptedRU26 Oct 2026Drone attack on Voronezh, Russia: governor reports more than 70 drones downed over the cityRU22 Oct 2026Drones downed over Kaluga Oblast, Russia, governor says

How to read a dossier

Every incident is judged on three separate questions. An airport can be confirmed closed while it is still unclear whether a drone was involved at all.

1

Was there a drone?

Drone presence: reported by a source, confirmed by explicit evidence, inconclusive after investigation, or debunked.

ConfirmedReportedInconclusiveDebunked
2

What was the impact?

Closures, diversions, damage or injuries, with their own evidence state. “Not established” means no source reports an impact.

ConfirmedReportedNot established
3

Who is responsible?

Attribution is never inferred. A party’s claim, a charge and a court finding are shown as different things.

Not establishedClaimedChargedConvicted