Train NS 5865 Amsterdam Centraal – Amersfoort Vathorst

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

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 18:11 from Amsterdam Centraal · Thu 12 Nov

Next departure 18:11 today · Amsterdam Centraal
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 4 full · 11 partial · 14 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 10 full · 13 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Tue 10 Nov Max en route +7 min · last fix heading to Amsterdam Science Park +7 min
  • Thu 29 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
18:11on time on time
18:16≈ on time ≈ on time
18:19≈ on time ≈ on time
18:22≈ on time ≈ on time
18:27 / 18:29≈ on time ≈ on time
18:35≈ on time ≈ on time
18:38≈ on time ≈ on time
18:42≈ on time ≈ +1 min
18:44 / 18:45≈ on time ≈ +1 min
18:51≈ on time ≈ +1 min
18:58 / 18:59≈ on time ≈ +1 min
19:03≈ on time ≈ +1 min
19:07on 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 11 NovAmsterdam Centraal 19:09Partial coverage0 min—
Tue 10 NovAmsterdam Science Park 18:53Partial coverage+7 min+7 min
Mon 9 NovAmsterdam Centraal 19:14Partial coverage+2 min+4 min
Sun 8 NovAmersfoort Schothorst 19:18Partial coverage0 min—
Sat 7 NovAmersfoort Schothorst 19:17Partial coverage0 min—
Fri 6 NovHilversum 19:14Partial coverage+3 min+4 min
Thu 5 NovAmsterdam Centraal 19:14No data—
Wed 4 NovAmsterdam Centraal 19:14No data—
Tue 3 NovAmsterdam Centraal 18:24No data—
Mon 2 NovWeesp 19:19Partial coverage+2 min+2 min
Sun 1 NovAmersfoort Schothorst 19:17Partial coverage0 min—
Sat 31 OctAmersfoort Schothorst 19:18Partial coverage+1 min—
Fri 30 OctBaarn 19:17No data—
Thu 29 Oct— 19:11+4 min+4 min
Wed 28 OctAmsterdam Centraal 18:250 min—
Tue 27 Oct— 19:20No data—
Mon 26 Oct— 19:11No data—
Sun 25 OctAmersfoort Schothorst 19:17No data—
Sat 24 OctAmersfoort Schothorst 19:190 min—
Fri 23 OctAmersfoort Schothorst 19:15Partial coverage+1 min+1 min
Thu 22 OctHilversum 19:21No data—
Wed 21 OctBussum Zuid 19:11No data—
Tue 20 OctHilversum 19:20No data—
Mon 19 OctHilversum Media Park 19:13Partial coverage0 min—
Sun 18 OctBaarn 18:540 min—
Sat 17 OctBaarn 18:55No data—
Fri 16 OctBaarn 19:11No data—
Thu 15 OctWeesp 19:07No data—
Wed 14 OctBaarn 19:09No data—
Tue 13 OctBussum Zuid 19:05No data—