Dutch rail (OVapi) train delays, Wednesday 14 October 2026

Delays recorded on this day, in Netherlands local time. Below: how it went, then the whole day as one file to download.

How late the trains were

98% of stops were reached less than 5 minutes late, and half of them within 0 minutes of the timetable.

Trains
3,203
5 min late or more
2% of stops
15 min late or more
0% of stops
Median delay
0 min
Cancelled trains
553 34 announced over a day ahead, 519 later

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 24,758 stops that had one, as the operator sent it. Cancelled trains (marked cancelled, or with every stop skipped), skipped stops and values over an hour early or twelve hours late are left out. 100% of the stops of the trains that ran (skipped stops aside) had a delay.

Fewer trains than usual: the archive saw 2,958 of the 6,346 trains the timetable planned (47%, against 99% on a usual day). The feed stopped or repeated old data for part of the day.

Not counted in the trains planned: 14 more trains the timetable lists on lines the live feed has not carried in the week before (Miljoenenlijn).

Most delayed trains

LineLeft its first stopWhere it was latestDelay
ICE Amsterdam Centraal <-> Hannover Hbf ICE24015:46Berlin-Spandau50 min
Eurocity Direct Brussel-Zuid <-> Lelystad Centrum ECD950020:49Amsterdam Zuid43.8 min
Nightjet Amsterdam Centraal <-> Zürich HB NJ40021:01Basel SBB41 min
European Sleeper Brussel-Zuid <-> Praha hl.n. ES40006:23Deventer36 min
Eurostar Amsterdam Centraal <-> London St. Pancras Int. EST910020:04Amsterdam Centraal33.6 min

Download

Read this day from code

This day’s table of final delays has a fixed address. Read it from DuckDB, Polars or curl, with one of your API tokens in place of YOUR_TOKEN:

https://data.train-archive.eu/daily/provider=nl-ovapi/service=TripUpdate/date=2026-10-14.parquet?token=YOUR_TOKEN

Examples for this day Try it in your browser

A few rows of the file

12 different trains, each at one stop. The CSV has more columns, listed below.

Stop stop_nameLine routeArrival predicted_arrivalDelay (min) arrival_delay_minStatus trip_status
Utrecht CentraalIntercity Utrecht Centraal <-> Rotterdam Centraal IC140005:480scheduled
Lelystad CentrumSprinter Lelystad Centrum <-> Leeuwarden SPR900008:070scheduled
EnschedeStoptrein RB51 Enschede <-> Dortmund Hbf ST2020008:270scheduled
LeeuwardenIntercity Schiphol Airport <-> Leeuwarden IC80010:440scheduled
Den Haag CentraalIntercity Den Haag Centraal <-> Enschede IC170012:350scheduled
Utrecht CentraalSprinter Bodegraven <-> Utrecht Centraal SPR890014:010scheduled
Zandvoort aan ZeeSprinter Amsterdam Centraal <-> Zandvoort aan Zee SPR540015:390scheduled
Zandvoort aan ZeeSprinter Amsterdam Centraal <-> Zandvoort aan Zee SPR540017:390scheduled
Amsterdam CentraalIntercity Amsterdam Centraal <-> Den Haag Centraal IC210020:400scheduled
NijmegenIntercity Den Helder <-> Nijmegen IC300000:470scheduled
NijmegenIntercity Den Helder <-> Nijmegen IC300001:500scheduled
[Den Haag HS] Achterzijde station, Waldorpstraat04:160scheduled

What the columns mean

service_date
The day the train was scheduled to run.
route
The line, as the operator names it (for example IC 3 or S2).
trip_id
The operator’s code for this train run. The same train on another day has another code.
trip_start_time
When the train was scheduled to leave its first station.
stop_sequence, stop_id, stop_name
Which stop along the route: its position, code and name.
arrival_delay_min, departure_delay_min
How late the train was at that stop, in minutes. Negative means early. Empty when the operator gave a time but no delay.
predicted_arrival, predicted_departure
The time the operator last announced for that stop, in local time.
observed_at
When that last announcement was seen. After the train has passed, it is what happened.
trip_status
scheduled, cancelled or added (a train that was not in the timetable).
stop_status
skipped when the train did not stop there; empty otherwise.
route_id
The route’s code in the timetable, to join with it.