Train NS 5878 Amersfoort Vathorst – Amsterdam Centraal

Amersfoort Vathorst 21:52 → Amsterdam Centraal 22:49 Daily 0 h 57 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November +2 min

Next service: today 21:52 from Amersfoort Vathorst · Sun 15 Nov

Next departure 21:52 today · Amersfoort Vathorst
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 14 full · 3 partial · 12 no data
On-time · 90 days
86%
25/29 runs under 3 min
RT coverage: 26 full · 3 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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 13 Nov Max en route +29 min · last fix heading to — +29 min
  • Sun 11 Oct Max en route +8 min · last fix heading to Amsterdam Muiderpoort +6 min
  • Mon 2 Nov Max en route +6 min · last fix heading to — +6 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Naarden-Bussum +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 86% · 25
  • 3–10 min 10% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 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
21:52on time on time
21:56≈ on time ≈ on time
22:00 / 22:01≈ on time ≈ +1 min
22:08≈ on time ≈ +1 min
22:14 / 22:15≈ on time ≈ +2 min
22:17≈ on time ≈ +2 min
22:21≈ on time ≈ +3 min
22:24≈ on time ≈ +3 min
22:30 / 22:32≈ on time ≈ +3 min
22:37≈ on time ≈ +4 min
22:40≈ on time ≈ +4 min
22:43≈ on time ≈ +5 min
22:49on time +5 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
Sat 14 NovAmsterdam Muiderpoort 22:57Partial coverage+2 min+2 min
Fri 13 Nov— 23:29+29 min+29 min
Thu 12 Nov— 22:490 min—
Wed 11 Nov— 22:490 min—
Tue 10 Nov— 22:49+1 min+2 min
Mon 9 Nov— 22:49+1 min—
Sun 8 NovAmsterdam Muiderpoort 22:570 min—
Sat 7 NovAmsterdam Muiderpoort 22:57Partial coverage0 min—
Fri 6 Nov— 22:490 min—
Thu 5 Nov— 22:49No data—
Wed 4 Nov— 22:49+1 min—
Tue 3 Nov— 22:49No data—
Mon 2 Nov— 22:59+6 min+6 min
Sun 1 NovAmsterdam Muiderpoort 22:57Partial coverage0 min—
Sat 31 OctAmsterdam Muiderpoort 22:57No data—
Fri 30 Oct— 22:51No data—
Thu 29 Oct— 22:500 min—
Wed 28 Oct— 22:50No data—
Tue 27 Oct— 22:51No data—
Mon 26 Oct— 22:500 min—
Sun 25 OctAmsterdam Muiderpoort 22:57No data—
Sat 24 OctDiemen 22:59No data—
Fri 23 Oct— 22:55+2 min+3 min
Thu 22 Oct— 22:51No data—
Wed 21 Oct— 22:51No data—
Tue 20 Oct— 22:500 min—
Mon 19 Oct— 22:50No data—
Sun 18 OctNaarden-Bussum 22:53+4 min+5 min
Sat 17 OctNaarden-Bussum 22:48No data—
Fri 16 Oct— 22:52+1 min—