Train NS 5838 Amersfoort Vathorst – Amsterdam Centraal

Amersfoort Vathorst 11:52 → Amsterdam Centraal 12:49 Daily 0 h 57 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 11:52 from Amersfoort Vathorst · Sun 8 Nov

Next departure 11:52 today · Amersfoort Vathorst
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 13 full · 1 partial · 14 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 18 full · 1 partial · 68 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: 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=5
  • 100% T n=1
  • 100% W n=2
  • 100% T n=3
  • 100% F n=2
  • 100% S n=4
  • 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
11:52on time on time
11:56≈ on time ≈ on time
12:00 / 12:01≈ on time ≈ on time
12:08≈ on time ≈ on time
12:14 / 12:15≈ on time ≈ on time
12:17≈ on time ≈ on time
12:21≈ on time ≈ on time
12:24≈ on time ≈ on time
12:30 / 12:32≈ on time ≈ on time
12:37≈ on time ≈ on time
12:40≈ on time ≈ +1 min
12:43≈ on time ≈ +1 min
12:49on 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
Sat 7 NovAmsterdam Muiderpoort 12:58Partial coverage+1 min+2 min
Fri 6 NovAmsterdam Muiderpoort 12:57No data—
Thu 5 NovAmsterdam Muiderpoort 12:570 min—
Wed 4 NovAmsterdam Muiderpoort 12:570 min—
Tue 3 NovAmsterdam Muiderpoort 12:57No data—
Mon 2 NovAmsterdam Muiderpoort 12:570 min—
Sat 31 OctAmsterdam Muiderpoort 12:570 min—
Fri 30 OctAmsterdam Muiderpoort 12:57No data—
Thu 29 OctAmsterdam Muiderpoort 12:570 min—
Wed 28 OctAmsterdam Muiderpoort 12:57No data—
Tue 27 OctAmsterdam Muiderpoort 12:57No data—
Mon 26 OctAmersfoort Centraal 15:580 min—
Sun 25 OctAmsterdam Muiderpoort 12:57No data—
Sat 24 OctAmsterdam Muiderpoort 12:570 min—
Fri 23 OctAmsterdam Muiderpoort 12:58No data—
Thu 22 OctAmsterdam Muiderpoort 12:59No data—
Wed 21 OctAmsterdam Muiderpoort 12:57No data—
Tue 20 OctAmsterdam Muiderpoort 12:57No data—
Mon 19 OctAmsterdam Muiderpoort 12:570 min—
Sun 18 OctNaarden-Bussum 12:50+1 min+2 min
Sat 17 OctNaarden-Bussum 12:51No data—
Fri 16 OctAmsterdam Muiderpoort 12:570 min—
Thu 15 OctAmsterdam Muiderpoort 12:57No data—
Wed 14 OctAmsterdam Muiderpoort 12:57No data—
Tue 13 OctAmsterdam Muiderpoort 12:57No data—
Mon 12 OctAmsterdam Muiderpoort 12:570 min—
Sun 11 OctAmsterdam Muiderpoort 12:570 min—
Sat 10 OctAmsterdam Muiderpoort 12:570 min—
Fri 9 OctAmsterdam Muiderpoort 12:58+1 min+1 min
Thu 8 OctAmsterdam Muiderpoort 12:570 min—