Train NS 5833 Amsterdam Centraal – Amersfoort Vathorst

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

✓ Today’s run finished

Today, last fix heading to Amersfoort Schothorst at 11:26 No data

  1. Amsterdam Centraal10:11
  2. Amsterdam Science Park10:19
  3. Weesp10:27
  4. Bussum Zuid10:38
  5. Hilversum10:44
  6. Amersfoort Schothorst11:03
  7. Amersfoort Vathorst11:07

Next service: tomorrow 10:11 from Amsterdam Centraal · Wed 21 Oct

Full trip card
Next departure 10:11 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 3 full · 6 partial · 21 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 3 full · 6 partial · 80 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Amersfoort Vathorst, 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

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

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

On-time by weekday

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

Stops and timetable

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

StopSched.
Amsterdam Centraal
10:11
Amsterdam Muiderpoort
10:16
Amsterdam Science Park
10:19
Diemen
10:22
Weesp
10:27 / 10:29
Naarden-Bussum
10:35
Bussum Zuid
10:38
Hilversum Media Park
10:42
Hilversum
10:44 / 10:45
Baarn
10:51
Amersfoort Centraal
10:58 / 10:59
Amersfoort Schothorst
11:03
Amersfoort Vathorst
11:07

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 20 OctAmersfoort Schothorst 11:26No data—
Mon 19 OctAmersfoort Schothorst 11:18Partial coverage0 min—
Sun 18 OctBaarn 10:55+1 min+1 min
Sat 17 OctBaarn 10:550 min—
Fri 16 OctBaarn 11:11No data—
Thu 15 OctBaarn 11:11No data—
Wed 14 OctBaarn 11:24No data—
Tue 13 OctBaarn 11:11No data—
Mon 12 OctBaarn 11:25No data—
Sun 11 OctAmersfoort Schothorst 11:18+1 min—
Sat 10 OctAmersfoort Schothorst 11:19Partial coverage+1 min+2 min
Fri 9 OctAmersfoort Schothorst 11:17Partial coverage0 min—
Thu 8 OctAmersfoort Schothorst 11:18Partial coverage+1 min—
Wed 7 OctAmersfoort Schothorst 12:01Partial coverage0 min—
Tue 6 OctAmersfoort Schothorst 11:19Partial coverage+1 min+1 min
Mon 5 OctAmersfoort Schothorst 11:17No data—
Sun 4 OctAlmere Oostvaarders 11:07No data—
Sat 3 OctAmersfoort Schothorst 11:17No data—
Fri 2 OctAmersfoort Schothorst 11:18No data—
Thu 1 OctAmersfoort Schothorst 11:19No data—
Wed 30 SeptAmersfoort Schothorst 11:18No data—
Tue 29 SeptAmersfoort Schothorst 11:18No data—
Mon 28 SeptAmersfoort Schothorst 11:17No data—
Sun 27 SeptNaarden-Bussum 10:50No data—
Sat 26 SeptNaarden-Bussum 10:53No data—
Fri 25 SeptAmersfoort Schothorst 11:17No data—
Thu 24 SeptAmersfoort Schothorst 11:18No data—
Wed 23 SeptAmersfoort Schothorst 11:18No data—
Tue 22 SeptAmersfoort Schothorst 11:21No data—
Mon 21 SeptAmersfoort Schothorst 11:17No data—