Train NS 12481 Rotterdam Centraal – Amsterdam Zuid

Rotterdam Centraal 22:52 → Amsterdam Zuid 23:25 Daily 0 h 33 min · 3 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November +10 min

Next service: Monday 22:52 from Rotterdam Centraal · Mon 9 Nov

Next departure 22:52 Monday · Rotterdam Centraal
On-time · 30 days
74%
14/19 runs under 3 min
RT coverage: 16 full · 3 partial · 9 no data
On-time · 90 days
78%
18/23 runs under 3 min
RT coverage: 20 full · 3 partial · 17 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Amsterdam Zuid, 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 +49 min · last fix heading to — +49 min
  • Fri 23 Oct Max en route +12 min · last fix heading to — +12 min
  • Fri 6 Nov Max en route +10 min · last fix heading to — +10 min
  • Fri 16 Oct Max en route +3 min · last fix heading to — +3 min
  • Mon 2 Nov Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 18
  • 3–10 min 9% · 2
  • 10–30 min 9% · 2
  • 30+ min 4% · 1

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=4
  • 0% 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, 23 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 10
22:52on time +3 min
23:18 / 23:19≈ +1 min ≈ +9 min
23:25+1 min +10 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:44+10 min+10 min
Thu 5 Nov— 23:340 min—
Wed 4 Nov— 23:29+1 min+1 min
Tue 3 Nov— 23:24No data—
Mon 2 Nov— 23:33+3 min+4 min
Sun 1 NovSchiphol Airport 23:33Partial coverage0 min—
Sat 31 OctSchiphol Airport 23:33Partial coverage0 min—
Fri 30 Oct— 23:28No data—
Wed 28 Oct— 23:08No data—
Tue 27 Oct— 23:270 min—
Mon 26 Oct— 23:26No data—
Sun 25 OctSchiphol Airport 23:36No data—
Sat 24 Oct— 23:280 min—
Fri 23 Oct— 23:51+12 min+12 min
Thu 22 Oct— 23:270 min—
Wed 21 Oct— 23:26No data—
Tue 20 Oct— 23:32No data—
Mon 19 Oct— 23:29No data—
Sun 18 OctSchiphol Airport 23:37+1 min+4 min
Sat 17 OctSchiphol Airport 23:340 min—
Fri 16 Oct— 23:32+3 min+3 min
Thu 15 Oct— 23:320 min—
Wed 14 Oct— 23:260 min—
Tue 13 Oct— 23:26No data—
Mon 12 Oct— 23:29+2 min+3 min
Sun 11 OctSchiphol Airport 23:34Partial coverage+1 min+1 min
Sat 10 Oct— 23:270 min—
Fri 9 Oct— 01:04+49 min+49 min
Thu 8 Oct— 23:28+1 min+1 min
Wed 7 Oct— 23:260 min—