Train NS 5852 Amersfoort Vathorst – Amsterdam Centraal

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

Running now · updated 16:21

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 16:19

  1. Amersfoort Vathorst15:22
  2. Amersfoort Centraal15:30
  3. Hilversum15:44
  4. Bussum Zuid15:51
  5. Weesp16:00
  6. Amsterdam Science Park16:10
  7. Amsterdam Centraal16:19

Today it is running no worse than usual: typical arrival delay is 0 min; 90% of the last 10 runs arrived on time.

Open live map ↗ Full trip card
Open live card ↗
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 3 full · 7 partial · 20 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 3 full · 7 partial · 79 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

Worst days

  • Sat 10 Oct Max en route +4 min · last fix heading to Amsterdam Muiderpoort +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 9
  • 3–10 min 10% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.Today
Amersfoort Vathorst
15:22
Amersfoort Schothorst
15:26
Amersfoort Centraal
15:30 / 15:31
Baarn
15:38
Hilversum
15:44 / 15:45
Hilversum Media Park
15:47
Bussum Zuid
15:51
Naarden-Bussum
15:54
Weesp
16:00 / 16:02
Diemen
16:07
Amsterdam Science Park
16:10
Amsterdam Muiderpoort
16:13
Amsterdam Centraal
16: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.

Recent runs

DateLast stopFinalMax
Mon 19 OctAmsterdam Muiderpoort 16:20Partial coverage0 min—
Sun 18 OctNaarden-Bussum 16:190 min+1 min
Sat 17 OctNaarden-Bussum 16:19No data—
Fri 16 OctAmsterdam Muiderpoort 16:27No data—
Thu 15 OctAmsterdam Muiderpoort 16:28No data—
Wed 14 OctAmsterdam Muiderpoort 16:29No data—
Tue 13 OctAmsterdam Muiderpoort 16:27No data—
Mon 12 OctAmsterdam Muiderpoort 16:270 min—
Sun 11 OctAmsterdam Muiderpoort 16:27Partial coverage0 min—
Sat 10 OctAmsterdam Muiderpoort 16:31Partial coverage+4 min+4 min
Fri 9 OctAmsterdam Muiderpoort 16:27Partial coverage0 min—
Thu 8 OctAmsterdam Muiderpoort 16:28Partial coverage+1 min—
Wed 7 OctAmsterdam Muiderpoort 16:27Partial coverage0 min—
Tue 6 OctAmsterdam Muiderpoort 16:27Partial coverage0 min—
Mon 5 OctAmsterdam Science Park 16:240 min—
Sun 4 OctAmsterdam Muiderpoort 16:30No data—
Sat 3 OctAmsterdam Science Park 16:27No data—
Fri 2 OctAmsterdam Muiderpoort 16:27No data—
Thu 1 OctAmsterdam Muiderpoort 16:27No data—
Wed 30 SeptAmsterdam Muiderpoort 16:33No data—
Tue 29 SeptAmsterdam Muiderpoort 16:31No data—
Mon 28 SeptAmsterdam Muiderpoort 16:28No data—
Sun 27 SeptAmsterdam Muiderpoort 16:29No data—
Sat 26 SeptAmsterdam Muiderpoort 16:28No data—
Fri 25 SeptAmsterdam Muiderpoort 16:27No data—
Thu 24 SeptAmsterdam Muiderpoort 16:27No data—
Wed 23 SeptAmsterdam Muiderpoort 16:28No data—
Tue 22 SeptAmsterdam Muiderpoort 16:27No data—
Mon 21 SeptAmsterdam Muiderpoort 16:27No data—
Sun 20 SeptAmsterdam Muiderpoort 16:28No data—