Train NS 5874 Amersfoort Vathorst – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Wednesday 18 November +3 min

Next service: today 20:52 from Amersfoort Vathorst · Thu 19 Nov

Next departure 20:52 today · Amersfoort Vathorst
On-time · 30 days
81%
17/21 runs under 3 min
RT coverage: 18 full · 3 partial · 6 no data
On-time · 90 days
85%
28/33 runs under 3 min
RT coverage: 28 full · 5 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +6 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 +19 min · last fix heading to — +19 min
  • Thu 12 Nov Max en route +13 min · last fix heading to — +13 min
  • Tue 10 Nov Max en route +6 min · last fix heading to — +6 min
  • Thu 8 Oct Max en route +6 min · last fix heading to — +4 min
  • Wed 11 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 28
  • 3–10 min 9% · 3
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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