Train NS Int 156 Frankfurt (M) Hbf → Amsterdam Centraal
NS Int 156 Frankfurt (M) Hbf–Amsterdam Centraal: final delay under 3 min on 1 of its 7 runs with data in the last 30 days (14%). Median final delay: +26 min. TrainsRadar data as of 22 Nov 2026, 20:32 (GMT+1).
An alert on this phone or computer when the 156 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Monday 16 November +18 min
Last 30 days
Arrival delay at Amsterdam Centraal, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 10 Nov Max en route +99 min · last fix heading to Utrecht Centraal +98 min
- Wed 11 Nov Max en route +75 min · last fix heading to Utrecht Centraal +75 min
- Thu 12 Nov Max en route +58 min · last fix heading to Utrecht Centraal +56 min
- Fri 13 Nov Max en route +30 min · last fix heading to Utrecht Centraal +26 min
- Sat 14 Nov Max en route +25 min · last fix heading to Utrecht Centraal +22 min
Distribution · 90 days
7 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 14% · 1
- 3–10 min 0% · 0
- 10–30 min 43% · 3
- 30+ min 43% · 3
On-time by weekday
- 0% M n=1
- 0% T n=1
- 0% W n=1
- 0% T n=1
- 0% F n=1
- 0% S n=1
- 100% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 7 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 11:34 | +21 min | +72 min | |
| 11:45 / 11:48 | ≈ +21 min | ≈ +79 min | |
| 12:27 / 12:29 | ≈ +22 min | ≈ +81 min | |
| 12:43 / 12:50 | ≈ +22 min | ≈ +81 min | |
| 13:31 / 13:33 | ≈ +23 min | ≈ +83 min | |
| 14:52 / 14:55 | ≈ +24 min | ≈ +86 min | |
| 15:23 / 15:28 | ≈ +25 min | ≈ +88 min | |
| 15:58 | +26 min | +89 min |
Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 16 Nov | Utrecht Centraal 16:05Partial coverage | +18 min | +20 min |
| Sun 15 Nov | Utrecht Centraal 15:48 | +2 min | +6 min |
| Sat 14 Nov | Utrecht Centraal 16:08 | +22 min | +25 min |
| Fri 13 Nov | Utrecht Centraal 16:12 | +26 min | +30 min |
| Thu 12 Nov | Utrecht Centraal 16:42Partial coverage | +56 min | +58 min |
| Wed 11 Nov | Utrecht Centraal 16:59 | +75 min | +75 min |
| Tue 10 Nov | Utrecht Centraal 17:23 | +98 min | +99 min |