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

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

Trains
4,651
5 min late or more
7% of stops
15 min late or more
1% of stops
Median delay
0.6 min
Cancelled trains
95

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 41,773 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,716 of the 4,857 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
ICE Amsterdam Centraal <-> München Hbf ICE200Amsterdam Centraal120.5 min
ICE Amsterdam Centraal <-> Frankfurt (M) Hbf ICE100Frankfurt Flughafen Fernb99.3 min
ICE Amsterdam Centraal <-> Berlin Südkreuz ICE140Berlin-Spandau95 min
ICE Amsterdam Centraal <-> Berlin Südkreuz ICE240Arnhem Centraal94.2 min
ICE Amsterdam Centraal <-> Frankfurt (M) Hbf ICE100Arnhem Centraal92 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-25.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
Rotterdam Centraal02:570added
GroningenStoptrein RS7 Veendam <-> Eemshaven ST3750022:130scheduled
SittardStoptrein RS15 Sittard <-> Heerlen ST3250008:420.6scheduled
Almere CentrumIntercity direct Rotterdam Centraal <-> Lelystad Centrum ICD240016:492.7scheduled
KampenSprinter RS22 Zwolle <-> Kampen SPR850007:280scheduled
HoofddorpSprinter Hoorn Kersenboogerd <-> Hoofddorp SPR410008:470.3scheduled
Maastricht RandwyckStoptrein RS12 Roermond <-> Maastricht Randwyck ST3240015:572.1scheduled
ZwolleSprinter Lelystad Centrum <-> Leeuwarden SPR900020:540scheduled
HoofddorpSprinter Amsterdam Centraal <-> Hoofddorp SPR810007:570scheduled
Utrecht CentraalIntercity Rotterdam Centraal <-> Utrecht Centraal IC200016:420.1scheduled
UitgeestSprinter Uitgeest <-> Rotterdam Centraal SPR400008:420scheduled
Rotterdam CentraalEuroCity Brussel-Zuid <-> Rotterdam Centraal ECC920011:0112.1scheduled
Den Haag CentraalIntercity Den Haag Centraal <-> Groningen IC50018:510scheduled
Amsterdam CentraalGoVolta Amsterdam Centraal <-> Berlin-Spandau GV30001:057.4scheduled

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.