All German rail (DELFI via gtfs.de) train delays, Sunday 18 October 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
89% of stops were reached less than 5 minutes late, and half of them within 0.1 minutes of the timetable.
- Trains
- 30,794
- 5 min late or more
- 11% of stops
- 15 min late or more
- 3% of stops
- Median delay
- 0.1 min
- Cancelled trains
- 316
Recorded from 00:00 to 23:58. The figures use the last delay announced at each of the 405,476 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 262 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 30,794 of the 32,923 trains the timetable planned for this day.
Not counted in the trains planned: 1,782 more trains the timetable lists on lines the live feed has not carried in the week before (ZVON Oberlausitz-Niederschlesien, SBB, DB Fernverkehr AG, ÖBB, Ostdeutsche Eisenbahn GmbH, Ceske Drahy and 36 more).
Most delayed trains
| Line | Left its first stop | Where it was latest | Delay |
|---|---|---|---|
| RE8 | Osterburken | 241 min | |
| RE6a | Sigmaringen | 224 min | |
| RE6a | Tübingen Hbf | 216 min | |
| RE3 | Aulendorf | 192 min | |
| S8 | Freudenstadt Hbf | 162.4 min |
Download
Get the CSV Accounts are free: you sign in with a code sent to your email, no password. You come back here after signing in.
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-10-18.parquet?token=YOUR_TOKEN
A few rows of the file
15 different trains, each at one stop. The CSV has more columns, listed below.
Stop stop_name | Line route | Arrival predicted_arrival | Delay (min) arrival_delay_min | Status trip_status |
|---|---|---|---|---|
| Leipzig Miltitzer Allee | S1 | 23:52 | 0 | scheduled |
| Eilenburg | S9 | 21:22 | 0 | scheduled |
| Duisburg Hbf | S1 | 17:39 | 3 | scheduled |
| Wurzen | S4 | 17:01 | 10 | scheduled |
| Nürnberg Hbf | S3 | 23:11 | 0 | scheduled |
| Coburg | RB18 | 23:30 | 0 | scheduled |
| Bruchsal | S33 | 05:01 | 1 | scheduled |
| S+U Berlin Hauptbahnhof | S15 | 10:29 | -0.7 | scheduled |
| Bad Langensalza | RB52 | 21:46 | 3 | scheduled |
| Tullastraße/Alter Schlachthof, Karlsruhe | S7 | 19:51 | 11.9 | scheduled |
| Karlsruhe Hbf | RE6 | 16:57 | 4 | scheduled |
| Stuttgart Hbf | RE5 | 20:26 | 1 | scheduled |
| Hannover Flughafen | S5 | 15:57 | 4 | scheduled |
| Trossingen Bahnhof | RB42a | 21:57 | 2 | scheduled |
| S Teltow Stadt | S26 | 17:01 | -0.9 | scheduled |
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.