Train NS 5884 Amersfoort Centraal – Amsterdam Centraal

Amersfoort Centraal 23:31 → Amsterdam Centraal 00:19 Daily 0 h 48 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 23:31 from Amersfoort Centraal · Fri 6 Nov

Next departure 23:31 today · Amersfoort Centraal
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 22 full · 3 partial · 4 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 26 full · 3 partial · 16 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: 0 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

  • Fri 23 Oct Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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:31on time +1 min
23:38≈ on time ≈ +1 min
23:44 / 23:45≈ on time ≈ +1 min
23:47≈ on time ≈ +1 min
23:51≈ on time ≈ +1 min
23:54≈ on time ≈ +1 min
00:00 / 00:02≈ on time ≈ +1 min
00:07≈ on time ≈ +1 min
00:10≈ on time ≈ +1 min
00:13≈ on time ≈ +1 min
00:19on time on time

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:330 min—
Wed 4 Nov— 00:190 min+2 min
Tue 3 Nov— 00:190 min—
Mon 2 Nov— 00:240 min+7 min
Sun 1 NovAmsterdam Muiderpoort 00:27Partial coverage0 min+3 min
Sat 31 OctAmersfoort Vathorst 00:20Partial coverage0 min—
Fri 30 Oct— 00:210 min—
Thu 29 Oct— 00:380 min+3 min
Wed 28 Oct— 00:200 min—
Tue 27 Oct— 00:210 min—
Mon 26 Oct— 00:280 min—
Sun 25 OctAmsterdam Muiderpoort 00:27No data—
Sat 24 Oct— 00:28No data—
Fri 23 Oct— 00:27+4 min+5 min
Thu 22 Oct— 00:31No data—
Wed 21 Oct— 00:310 min—
Tue 20 Oct— 00:270 min—
Mon 19 Oct— 00:250 min+5 min
Sun 18 OctNaarden-Bussum 00:20Partial coverage0 min—
Sat 17 OctNaarden-Bussum 00:200 min—
Fri 16 Oct— 00:200 min—
Thu 15 Oct— 00:220 min—
Wed 14 Oct— 00:200 min—
Tue 13 Oct— 00:21No data—
Mon 12 Oct— 00:21+1 min—
Sun 11 OctAmsterdam Muiderpoort 00:350 min+10 min
Sat 10 Oct— 00:210 min+2 min
Fri 9 Oct— 00:200 min+2 min
Thu 8 Oct— 00:200 min+3 min
Wed 7 Oct— 00:200 min+2 min