Train NS 5864 Amersfoort Vathorst – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 18:22 from Amersfoort Vathorst · Thu 5 Nov

Next departure 18:22 today · Amersfoort Vathorst
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 11 full · 9 partial · 8 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 13 full · 9 partial · 47 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: 0 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=5
  • 100% T n=2
  • 100% F n=4
  • 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, 22 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:22on time on time
18:26≈ on time ≈ on time
18:30 / 18:31≈ on time ≈ on time
18:38≈ on time ≈ on time
18:44 / 18:45≈ on time ≈ on time
18:47≈ on time ≈ on time
18:51≈ on time ≈ on time
18:54≈ on time ≈ on time
19:00 / 19:02≈ on time ≈ on time
19:07≈ on time ≈ on time
19:10≈ on time ≈ on time
19:13≈ on time ≈ on time
19:19on 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— 19:190 min—
Mon 2 Nov— 19:19No data—
Sun 1 NovAmsterdam Muiderpoort 19:27Partial coverage0 min—
Sat 31 OctAmsterdam Muiderpoort 19:27Partial coverage0 min—
Fri 30 OctNaarden-Bussum 19:20Partial coverage0 min—
Thu 29 Oct— 19:21+1 min—
Wed 28 Oct— 19:200 min—
Tue 27 Oct— 19:210 min—
Mon 26 Oct— 19:190 min—
Sun 25 OctAmsterdam Muiderpoort 19:27No data—
Sat 24 OctAmsterdam Muiderpoort 19:27No data—
Fri 23 OctAmsterdam Muiderpoort 19:27Partial coverage0 min—
Thu 22 OctHilversum 19:21No data—
Wed 21 OctBaarn 19:21Partial coverage0 min—
Tue 20 OctHilversum 19:21No data—
Mon 19 OctBaarn 19:21Partial coverage0 min—
Sun 18 OctNaarden-Bussum 19:200 min+2 min
Sat 17 OctNaarden-Bussum 19:19No data—
Fri 16 OctAmsterdam Muiderpoort 19:270 min—
Thu 15 OctAmersfoort Centraal 19:25No data—
Wed 14 OctAmsterdam Muiderpoort 19:270 min—
Tue 13 OctBaarn 19:21No data—
Mon 12 OctHilversum 19:210 min—
Sun 11 OctAmsterdam Muiderpoort 19:27Partial coverage0 min—
Sat 10 OctAmsterdam Muiderpoort 19:27Partial coverage0 min—
Fri 9 OctAmersfoort Centraal 19:20Partial coverage0 min—
Thu 8 Oct— 19:200 min—
Wed 7 Oct— 19:200 min—
Tue 6 Oct— 19:20+1 min+2 min
Mon 5 Oct— 19:150 min—