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

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

Trains
6,691
5 min late or more
3% of stops
15 min late or more
1% of stops
Median delay
0.2 min
Cancelled trains
44 3 announced over a day ahead, 41 later

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 54,716 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 5,114 of the 5,118 trains the timetable planned for this day.

Most delayed trains

LineLeft its first stopWhere it was latestDelay
ICE Amsterdam Centraal <-> München Hbf ICE20014:20Utrecht Centraal72.2 min
Sprinter Uitgeest <-> Rotterdam Centraal SPR400010:33Heerhugowaard63 min
Intercity Enkhuizen <-> Maastricht IC290009:39Schiphol Airport42 min
Eurostar Paris-Nord <-> Amsterdam Centraal EST930018:23Rotterdam Centraal35.8 min
Stoptrein RE19 Arnhem Centraal <-> Düsseldorf Hbf ST2000010:26Zevenaar34.5 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-03.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
Utrecht CentraalIntercity Utrecht Centraal <-> Rotterdam Centraal IC140005:490.6scheduled
ApeldoornSneltrein RE30 Apeldoorn <-> Winterswijk S3040008:080scheduled
[Amsterdam Centraal] Metrostation Amsterdam Centraal08:540scheduled
Rotterdam CentraalIntercity Rotterdam Centraal <-> Utrecht Centraal IC280010:411.2scheduled
VeendamStoptrein RS5 Veendam <-> Delfzijl ST3780012:270scheduled
Lelystad CentrumSprinter Lelystad Centrum <-> Leeuwarden SPR900014:070scheduled
Amsterdam SloterdijkIntercity Amsterdam Centraal <-> Den Haag Centraal IC210014:384.8scheduled
[Amsterdam Amstel] Metrostation Amsterdam Amstel15:080scheduled
[Kapelle-Biezelinge] Voorzijde station, Stationsstraat16:250scheduled
Den Haag CentraalIntercity Amsterdam Centraal <-> Den Haag Centraal IC210018:130scheduled
Den Haag CentraalIntercity Den Haag Centraal <-> Enschede IC170021:050scheduled
ZwolleSprinter RS23 Zwolle <-> Enschede SPR790021:090scheduled
[Amsterdam Centraal] Metrostation Amsterdam Centraal21:590scheduled
[Amsterdam Centraal] Metrostation Amsterdam Centraal23:110scheduled
Amersfoort CentraalIntercity Alkmaar <-> Amsterdam Centraal IC2140003:330scheduled

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.