DOSSIER · NLPermanent page

Critical infrastructure

Unidentified drones reported over Eemshaven

Eemshaven, Netherlands15 Oct 2026 · statement datecountry reference point on the map; exact location not yet known

Reporting on 15 October 2026 describes unidentified drones over Eemshaven on the preceding weekend and Tuesday evening.

Drone presenceReported[1]

ImpactNot established

AttributionNot established

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

Curated dossier · sources checked line by line on 29 Oct 2026 · Dossier updated 29 Oct 2026

Source passage

Groningen Seaports via Eemskrant · “onbekende drones gezien” eemskrant.nl

Facts at a glance

Drone type: No named drone type is recorded in this dossier.
Who reported what: RTV Noord: Assessment of drone involvement
eemskrant.nl: Assessment of drone involvement
Source families: 2 source families are recorded; republication is not independent confirmation
No structured detail recorded: Hit / damaged · Fell near · Intercepted (claimed) · Human consequences · Effects

Country reference only
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.

<iframe src="https://droneincidents.com/embed/dossier/eemshaven-unidentified-drone-reports-2026-10-15/en/" title="Embed this dossier" width="100%" height="320" loading="lazy" referrerpolicy="no-referrer"></iframe>

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 establishing when the event happened, rather than when a statement or article was published.
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.

Claims and evidence

2 sources · 1 original statement

Sources that repeat the same original statement count once: a number of articles is not a number of independent confirmations.

Claim	Original source	Assessment
Drone Seaports reports repeated drone sightings. Source passage [2] “onbekende drones gezien” Passage checked word for word against the source on 29 Oct 2026.	Groningen Seaports via Eemskrant via Eemskrant	Supports the report Official accounts relayed by the cited publishers; no independent technical verification.

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.

Groningen Seaports via Eemskrant
- Eemskrant: Seaports and security reports [2] · Relayed statement
Unknown dependency
- RTV Noord: initial port sightings [1]

Show source graph

Left: publishers; right: recorded original statement. Converging lines show shared origin, not publication order. Dashed nodes have unknown dependency.

Drones involved

The cited sources do not name the type of drone.

What we know

Seaports says police also saw drones. No damage or operational disruption established.

RTV Noord and Eemskrant report the Seaports account. Their shared official origin is explicit; the reports do not independently identify the aircraft.

What remains unknown

Counts, operators and precise flight dates remain uncertain. The date is the report date. These reports are separate from the 20 October arrest.

Operator attribution: Not established. No hostile operator or motive established.

How the story changed

15 Oct 2026
Reporting on 15 October 2026 describes unidentified drones over Eemshaven on the preceding weekend and Tuesday evening. [1]

Original sources (2)

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

1RTV Noord: initial port sightings15 Oct 2026 · source family: rtvnoord

Fetch unavailable: 2026-10-29 09:35:02 UTC

2Eemskrant: Seaports and security reports15 Oct 2026 · source family: eemskrant

First observed: 2026-10-29 08:28:38 UTC

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

Editorial changes

Revision 1 · 29 Oct 2026Curated dossier created after checking the cited sources line by line.

Story timeline

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

Revision 1 · Current dossier · 29 Oct 2026
Drone presence: Reported · Impact: Not established · Attribution: Not established

Current dossier

Cite this dossier

Permanent page · Revision 1

Chicago

DroneLedger. “Unidentified drones reported over Eemshaven.” Dossier eemshaven-unidentified-drone-reports-2026-10-15, revision 1, updated 29 Oct 2026. https://droneincidents.com/incident/eemshaven-unidentified-drone-reports-2026-10-15/v1/

APA

DroneLedger. (29 Oct 2026). Unidentified drones reported over Eemshaven (Dossier eemshaven-unidentified-drone-reports-2026-10-15, revision 1). https://droneincidents.com/incident/eemshaven-unidentified-drone-reports-2026-10-15/v1/

Dataset DOI: 10.5281/zenodo.23345422

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

Press graphics

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

Download dossier JSON

Curated dossier · sources checked line by line on 29 Oct 2026
Dossier updated 29 Oct 2026

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.

NL15 Oct 2026·Critical infrastructureNew

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.

331dossiers

46countries

19with drone presence confirmed

Curated dossiers and automatic reports · no live detection

Curated dossiers updated: 29 Oct 2026
Automatic reports updated: 29 Oct 2026

Dossier update dates, not incident dates. Automatic reports are not editorial approval.

Recorded two-source editorial review: 29 Oct 2026

Editorial country/category selection; not a live or legal safety boundary.

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.

SD26 Oct 2026Drone attacks reported in Gedaref State, Sudan; electricity supply disrupted RU26 Oct 2026Drone attack on Voronezh, Russia: governor reports more than 70 drones downed over the city RU22 Oct 2026Drones downed over Kaluga Oblast, Russia, governor says FR21 Oct 2026Unauthorised drone flights reported during French Navy exercises near Toulon, France

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.

Was there a drone?

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

ConfirmedReportedInconclusiveDebunked

What was the impact?

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

ConfirmedReportedNot established

Who is responsible?

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

Not establishedClaimedChargedConvicted

Incident archive

No matching dossiers