Train NS Int 124 Frankfurt (M) Hbf – Amsterdam Centraal

Frankfurt (M) Hbf 13:34 → Amsterdam Centraal 17:50 Daily 4 h 16 min · 8 stops NS Int

✓ Today’s run finished

Today, last fix heading to Utrecht Centraal at 18:09 0 min

  1. Frankfurt (M) Hbf13:34
  2. Frankfurt Flughafen Fernb13:45
  3. Siegburg/Bonn14:27
  4. Düsseldorf Hbf15:11
  5. Arnhem Centraal16:26
  6. Utrecht Centraal17:23
  7. Amsterdam Centraal17:50

Next service: tomorrow 13:34 from Frankfurt (M) Hbf · Sat 24 Oct

Next departure 13:34 tomorrow · Frankfurt (M) Hbf
On-time · 30 days
38%
5/13 runs under 3 min
RT coverage: 12 full · 1 partial · 17 no data
On-time · 90 days
38%
5/13 runs under 3 min
RT coverage: 12 full · 1 partial · 76 no data
Typical delay
+10min
Median at arrival, 90 days
30 days: +10 min
P90
+27min
9 in 10 runs arrive with less than this
30 days: +27 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

  • Mon 12 Oct Max en route +45 min · last fix heading to Utrecht Centraal +45 min
  • Sun 18 Oct Max en route +27 min · last fix heading to Utrecht Centraal +27 min
  • Sun 11 Oct Max en route +27 min · last fix heading to Utrecht Centraal +26 min
  • Sat 10 Oct Max en route +12 min · last fix heading to Utrecht Centraal +12 min
  • Thu 8 Oct Max en route +14 min · last fix heading to Utrecht Centraal +11 min

Distribution · 90 days

13 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 38% · 5
  • 3–10 min 8% · 1
  • 10–30 min 46% · 6
  • 30+ min 8% · 1

On-time by weekday

  • 67% M n=3
  • 0% T n=1
  • 0% W n=1
  • 0% T n=1
  • 67% F n=3
  • 50% S n=2
  • 0% S n=2

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 stops).

StopSched.
13:34
13:45 / 13:48
14:27 / 14:29
14:43 / 14:49
15:11 / 15:13
16:26 / 16:31
17:23 / 17:27
17:50

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.

Recent runs

DateLast stopFinalMax
Fri 23 OctUtrecht Centraal 18:09Partial coverage0 min—
Thu 22 OctUtrecht Centraal 18:12No data—
Wed 21 OctUtrecht Centraal 18:32No data—
Tue 20 OctUtrecht Centraal 17:52No data—
Mon 19 OctUtrecht Centraal 17:440 min—
Sun 18 OctUtrecht Centraal 17:45+27 min+27 min
Sat 17 OctUtrecht Centraal 17:320 min—
Fri 16 OctUtrecht Centraal 18:060 min—
Thu 15 OctUtrecht Centraal 17:36No data—
Wed 14 OctUtrecht Centraal 17:28No data—
Tue 13 OctUtrecht Centraal 17:45No data—
Mon 12 OctUtrecht Centraal 18:09+45 min+45 min
Sun 11 OctUtrecht Centraal 17:42+26 min+27 min
Sat 10 OctUtrecht Centraal 17:30+12 min+12 min
Fri 9 OctUtrecht Centraal 17:27+11 min+11 min
Thu 8 OctUtrecht Centraal 17:32+11 min+14 min
Wed 7 OctUtrecht Centraal 17:29+10 min+11 min
Tue 6 OctUtrecht Centraal 17:23+5 min+5 min
Mon 5 OctUtrecht Centraal 17:20+3 min+5 min
Sun 4 OctUtrecht Centraal 17:16No data—
Sat 3 OctArnhem Centraal 17:01No data—
Fri 2 OctUtrecht Centraal 17:41No data—
Thu 1 OctUtrecht Centraal 17:19No data—
Wed 30 SeptUtrecht Centraal 17:30No data—
Tue 29 SeptUtrecht Centraal 17:20No data—
Mon 28 SeptUtrecht Centraal 17:29No data—
Sun 27 SeptUtrecht Centraal 17:17No data—
Sat 26 SeptUtrecht Centraal 17:44No data—
Fri 25 SeptUtrecht Centraal 17:31No data—
Thu 24 SeptUtrecht Centraal 17:19No data—