Train NS 5869 Amsterdam Centraal – Amersfoort Vathorst

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 19:11 today · Amsterdam Centraal
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 10 full · 5 partial · 13 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 12 full · 5 partial · 42 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

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

  • Early 0% · 0
  • On time 100% · 17
  • 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=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=2
  • 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, 17 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:11on time on time
19:16≈ on time ≈ on time
19:19≈ on time ≈ on time
19:22≈ on time ≈ on time
19:27 / 19:29≈ on time ≈ on time
19:35≈ on time ≈ on time
19:38≈ on time ≈ on time
19:42≈ on time ≈ on time
19:44 / 19:45≈ on time ≈ on time
19:51≈ on time ≈ on time
19:58 / 19:59≈ on time ≈ on time
20:03≈ on time ≈ on time
20:07on time on time

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:240 min+12 min
Tue 3 Nov— 20:09No data—
Mon 2 Nov— 20:08No data—
Sun 1 NovAmersfoort Schothorst 20:17Partial coverage0 min—
Sat 31 OctAmersfoort Schothorst 20:18Partial coverage+1 min—
Fri 30 Oct— 20:11No data—
Thu 29 Oct— 20:080 min—
Wed 28 Oct— 20:13No data—
Tue 27 Oct— 20:090 min—
Mon 26 OctHilversum 20:15No data—
Sun 25 OctAmersfoort Schothorst 20:17No data—
Sat 24 OctAmersfoort Schothorst 20:22No data—
Fri 23 OctDiemen 20:09Partial coverage0 min—
Thu 22 Oct— 20:12No data—
Wed 21 Oct— 20:09No data—
Mon 19 Oct— 20:200 min—
Sun 18 OctBaarn 19:550 min—
Sat 17 OctBaarn 19:580 min—
Fri 16 OctHilversum 20:05No data—
Thu 15 Oct— 20:05No data—
Wed 14 OctHilversum 20:06No data—
Tue 13 Oct— 20:06No data—
Mon 12 Oct— 20:050 min—
Sun 11 OctAmersfoort Schothorst 20:17Partial coverage0 min—
Sat 10 OctAmersfoort Schothorst 20:20Partial coverage+3 min+3 min
Fri 9 Oct— 20:080 min—
Thu 8 Oct— 20:190 min—
Wed 7 Oct— 20:080 min—
Tue 6 Oct— 20:080 min—
Mon 5 Oct— 20:090 min—