Train NS 5885 Amsterdam Centraal – Amersfoort Centraal

Amsterdam Centraal 23:11 → Amersfoort Centraal 23:58 Daily 0 h 47 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 23:11 from Amsterdam Centraal · Thu 12 Nov

Full trip card
Next departure 23:11 today · Amsterdam Centraal
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 21 full · 2 partial · 5 no data
On-time · 90 days
97%
31/32 runs under 3 min
RT coverage: 30 full · 2 partial · 18 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: 0 min

Last 30 days

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

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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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
Amsterdam Centraal
23:11on time on time
Amsterdam Muiderpoort
23:17≈ on time ≈ on time
Amsterdam Science Park
23:20≈ on time ≈ on time
Diemen
23:22≈ on time ≈ on time
Weesp
23:27 / 23:29≈ on time ≈ on time
Naarden-Bussum
23:35≈ on time ≈ on time
Bussum Zuid
23:38≈ on time ≈ on time
Hilversum Media Park
23:42≈ on time ≈ on time
Hilversum
23:45≈ on time ≈ +1 min
Baarn
23:51≈ on time ≈ +1 min
Amersfoort Centraal
23:58on 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
Wed 11 Nov— 00:000 min—
Tue 10 Nov— 23:590 min—
Mon 9 Nov— 23:590 min—
Sun 8 NovBaarn 00:04Partial coverage0 min—
Sat 7 NovDiemen 00:080 min—
Fri 6 Nov— 00:080 min—
Thu 5 Nov— 23:59No data—
Wed 4 Nov— 23:590 min—
Tue 3 Nov— 23:59No data—
Mon 2 Nov— 00:04+4 min+4 min
Sun 1 NovBaarn 00:04Partial coverage0 min—
Sat 31 OctDiemen 00:180 min—
Thu 29 Oct— 00:060 min+4 min
Wed 28 Oct— 00:030 min—
Tue 27 Oct— 00:040 min—
Mon 26 Oct— 00:030 min—
Sun 25 OctBaarn 00:050 min—
Sat 24 Oct— 00:09No data—
Fri 23 Oct— 00:090 min—
Thu 22 Oct— 00:02No data—
Wed 21 Oct— 00:050 min—
Tue 20 Oct— 00:060 min—
Mon 19 Oct— 23:59+2 min+2 min
Sun 18 OctBaarn 23:540 min—
Sat 17 OctBaarn 23:54No data—
Fri 16 Oct— 00:050 min—
Thu 15 Oct— 00:070 min—
Wed 14 Oct— 00:050 min—
Tue 13 Oct— 00:050 min—
Mon 12 Oct— 00:050 min—