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

Frankfurt (M) Hbf 11:34 → Amsterdam Centraal 15:29 Daily 3 h 55 min · 8 stops NS Int

✓ Today’s run finished

Today, last fix heading to Utrecht Centraal at 16:11 No data

  1. Frankfurt (M) Hbf11:34
  2. Frankfurt Flughafen Fernb11:45
  3. Siegburg/Bonn12:27
  4. Düsseldorf Hbf13:11
  5. Arnhem Centraal14:26
  6. Utrecht Centraal14:59
  7. Amsterdam Centraal15:29

Next service: tomorrow 11:34 from Frankfurt (M) Hbf · Wed 21 Oct

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

  • Sun 18 Oct Max en route +37 min · last fix heading to Utrecht Centraal +37 min
  • Mon 12 Oct Max en route +33 min · last fix heading to Utrecht Centraal +31 min
  • Fri 9 Oct Max en route +29 min · last fix heading to Utrecht Centraal +28 min
  • Sun 11 Oct Max en route +25 min · last fix heading to Utrecht Centraal +25 min
  • Thu 8 Oct Max en route +20 min · last fix heading to Utrecht Centraal +19 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 27% · 3
  • 3–10 min 18% · 2
  • 10–30 min 36% · 4
  • 30+ min 18% · 2

On-time by weekday

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

Stops and timetable

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

StopSched.
11:34
11:45 / 11:46
12:27 / 12:29
12:43 / 12:49
13:11 / 13:13
14:26 / 14:28
14:59 / 15:02
15:29

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
Tue 20 OctUtrecht Centraal 16:11No data—
Mon 19 OctUtrecht Centraal 15:39Partial coverage0 min—
Sun 18 OctUtrecht Centraal 15:53+37 min+37 min
Sat 17 OctArnhem Centraal 16:22No data—
Fri 16 OctUtrecht Centraal 16:130 min—
Thu 15 OctUtrecht Centraal 15:53No data—
Wed 14 OctUtrecht Centraal 15:40No data—
Tue 13 OctUtrecht Centraal 15:59No data—
Mon 12 OctUtrecht Centraal 15:50Partial coverage+31 min+33 min
Sun 11 OctUtrecht Centraal 15:40+25 min+25 min
Sat 10 OctUtrecht Centraal 15:24+6 min+8 min
Fri 9 OctUtrecht Centraal 15:47+28 min+29 min
Thu 8 OctUtrecht Centraal 15:38+19 min+20 min
Wed 7 OctUtrecht Centraal 15:31+11 min+14 min
Tue 6 OctUtrecht Centraal 15:27+8 min+10 min
Mon 5 OctUtrecht Centraal 15:21+1 min+4 min
Sun 4 OctUtrecht Centraal 15:25No data—
Sat 3 OctArnhem Centraal 14:51No data—
Fri 2 OctUtrecht Centraal 15:43No data—
Thu 1 OctUtrecht Centraal 15:51No data—
Wed 30 SeptUtrecht Centraal 15:35No data—
Tue 29 SeptUtrecht Centraal 15:20No data—
Mon 28 SeptUtrecht Centraal 15:22No data—
Sun 27 SeptUtrecht Centraal 15:16No data—
Sat 26 SeptUtrecht Centraal 16:24No data—
Fri 25 SeptUtrecht Centraal 15:32No data—
Thu 24 SeptArnhem Centraal 16:29No data—
Wed 23 SeptUtrecht Centraal 15:43No data—
Tue 22 SeptUtrecht Centraal 15:38No data—
Mon 21 SeptUtrecht Centraal 15:32No data—