All German rail (DELFI via gtfs.de) train delays, Monday 2 November 2026

Delays recorded on this day, in Germany local time. Below: how it went, then the whole day as one file to download.

gtfs.de's realtime feed (CC BY 4.0) carries DB long-distance trains only where their lines cross the VRR and NVBW areas. From 23 October 2026, the DB Fernverkehr trains it lacks (international legs, SyltShuttle, EC/ECE, some IC lines) are added from Deutsche Bahn's Timetables API (DB API Marketplace, CC BY 4.0), with delays at German stations only.

How late the trains were

80% of stops were reached less than 5 minutes late, and half of them within 1 minute of the timetable.

Trains
39,094
5 min late or more
20% of stops
15 min late or more
4% of stops
Median delay
1 min
Cancelled trains
598

Recorded from 00:01 to 23:58. The figures use the last delay announced at each of the 541,074 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 381 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 39,094 of the 41,763 trains the timetable planned for this day.

Not counted in the trains planned: 1,734 more trains the timetable lists on lines the live feed has not carried in the week before (ZVON Oberlausitz-Niederschlesien, SBB, ÖBB, Ostdeutsche Eisenbahn GmbH, CFL, SNCB and 23 more).

Most delayed trains

LineLeft its first stopWhere it was latestDelay
RE3Mainz Hbf212 min
RE3Mainz Hbf198 min
RS3Hude189 min
RB33Bad Kreuznach186 min
RB89Bopfingen169 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=de-gtfsde/service=TripUpdate/date=2026-11-02.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
FlehingenS413:469.5scheduled
BöblingenS6007:026scheduled
OffenburgRB2620:564scheduled
AumühleS710:280scheduled
Neuenburg(Baden)RB2708:026scheduled
S Bernau BhfS206:14-0.4scheduled
BambergRE3521:153scheduled
Wedel(Holst)S115:012scheduled
Ulm HbfRE909:510scheduled
Freiburg, HauptbahnhofS1018:180scheduled
S Blankenfelde (TF) BhfS217:386.1scheduled
KauferingRB6907:597scheduled
Mönchengladbach HbfRE1321:110scheduled
Wuppertal-OberbarmenRB4801:460scheduled
S+U Warschauer Str.S7504:38-0.1scheduled

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.