Dutch rail (OVapi) train delays, Friday 2 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.4 minutes of the timetable.

Trains
6,439
5 min late or more
4% of stops
15 min late or more
1% of stops
Median delay
0.4 min
Cancelled trains
55

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 61,404 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 6,052 of the 6,289 trains the timetable planned for this day.

Most delayed trains

LineLeft its first stopWhere it was latestDelay
GoVolta Amsterdam Centraal <-> Berlin-Spandau GV30016:15Deventer227.9 min
Sprinter Haarlem <-> Den Haag Centraal SPR420017:17Den Haag Centraal59 min
EuroCity Brussel-Zuid <-> Rotterdam Centraal ECC920015:10Rotterdam Centraal54.9 min
Sprinter Den Haag Centraal <-> Lelystad Centrum SPR430016:25Den Haag Centraal48 min
Intercity Amsterdam Centraal <-> Den Haag Centraal IC210010:20Haarlem40.1 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-02.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
Utrecht CentraalIntercity Utrecht Centraal <-> Rotterdam Centraal IC140005:570.8scheduled
Driebergen-ZeistSprinter Uitgeest <-> Driebergen-Zeist SPR740007:370scheduled
KampenSprinter RS22 Zwolle <-> Kampen SPR850007:560scheduled
Utrecht CentraalSprinter Uitgeest <-> Driebergen-Zeist SPR740010:240scheduled
Utrecht CentraalSprinter Almere Centrum <-> Utrecht Centraal SPR490011:050.1scheduled
Amsterdam CentraalSprinter Amsterdam Centraal <-> Hoofddorp SPR840012:050scheduled
Amersfoort CentraalSprinter RS34 Amersfoort Centraal <-> Ede-Wageningen SPR3130015:000.2scheduled
LeeuwardenIntercity Den Haag Centraal <-> Leeuwarden IC60018:140scheduled
Almere CentrumSprinter Almere Centrum <-> Utrecht Centraal SPR490017:380scheduled
Den Haag CentraalSprinter Den Haag Centraal <-> Dordrecht SPR510019:040.5scheduled
Ede-WageningenSprinter Ede-Wageningen <-> Arnhem Centraal SPR750019:480scheduled
Düsseldorf HbfSneltrein RE13 Venlo <-> Hamm (Westf.) S2000022:100scheduled
Tilburg UniversiteitSprinter Tilburg Universiteit <-> Weert SPR640023:280.9scheduled
[Amsterdam Centraal] Busstation IJ-Zijde, Bushalte M03:550scheduled

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.