Train NS 11891 Rotterdam Centraal – Amsterdam Zuid

Rotterdam Centraal 23:41 → Amsterdam Zuid 00:15 Mon, Tue, Wed, Thu, Sun 0 h 34 min · 3 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 5 November No data

Next service: Monday 23:41 from Rotterdam Centraal · Mon 9 Nov

Next departure 23:41 Monday · Rotterdam Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 13 full · 4 partial · 4 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Mon 2 Nov Max en route +7 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=5
  • 100% W n=4
  • 100% T n=2
  • — F n=0
  • — S n=0
  • 100% S n=4

Stops and timetable

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

Last 90 days, 19 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
23:41on time on time
00:07 / 00:08≈ on time ≈ +1 min
00:15on 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
Thu 5 Nov— 00:24No data—
Wed 4 Nov— 00:140 min—
Tue 3 Nov— 00:170 min—
Mon 2 Nov— 00:29+6 min+7 min
Sun 1 NovSchiphol Airport 00:22Partial coverage0 min—
Thu 29 Oct— 00:22+2 min+3 min
Wed 28 Oct— 00:170 min—
Tue 27 Oct— 00:160 min—
Mon 26 Oct— 00:160 min—
Sun 25 OctSchiphol Airport 00:23Partial coverage0 min—
Thu 22 Oct— 00:17No data—
Wed 21 Oct— 00:160 min—
Tue 20 Oct— 00:550 min—
Mon 19 Oct— 00:170 min—
Sun 18 OctSchiphol Airport 00:26Partial coverage0 min+3 min
Thu 15 Oct— 00:17No data—
Wed 14 Oct— 00:16No data—
Tue 13 Oct— 00:170 min—
Mon 12 Oct— 00:160 min—
Sun 11 OctSchiphol Airport 00:22Partial coverage0 min—
Thu 8 Oct— 00:160 min—
Wed 7 Oct— 00:160 min—
Tue 6 Oct— 00:160 min—
Mon 5 OctRotterdam Centraal 00:16No data—
Sun 4 OctSchiphol Airport 00:22No data—
Sun 20 SeptSchiphol Airport 00:24No data—
Sun 13 SeptRotterdam Centraal 23:56No data—
Sun 30 AugSchiphol Airport 00:22No data—
Sun 16 AugLeiden Centraal 01:22No data—
Sun 9 AugSchiphol Airport 00:22No data—