Train NS 12480 Amsterdam Zuid – Rotterdam Centraal

Amsterdam Zuid 23:04 → Rotterdam Centraal 23:38 Daily 0 h 34 min · 3 stops NS (Nederlandse Spoorwegen)

Running now · updated 23:14

Heading to Rotterdam Centraal 0 min

Estimated arrival at Rotterdam Centraal 23:38 · 55 km/h

  1. Amsterdam Zuid23:04
  2. Schiphol Airport23:10
  3. Rotterdam Centraal23:38

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 22 runs arrived on time.

On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 21 full · 1 partial · 6 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 partial · 15 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Rotterdam 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

  • Fri 9 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=4
  • 75% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 24 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.

StopSched.Usually 9 days in 10Today
23:04on time on time
23:10 / 23:11≈ on time ≈ +1 min
23:38on time +1 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

DateLast stopFinalMax
Fri 6 Nov— 23:090 min—
Thu 5 Nov— 23:390 min—
Wed 4 Nov— 23:390 min—
Mon 2 Nov— 23:39+1 min—
Sun 1 NovSchiphol Airport 23:390 min—
Sat 31 OctSchiphol Airport 23:250 min—
Thu 29 Oct— 23:390 min—
Wed 28 Oct— 23:390 min—
Tue 27 Oct— 00:020 min—
Mon 26 Oct— 23:43No data—
Sun 25 OctSchiphol Airport 23:38No data—
Sat 24 Oct— 23:390 min—
Fri 23 Oct— 23:41+1 min+1 min
Thu 22 Oct— 23:390 min—
Wed 21 Oct— 23:390 min—
Tue 20 Oct— 23:39No data—
Mon 19 Oct— 23:240 min—
Sun 18 OctSchiphol Airport 23:390 min—
Sat 17 OctSchiphol Airport 23:400 min—
Fri 16 Oct— 23:390 min—
Thu 15 Oct— 23:41No data—
Wed 14 Oct— 23:39No data—
Tue 13 Oct— 23:39No data—
Mon 12 Oct— 23:390 min—
Sun 11 OctSchiphol Airport 23:41Partial coverage+1 min+1 min
Sat 10 Oct— 23:400 min—
Fri 9 Oct— 23:48+5 min+6 min
Thu 8 Oct— 23:390 min—
Wed 7 Oct— 23:50No data—
Tue 6 Oct— 23:390 min—