Train NS 5848 Amersfoort Vathorst – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Amsterdam Muiderpoort at 15:28 No data

  1. Amersfoort Vathorst14:22
  2. Amersfoort Centraal14:30
  3. Hilversum14:44
  4. Bussum Zuid14:51
  5. Weesp15:00
  6. Amsterdam Muiderpoort15:13
  7. Amsterdam Centraal15:19

Next service: tomorrow 14:22 from Amersfoort Vathorst · Sat 24 Oct

Full trip card
Next departure 14:22 tomorrow · Amersfoort Vathorst
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 7 full · 6 partial · 17 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 7 full · 6 partial · 76 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

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

  • Early 0% · 0
  • On time 100% · 13
  • 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=3
  • 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
14:22
Amersfoort Schothorst
14:26
Amersfoort Centraal
14:30 / 14:31
Baarn
14:38
Hilversum
14:44 / 14:45
Hilversum Media Park
14:47
Bussum Zuid
14:51
Naarden-Bussum
14:54
Weesp
15:00 / 15:02
Diemen
15:07
Amsterdam Science Park
15:10
Amsterdam Muiderpoort
15:13
Amsterdam Centraal
15: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
Fri 23 OctAmsterdam Muiderpoort 15:28No data—
Thu 22 OctAmsterdam Muiderpoort 15:29No data—
Wed 21 OctAmsterdam Muiderpoort 15:27Partial coverage0 min—
Tue 20 OctAmsterdam Muiderpoort 15:27No data—
Mon 19 OctAmsterdam Muiderpoort 15:28Partial coverage0 min—
Sun 18 OctNaarden-Bussum 15:18+1 min+2 min
Sat 17 OctNaarden-Bussum 15:21No data—
Fri 16 OctAmsterdam Muiderpoort 15:270 min—
Thu 15 OctAmsterdam Muiderpoort 15:27No data—
Wed 14 OctAmsterdam Muiderpoort 15:280 min—
Tue 13 OctAmsterdam Muiderpoort 15:27No data—
Mon 12 OctAmsterdam Muiderpoort 15:270 min—
Sun 11 OctAmsterdam Muiderpoort 15:27Partial coverage0 min—
Sat 10 OctAmsterdam Muiderpoort 15:29Partial coverage+1 min+2 min
Fri 9 OctAmsterdam Muiderpoort 15:27Partial coverage0 min—
Thu 8 OctAmsterdam Muiderpoort 15:27Partial coverage0 min—
Wed 7 OctAmsterdam Muiderpoort 15:270 min—
Tue 6 OctAmsterdam Muiderpoort 15:270 min—
Mon 5 OctAmsterdam Science Park 15:26+1 min+2 min
Sun 4 OctAmsterdam Muiderpoort 15:30No data—
Sat 3 OctAmsterdam Science Park 15:26No data—
Fri 2 OctAmsterdam Muiderpoort 15:27No data—
Thu 1 OctAmsterdam Muiderpoort 15:27No data—
Wed 30 SeptAmsterdam Muiderpoort 15:28No data—
Tue 29 SeptAmsterdam Muiderpoort 15:27No data—
Mon 28 SeptAmsterdam Muiderpoort 15:28No data—
Sun 27 SeptAmsterdam Muiderpoort 15:27No data—
Sat 26 SeptAmsterdam Muiderpoort 15:26No data—
Fri 25 SeptAmsterdam Muiderpoort 15:27No data—
Thu 24 SeptAmsterdam Muiderpoort 15:27No data—