Train NS 5854 Amersfoort Vathorst – Amsterdam Centraal

Amersfoort Vathorst 15:52 → Amsterdam Centraal 16:48 Daily 0 h 56 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +3 min

Next service: today 15:52 from Amersfoort Vathorst · Mon 16 Nov

Next departure 15:52 today · Amersfoort Vathorst
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 15 full · 4 partial · 10 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 22 full · 6 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Mon 9 Nov Max en route +6 min · last fix heading to Amsterdam Muiderpoort +4 min
  • Sun 15 Nov Max en route +3 min · last fix heading to Amsterdam Muiderpoort +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
15:52on time on time
15:56≈ on time ≈ on time
16:00 / 16:01≈ on time ≈ on time
16:08≈ on time ≈ +1 min
16:14 / 16:15≈ on time ≈ +1 min
16:17≈ on time ≈ +1 min
16:21≈ on time ≈ +1 min
16:24≈ on time ≈ +1 min
16:30 / 16:32≈ on time ≈ +2 min
16:37≈ on time ≈ +2 min
16:40≈ on time ≈ +2 min
16:43≈ on time ≈ +2 min
16:48on time +2 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
Sun 15 NovAmsterdam Muiderpoort 16:59Partial coverage+3 min+3 min
Sat 14 NovAmsterdam Muiderpoort 16:58Partial coverage0 min—
Fri 13 NovAmsterdam Muiderpoort 16:59+2 min+3 min
Thu 12 NovAmsterdam Muiderpoort 16:59+3 min+3 min
Wed 11 NovAmsterdam Muiderpoort 16:580 min—
Tue 10 NovAmsterdam Muiderpoort 16:59+2 min+3 min
Mon 9 NovAmsterdam Muiderpoort 17:03+4 min+6 min
Sun 8 NovAmsterdam Muiderpoort 16:580 min—
Sat 7 NovAmsterdam Muiderpoort 16:570 min—
Fri 6 NovAmsterdam Muiderpoort 16:57No data—
Thu 5 NovAmsterdam Muiderpoort 16:570 min—
Wed 4 NovAmsterdam Muiderpoort 16:570 min—
Tue 3 NovAmsterdam Muiderpoort 16:57No data—
Mon 2 NovAmsterdam Muiderpoort 16:590 min—
Sun 1 NovAmsterdam Muiderpoort 16:57Partial coverage0 min—
Sat 31 OctAmsterdam Muiderpoort 16:57Partial coverage0 min—
Fri 30 OctAmsterdam Muiderpoort 16:57No data—
Thu 29 OctAmsterdam Muiderpoort 16:570 min—
Wed 28 OctAmsterdam Muiderpoort 16:57No data—
Tue 27 OctAmsterdam Muiderpoort 16:57No data—
Mon 26 OctAmsterdam Muiderpoort 16:570 min—
Sun 25 OctAmsterdam Muiderpoort 16:57No data—
Sat 24 OctAmsterdam Muiderpoort 16:570 min—
Fri 23 OctAmsterdam Muiderpoort 16:57No data—
Thu 22 OctAmsterdam Muiderpoort 16:57No data—
Wed 21 OctAmsterdam Muiderpoort 16:57No data—
Tue 20 OctAmsterdam Muiderpoort 16:58No data—
Mon 19 OctAmsterdam Muiderpoort 17:000 min—
Sun 18 OctNaarden-Bussum 16:50+2 min+2 min
Sat 17 OctNaarden-Bussum 16:49No data—