Train NS 5846 Amersfoort Vathorst – Amsterdam Centraal

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

✓ Today’s run finished

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

  1. Amersfoort Vathorst13:52
  2. Amersfoort Centraal14:00
  3. Hilversum14:14
  4. Bussum Zuid14:21
  5. Weesp14:30
  6. Amsterdam Muiderpoort14:43
  7. Amsterdam Centraal14:48

Next service: tomorrow 13:52 from Amersfoort Vathorst · Wed 28 Oct

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

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

  • Early 0% · 0
  • On time 100% · 16
  • 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=3
  • 100% W n=1
  • 100% T n=2
  • 100% F n=3
  • 100% S n=2
  • 100% S n=2

Stops and timetable

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

StopSched.
Amersfoort Vathorst
13:52
Amersfoort Schothorst
13:56
Amersfoort Centraal
14:00 / 14:01
Baarn
14:08
Hilversum
14:14 / 14:15
Hilversum Media Park
14:17
Bussum Zuid
14:21
Naarden-Bussum
14:24
Weesp
14:30 / 14:32
Diemen
14:37
Amsterdam Science Park
14:40
Amsterdam Muiderpoort
14:43
Amsterdam Centraal
14: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
Tue 27 OctAmsterdam Muiderpoort 14:57Partial coverage0 min—
Mon 26 OctAmsterdam Muiderpoort 14:57No data—
Sun 25 OctAmsterdam Muiderpoort 15:01No data—
Sat 24 OctAmsterdam Muiderpoort 14:57Partial coverage0 min—
Fri 23 OctAmsterdam Muiderpoort 15:010 min—
Thu 22 OctAmsterdam Muiderpoort 14:57No data—
Wed 21 OctAmsterdam Muiderpoort 14:57No data—
Tue 20 OctAmsterdam Muiderpoort 14:58Partial coverage0 min—
Mon 19 OctAmsterdam Muiderpoort 14:58Partial coverage0 min—
Sun 18 OctNaarden-Bussum 14:49+1 min—
Sat 17 OctNaarden-Bussum 14:50No data—
Fri 16 OctAmsterdam Muiderpoort 14:570 min—
Thu 15 OctAmsterdam Muiderpoort 14:570 min—
Wed 14 OctAmsterdam Muiderpoort 14:58No data—
Tue 13 OctAmsterdam Muiderpoort 14:57No data—
Mon 12 OctAmsterdam Muiderpoort 14:570 min—
Sun 11 OctAmsterdam Muiderpoort 14:57Partial coverage0 min—
Sat 10 OctAmsterdam Muiderpoort 14:58Partial coverage+1 min+1 min
Fri 9 OctAmsterdam Muiderpoort 14:58Partial coverage+1 min+1 min
Thu 8 OctAmsterdam Muiderpoort 14:57Partial coverage+2 min+2 min
Wed 7 OctAmsterdam Muiderpoort 14:57Partial coverage0 min—
Tue 6 OctAmsterdam Muiderpoort 14:57Partial coverage0 min—
Mon 5 OctAmsterdam Science Park 14:560 min—
Sun 4 OctAmsterdam Muiderpoort 15:00No data—
Sat 3 OctAmsterdam Science Park 15:00No data—
Fri 2 OctAmsterdam Muiderpoort 14:57No data—
Thu 1 OctAmsterdam Muiderpoort 14:58No data—
Wed 30 SeptAmsterdam Muiderpoort 14:57No data—
Tue 29 SeptAmsterdam Muiderpoort 14:57No data—
Mon 28 SeptAmsterdam Muiderpoort 14:58No data—