Train NS 5872 Amersfoort Vathorst – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 20:22 from Amersfoort Vathorst · Fri 6 Nov

Next departure 20:22 today · Amersfoort Vathorst
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 13 full · 4 partial · 11 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 16 full · 4 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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:22on time on time
20:26≈ on time ≈ on time
20:30 / 20:31≈ on time ≈ on time
20:38≈ on time ≈ +1 min
20:44 / 20:45≈ on time ≈ +1 min
20:47≈ on time ≈ +1 min
20:51≈ on time ≈ +1 min
20:54≈ on time ≈ +1 min
21:00 / 21:02≈ on time ≈ +1 min
21:07≈ on time ≈ +1 min
21:10≈ on time ≈ +2 min
21:13≈ on time ≈ +2 min
21:19on 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
Thu 5 Nov— 21:390 min—
Wed 4 Nov— 21:190 min—
Mon 2 Nov— 21:190 min—
Sun 1 NovAmsterdam Muiderpoort 21:27Partial coverage0 min—
Sat 31 OctAmsterdam Muiderpoort 21:28Partial coverage0 min—
Fri 30 Oct— 21:21No data—
Thu 29 Oct— 21:190 min—
Wed 28 Oct— 21:21No data—
Tue 27 Oct— 21:210 min—
Mon 26 Oct— 21:25No data—
Sun 25 OctAmsterdam Muiderpoort 21:27No data—
Sat 24 OctAmsterdam Muiderpoort 21:27No data—
Fri 23 Oct— 21:21+1 min+2 min
Thu 22 Oct— 21:390 min—
Wed 21 Oct— 21:23No data—
Tue 20 Oct— 21:380 min—
Mon 19 Oct— 21:21No data—
Sun 18 OctNaarden-Bussum 21:21+3 min+4 min
Sat 17 OctNaarden-Bussum 21:19No data—
Fri 16 Oct— 21:200 min—
Thu 15 Oct— 21:20No data—
Wed 14 Oct— 21:21No data—
Tue 13 Oct— 21:21No data—
Mon 12 Oct— 21:200 min—
Sun 11 OctAmsterdam Muiderpoort 21:27Partial coverage0 min—
Sat 10 OctAmsterdam Muiderpoort 21:27Partial coverage0 min+2 min
Fri 9 Oct— 21:26+2 min+4 min
Thu 8 Oct— 21:390 min—
Wed 7 Oct— 21:200 min—
Tue 6 Oct— 21:200 min+1 min