Train NS 5838 Amersfoort Vathorst – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Amsterdam Muiderpoort at 12:57 0 min

  1. Amersfoort Vathorst11:52
  2. Amersfoort Centraal12:00
  3. Hilversum12:14
  4. Bussum Zuid12:21
  5. Weesp12:30
  6. Amsterdam Muiderpoort12:43
  7. Amsterdam Centraal12:48

Next service: tomorrow 11:52 from Amersfoort Vathorst · Tue 20 Oct

Full trip card
Next departure 11:52 tomorrow · Amersfoort Vathorst
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 4 full · 7 partial · 19 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 4 full · 7 partial · 78 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

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

  • Early 0% · 0
  • On time 100% · 11
  • 3–10 min 0% · 0
  • 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=2
  • 100% S n=1
  • 100% S n=2

Stops and timetable

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

StopSched.
Amersfoort Vathorst
11:52
Amersfoort Schothorst
11:56
Amersfoort Centraal
12:00 / 12:01
Baarn
12:08
Hilversum
12:14 / 12:15
Hilversum Media Park
12:17
Bussum Zuid
12:21
Naarden-Bussum
12:24
Weesp
12:30 / 12:32
Diemen
12:37
Amsterdam Science Park
12:40
Amsterdam Muiderpoort
12:43
Amsterdam Centraal
12:48

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 12:57Partial coverage0 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:57Partial coverage0 min—
Sat 10 OctAmsterdam Muiderpoort 12:57Partial coverage0 min—
Fri 9 OctAmsterdam Muiderpoort 12:58Partial coverage+1 min+1 min
Thu 8 OctAmsterdam Muiderpoort 12:57Partial coverage0 min—
Wed 7 OctAmsterdam Muiderpoort 12:57Partial coverage0 min—
Tue 6 OctAmsterdam Muiderpoort 12:58Partial coverage0 min—
Mon 5 OctAmsterdam Science Park 12:550 min—
Sun 4 OctAmsterdam Muiderpoort 13:00No data—
Sat 3 OctAmsterdam Science Park 12:56No data—
Fri 2 OctAmsterdam Muiderpoort 12:57No data—
Thu 1 OctAmsterdam Muiderpoort 12:57No data—
Wed 30 SeptAmsterdam Muiderpoort 12:58No data—
Tue 29 SeptAmsterdam Muiderpoort 12:57No data—
Mon 28 SeptAmsterdam Muiderpoort 12:57No data—
Sun 27 SeptAmsterdam Muiderpoort 12:59No data—
Sat 26 SeptAmsterdam Muiderpoort 13:03No data—
Fri 25 SeptAmsterdam Muiderpoort 12:57No data—
Thu 24 SeptAmsterdam Muiderpoort 12:57No data—
Wed 23 SeptAmsterdam Muiderpoort 12:57No data—
Tue 22 SeptAmsterdam Muiderpoort 12:57No data—
Mon 21 SeptAmsterdam Muiderpoort 12:57No data—
Sun 20 SeptAmsterdam Muiderpoort 12:57No data—