Train NS 5832 Amersfoort Vathorst – Amsterdam Centraal

Amersfoort Vathorst 10:22 → Amsterdam Centraal 11: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 10:22 from Amersfoort Vathorst · Thu 5 Nov

Next departure 10:22 today · Amersfoort Vathorst
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 6 full · 12 partial · 10 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 7 full · 12 partial · 68 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

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

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

On-time by weekday

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

Stops and timetable

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

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