Train NS 5826 Amersfoort Vathorst – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 08:52 from Amersfoort Vathorst · Fri 6 Nov

Next departure 08:52 today · Amersfoort Vathorst
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 13 full · 3 partial · 12 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 13 full · 5 partial · 69 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: +1 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

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

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

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 100% W n=2
  • 100% T n=3
  • 100% F n=3
  • 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, 18 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
08:52on time on time
08:56≈ on time ≈ on time
09:00 / 09:01≈ on time ≈ on time
09:08≈ on time ≈ on time
09:14 / 09:15≈ on time ≈ +1 min
09:17≈ on time ≈ +1 min
09:21≈ on time ≈ +1 min
09:24≈ on time ≈ +1 min
09:30 / 09:32≈ on time ≈ +1 min
09:37≈ on time ≈ +1 min
09:40≈ on time ≈ +1 min
09:42 / 09:44≈ on time ≈ +1 min
09: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
Thu 5 NovAmsterdam Muiderpoort 09:58No data—
Wed 4 NovAmsterdam Muiderpoort 09:58Partial coverage+2 min+2 min
Tue 3 NovAmsterdam Muiderpoort 09:59No data—
Mon 2 NovAmsterdam Muiderpoort 09:58No data—
Sat 31 OctAmsterdam Muiderpoort 09:58+1 min+1 min
Fri 30 OctAmsterdam Muiderpoort 09:570 min—
Thu 29 OctAmsterdam Muiderpoort 09:570 min—
Wed 28 OctAmsterdam Muiderpoort 09:59No data—
Tue 27 OctAmsterdam Muiderpoort 09:570 min—
Mon 26 OctAmsterdam Muiderpoort 09:57No data—
Sun 25 OctAmsterdam Muiderpoort 09:57No data—
Sat 24 OctAmsterdam Muiderpoort 09:570 min—
Fri 23 OctAmsterdam Muiderpoort 09:57No data—
Thu 22 OctAmsterdam Muiderpoort 09:580 min—
Wed 21 OctAmsterdam Muiderpoort 09:58No data—
Tue 20 OctAmsterdam Muiderpoort 09:580 min—
Mon 19 OctAmsterdam Muiderpoort 10:01Partial coverage0 min—
Sun 18 OctNaarden-Bussum 09:490 min+1 min
Sat 17 OctNaarden-Bussum 09:490 min+1 min
Fri 16 OctAmsterdam Muiderpoort 09:580 min—
Thu 15 OctNaarden-Bussum 10:58No data—
Wed 14 OctAmsterdam Muiderpoort 10:08No data—
Tue 13 OctAmsterdam Muiderpoort 09:58No data—
Mon 12 OctAmsterdam Muiderpoort 10:03No data—
Sun 11 OctAmsterdam Muiderpoort 09:58+2 min+3 min
Sat 10 OctAmsterdam Muiderpoort 09:570 min—
Fri 9 OctAmsterdam Muiderpoort 09:580 min—
Thu 8 OctAmsterdam Muiderpoort 09:58Partial coverage0 min—
Wed 7 OctAmsterdam Muiderpoort 09:58Partial coverage0 min+1 min
Tue 6 OctAmsterdam Muiderpoort 09:58Partial coverage0 min—