Train NS 5836 Amersfoort Vathorst – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

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

Next departure 11:22 today · Amersfoort Vathorst
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 2 full · 10 partial · 16 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 3 full · 14 partial · 70 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Worst days

  • Sat 10 Oct Max en route +11 min · last fix heading to Amsterdam Science Park +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=2
  • 100% T n=3
  • 100% F n=2
  • 75% 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, 17 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:22on time on time
11:26— —
11:30 / 11:31— —
11:38— —
11:44 / 11:45— —
11:47— —
11:51— —
11:54— —
12:00 / 12:02— —
12:07— —
12:10— —
12:13— —
12:19— —

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:27Partial coverage0 min—
Fri 6 NovAmsterdam Muiderpoort 12:27No data—
Thu 5 NovAmsterdam Muiderpoort 12:29No data—
Wed 4 NovAmsterdam Muiderpoort 12:27Partial coverage0 min—
Tue 3 NovAmsterdam Muiderpoort 12:29No data—
Mon 2 NovAmsterdam Muiderpoort 12:27No data—
Sat 31 OctAmsterdam Muiderpoort 12:29Partial coverage+2 min+2 min
Fri 30 OctAmsterdam Muiderpoort 12:29No data—
Thu 29 OctAmsterdam Muiderpoort 12:27Partial coverage0 min—
Wed 28 OctAmsterdam Muiderpoort 12:30No data—
Tue 27 OctAmsterdam Muiderpoort 12:28No data—
Mon 26 OctAmsterdam Muiderpoort 12:27No data—
Sun 25 OctAmsterdam Muiderpoort 12:28No data—
Sat 24 OctAmsterdam Muiderpoort 12:27Partial coverage0 min—
Fri 23 OctAmsterdam Muiderpoort 12:28Partial coverage0 min—
Thu 22 OctAmsterdam Muiderpoort 12:27Partial coverage0 min—
Wed 21 OctAmsterdam Muiderpoort 12:27No data—
Tue 20 OctAmsterdam Muiderpoort 12:27No data—
Mon 19 OctAmsterdam Muiderpoort 12:27Partial coverage0 min—
Sun 18 OctNaarden-Bussum 12:22+2 min+4 min
Sat 17 OctNaarden-Bussum 12:22No data—
Fri 16 OctAmsterdam Muiderpoort 12:28No data—
Thu 15 OctAmsterdam Muiderpoort 12:27No data—
Wed 14 OctAmsterdam Muiderpoort 12:32No data—
Tue 13 OctAmsterdam Muiderpoort 12:27No data—
Mon 12 OctAmsterdam Muiderpoort 12:290 min—
Sun 11 OctAmsterdam Muiderpoort 12:30Partial coverage+2 min+3 min
Sat 10 OctAmsterdam Science Park 12:41Partial coverage+10 min+11 min
Fri 9 OctAmsterdam Muiderpoort 12:30Partial coverage+2 min+3 min
Thu 8 OctAmsterdam Muiderpoort 12:27Partial coverage0 min—