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

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

Trains
6,402
5 min late or more
6% of stops
15 min late or more
1% of stops
Median delay
0.5 min
Cancelled trains
129 8 announced over a day ahead, 121 later

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 59,820 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, as are 3 placeholder values the feed sent instead of a time (a train “here, now” hours late, or one time repeated at every stop). 100% of the stops of the trains that ran (skipped stops aside) had a delay.

The archive saw 6,382 of the 6,461 trains the timetable planned for this day.

Most delayed trains

LineLeft its first stopWhere it was latestDelay
ICE Amsterdam Centraal <-> Frankfurt (M) Hbf ICE10015:34Utrecht Centraal111 min
ICE Amsterdam Centraal <-> Frankfurt (M) Hbf ICE10019:34Amsterdam Centraal87 min
ICE Amsterdam Centraal <-> München Hbf ICE20005:34Utrecht Centraal85.7 min
European Sleeper Brussel-Zuid <-> Praha hl.n. ES40006:07Rotterdam Centraal76.6 min
ICE Amsterdam Centraal <-> Frankfurt (M) Hbf ICE10012:07Arnhem Centraal75.2 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-30.parquet?token=YOUR_TOKEN

Examples for this day Try it in your browser

A few rows of the file

14 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
Den Haag Centraal00:451added
ZwolleSprinter RS23 Zwolle <-> Enschede SPR790007:423.9scheduled
MeppelSprinter Lelystad Centrum <-> Leeuwarden SPR900008:503.1scheduled
Schiphol AirportIntercity direct Breda <-> Amersfoort Schothorst ICD180011:500.7scheduled
VenloSprinter Horst-Sevenum <-> Venlo14:280scheduled
DordrechtSprinter Den Haag Centraal <-> Dordrecht SPR500018:350scheduled
Utrecht CentraalIntercity Rotterdam Centraal <-> Utrecht Centraal IC280023:025.9scheduled
Amsterdam CentraalIntercity Amsterdam Centraal <-> Almere Centrum IC260016:520scheduled
Utrecht MaliebaanSprinter Spoorwegmuseum Utrecht Centraal <-> Utrecht Maliebaan09:490scheduled
WinterswijkStoptrein RS31 Zutphen <-> Winterswijk ST3080015:400scheduled
Arnhem CentraalStoptrein RS32 Arnhem Centraal <-> Winterswijk ST3090018:251.6scheduled
VeendamStoptrein RS5 Veendam <-> Delfzijl ST3780012:270scheduled
VenrayStoptrein RS11 Nijmegen <-> Venray ST3230012:580scheduled
Amsterdam CentraalSprinter Amsterdam Centraal <-> Hoofddorp SPR820015:390scheduled

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.