Train NS 5871 Amsterdam Centraal – Amersfoort Vathorst

Amsterdam Centraal 19:41 → Amersfoort Vathorst 20:37 Daily 0 h 56 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 19:41 from Amsterdam Centraal · Thu 5 Nov

Next departure 19:41 today · Amsterdam Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 14 full · 4 partial · 11 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 16 full · 4 partial · 36 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: +2 min

Last 30 days

Arrival delay at Amersfoort Vathorst, 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=3
  • 100% F n=3
  • 100% S n=3
  • 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
19:41on time on time
19:46≈ on time ≈ on time
19:49≈ on time ≈ on time
19:52≈ on time ≈ on time
19:57 / 19:59≈ on time ≈ on time
20:05≈ on time ≈ +1 min
20:08≈ on time ≈ +1 min
20:12≈ on time ≈ +1 min
20:14 / 20:15≈ on time ≈ +1 min
20:21≈ on time ≈ +1 min
20:28 / 20:29≈ on time ≈ +1 min
20:33≈ on time ≈ +1 min
20:37on 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 4 Nov— 20:39+2 min+2 min
Tue 3 Nov— 20:43No data—
Mon 2 Nov— 20:39No data—
Sun 1 NovAmersfoort Schothorst 20:47Partial coverage0 min—
Sat 31 OctAmersfoort Schothorst 20:47Partial coverage0 min+1 min
Fri 30 Oct— 20:41No data—
Thu 29 Oct— 20:380 min—
Wed 28 Oct— 20:49No data—
Tue 27 Oct— 20:410 min—
Mon 26 OctAmsterdam Muiderpoort 20:42No data—
Sun 25 OctAmersfoort Schothorst 20:47No data—
Sat 24 OctAmersfoort Schothorst 21:00Partial coverage0 min—
Fri 23 Oct— 20:49+1 min+1 min
Thu 22 Oct— 20:390 min—
Wed 21 Oct— 20:38No data—
Tue 20 Oct— 20:430 min—
Mon 19 Oct— 20:580 min—
Sun 18 OctBaarn 20:25+1 min—
Sat 17 OctBaarn 20:25No data—
Fri 16 OctDiemen 20:340 min—
Thu 15 Oct— 20:42No data—
Wed 14 OctAmsterdam Muiderpoort 20:35No data—
Tue 13 Oct— 20:36No data—
Mon 12 Oct— 20:350 min—
Sun 11 OctAmersfoort Schothorst 20:470 min—
Sat 10 OctAmersfoort Schothorst 20:51Partial coverage+2 min+3 min
Fri 9 Oct— 20:490 min—
Thu 8 Oct— 20:41+1 min+2 min
Wed 7 Oct— 20:490 min—
Tue 6 Oct— 20:39+1 min—