SevereActive

Rail disruption activity in Netherlands

🇳🇱 Netherlands

Onset: 2026-06-15 · First detected: 2026-06-15T22:23:23.789491+00:00 · Last observed: 2026-10-10T00:00:57.359673+00:00

Generated at: 2026-10-10T00:00:57.359673+00:00 · The radar runs every 6 hours; data may lag by up to 6 hours.

Plain-language brief

What happened, who is affected, what similar past episodes looked like and what to do — every number links to its source.

What happened

ObservedOn 2026-06-15, our automated monitoring flagged a rail disruption in Netherlands — rated severe — the highest of our three alert levels.[NS Open Data Portal Netherlands]
ObservedThe reading behind this alert: max impact at 5 (the full technical detail is in the sections below).[NS Open Data Portal Netherlands]

Who is affected

ObservedHotels, travel managers, OTAs and tour operators with guests in Netherlands during the event window are the most directly affected, together with travellers holding bookings there.[NS Open Data Portal Netherlands]

What similar past episodes looked like

Historical associationIn similar past high-disruption months, overnight stays in Netherlands averaged 44.6% below normal calm-month levels — a historical association from our published research panel, not a prediction.[estimates.historical_correlation]
Historical associationLooking at the 3 most similar months in our 2014-2026 research panel, overnight stays one month later differed from a year earlier by a median of -0.4% — again a historical association, not a prediction of this event.[estimates.analogues]

What to do now

RecommendationFor now, keep an eye on the situation in Netherlands; no change to bookings is needed yet.[detection.observed]
RecommendationContact guests and travellers with upcoming stays in Netherlands before they contact you, and point them to the official sources linked in this report.[detection.observed]

Impact

significant_disruptions	2
max_impact	5
by_type	{"CALAMITY":1,"MAINTENANCE":1}
operators	["NS"]

Historical monthly context — not current conditionsAs of: 2026-10 · Disruption index: 0 · 0 months older than this event

How this was detected

Rule: ns_impact_disruptions

Method: deterministic-rule

Thresholds

impact_warning	3
impact_severe	4
calamity_type	CALAMITY
elevate_types	["CALAMITY"]
baseline_metric	significant_disruptions
abs_min_disruptions	1
z_min	2
z_floor	3

Observed

significant_disruptions	2
max_impact	5
by_type	{"CALAMITY":1,"MAINTENANCE":1}
operators	["NS"]

Baseline

n_points	0
window_hours	0
mean	—
std	—

Insufficient baseline — absolute threshold only.

Sources

NS Open Data Portal Netherlands snapshotcollected: 2026-10-10T00:00:57.359673+00:00

Corroborating evidence

Independent live sources scanned for disruption-significant entries about this country. Only strict, disclosed rules count — routine entries are never counted.

No corroborating entries found in the sources scanned.

Sources scanned: auswaertiges-amt-api-de, emsc-seismic, france-diplomatie-travel, gdacs-live, mae-ro-travel, meteoalarm-eumetnet, minbuza-nl-travel, uk-fcdo-advisories, us-state-advisories, viaggia-sicuri-it

Estimates

Estimates are labeled model outputs derived from published historical artifacts — they are context, not forecasts.

Model output — historical correlation estimatehistorical-correlation

r_nights	-0.14
r_arrivals	-0.36
best_lag_months	6
best_lag_r	-0.22
baseline_deviation_pct	-44.61
n_months	139

Caveats:

correlation is association, not causation
baseline_deviation_pct is the observed average nights deviation during historical high-disruption months (index > 50) vs calm months
coefficients are dominated by the 2020-2021 pandemic period and may overstate the impact of smaller disruptions
computed on monthly national aggregates; sub-national and short-lived events are diluted

Observed history — analogue episodes, not a predictionanalogue-episodesindex_equiv = 60

Episode	score	index	h0	h1	h2	h3
🇫🇷 France · 2026-07	1.992	93.33	2.97	—	—	—
🇫🇷 France · 2025-07	1.889	87.11	5.56	1.18	1.93	4.24
🇫🇷 France · 2016-07	1.877	81.18	-1.78	-1.98	-1.28	-9.14

median_h1	-0.40
median_h2	0.32
median_h3	-2.45

Caveats:

analogues are historically similar months, not a forecast of this event
similarity is computed on a 10-feature panel embedding (tourism volumes, disruption/stringency indices, seasonality); it ignores event semantics
the index_equiv mapping from severity to disruption-index points is a disclosed modelling assumption, not an observation
observed_nights_yoy_pct mixes the event effect with everything else that happened in those months

Recommendations

Monitor the situation in Netherlands and re-check this report before confirming new bookings.
based on: detection.observed
Proactively inform guests with upcoming stays in Netherlands about possible disruptions.
based on: detection.observed
Enable flexible rebooking for trips to Netherlands departing within {days} days.
based on: detection.observed, estimates.historical_correlation
Shift promoted inventory away from Netherlands toward unaffected destinations until {month}.
based on: detection.observed

For AI agents

Machine-readable JSON for this page:

/data/api/v1/events/ev-rail-disruption-event-nl-20260615-c6d64f.json

Add as an MCP server (from the repo root):

claude mcp add travel-trends -- .venv/bin/python -m etl.mcp_server

API documentation→