Dutch rail (OVapi) train delays, Sunday 11 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

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

Trains
5,566
5 min late or more
4% of stops
15 min late or more
1% of stops
Median delay
0.3 min
Cancelled trains
82 18 announced over a day ahead, 64 later

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 47,975 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.

The archive saw 4,706 of the 4,826 trains the timetable planned for this 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
GoVolta Amsterdam Centraal <-> Berlin-Spandau GV30015:19Hengelo125.8 min
ICE Amsterdam Centraal <-> München Hbf ICE20014:20Arnhem Centraal55.1 min
ICE Amsterdam Centraal <-> Hannover Hbf ICE14010:57Bad Bentheim54 min
Intercity Amsterdam Centraal <-> Deventer IC150022:00Amersfoort Centraal48.2 min
Sprinter Almere Centrum <-> Utrecht Centraal SPR490021:51Hilversum Sportpark47 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-11.parquet?token=YOUR_TOKEN

Examples for this day Try it in your browser

A few rows of the file

15 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
Alkmaar01:011.8added
EnschedeSprinter RS23 Zwolle <-> Enschede SPR790008:270scheduled
PuursStoptrein Puurs <-> Roosendaal ST255010:530scheduled
Amsterdam CentraalIntercity Amsterdam Centraal <-> Vlissingen IC220010:550.4scheduled
Hoofddorp12:520added
WinterswijkStoptrein RS32 Arnhem Centraal <-> Winterswijk ST3090014:100scheduled
[Haarlem] Voorplein station OV (uitstaphalte)15:180scheduled
Venlo16:120added
Utrecht CentraalSprinter Leiden Centraal <-> Utrecht Centraal SPR570017:513.9scheduled
Utrecht CentraalIntercity Rotterdam Centraal <-> Utrecht Centraal IC280018:270scheduled
ZwolleSprinter Zwolle <-> Groningen SPR610020:070scheduled
's-HertogenboschSprinter Den Haag Centraal <-> 's-Hertogenbosch SPR600022:020scheduled
Amsterdam HolendrechtSprinter Breukelen <-> Rhenen SPR730022:210scheduled
Eindhoven CentraalIntercity Enkhuizen <-> Maastricht IC290000:020scheduled
Rotterdam CentraalIntercity Utrecht Centraal <-> Rotterdam Centraal IC140004:570scheduled

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.