Dutch rail (OVapi) train delays, Thursday 19 November 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

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

Trains
7,590
5 min late or more
9% of stops
15 min late or more
2% of stops
Median delay
0.7 min
Cancelled trains
199

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

Most delayed trains

LineLeft its first stopWhere it was latestDelay
Nightjet Amsterdam Centraal <-> Innsbruck Hbf NJ40027:11Arnhem Centraal176.4 min
Nightjet Amsterdam Centraal <-> Innsbruck Hbf NJ40021:01Bonn Hbf127 min
Nightjet Amsterdam Centraal <-> Innsbruck Hbf NJ40026:01Arnhem Centraal105.9 min
RE13 Venlo <-> Hamm (Westf.)15:05Bönen89 min
RE13 Venlo <-> Hamm (Westf.)13:25Neuss Hbf79 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-11-19.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
Alkmaar02:011.2added
BredaIntercity direct Breda <-> Amersfoort Schothorst ICD180008:160scheduled
GroningenSprinter Assen <-> Groningen SPR620008:080.6scheduled
Amsterdam CentraalSprinter Amsterdam Centraal <-> Haarlem SPR540009:190scheduled
LeeuwardenRS3 Leeuwarden <-> Stavoren11:080scheduled
Utrecht CentraalIntercity Rotterdam Centraal <-> Utrecht Centraal IC200012:120scheduled
DordrechtStoptrein Dordrecht <-> Gorinchem ST710013:200scheduled
Alphen a/d RijnSprinter Alphen a/d Rijn <-> Gouda SPR870014:350.5scheduled
ZwolleRE20 Zwolle <-> Emmen15:530.2scheduled
Nieuw AmsterdamStoptrein Nieuw Amsterdam <-> Emmen ST3640016:480scheduled
Hardenberg18:510scheduled
HoofddorpSprinter Amsterdam Centraal <-> Hoofddorp SPR830019:351.2scheduled
HeerlenRS15 Sittard <-> Heerlen21:092scheduled
WeertSprinter Tilburg Universiteit <-> Weert SPR640023:422.5scheduled
Amsterdam CentraalNightjet Amsterdam Centraal <-> Innsbruck Hbf NJ40011:46167.2scheduled

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.