Train NS 5843 Amsterdam Centraal – Amersfoort Vathorst

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 12:41 from Amsterdam Centraal · Thu 5 Nov

Next departure 12:41 today · Amsterdam Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 5 full · 13 partial · 10 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 6 full · 14 partial · 67 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 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

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

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

Stops and timetable

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

Last 90 days, 20 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.

StopSched.Usually 9 days in 10
12:41on time on time
12:46≈ on time ≈ on time
12:49≈ on time ≈ on time
12:52≈ on time ≈ on time
12:57 / 12:59≈ on time ≈ on time
13:05≈ on time ≈ on time
13:08≈ on time ≈ on time
13:12≈ on time ≈ on time
13:14 / 13:15≈ on time ≈ on time
13:21≈ on time ≈ on time
13:28 / 13:29≈ on time ≈ +1 min
13:33≈ on time ≈ +1 min
13:37on time +1 min

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.

Will I make my connection?

Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.

Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.

Recent runs

DateLast stopFinalMax
Wed 4 NovAmersfoort Schothorst 13:48Partial coverage+1 min—
Tue 3 NovAmersfoort Schothorst 13:47No data—
Mon 2 NovAmersfoort Schothorst 13:49No data—
Sat 31 OctAmersfoort Schothorst 13:48Partial coverage0 min+1 min
Fri 30 OctAmersfoort Schothorst 13:47Partial coverage0 min—
Thu 29 OctAmersfoort Schothorst 13:47No data—
Wed 28 OctAmersfoort Schothorst 13:55No data—
Tue 27 OctAmersfoort Schothorst 13:47Partial coverage0 min—
Mon 26 OctAmersfoort Schothorst 13:49No data—
Sun 25 OctAmersfoort Schothorst 13:47No data—
Sat 24 OctAmersfoort Schothorst 13:48Partial coverage+1 min+1 min
Fri 23 OctAmersfoort Schothorst 13:48Partial coverage0 min—
Thu 22 OctAmersfoort Schothorst 13:52No data—
Wed 21 OctAmersfoort Schothorst 13:48No data—
Tue 20 OctAmersfoort Schothorst 13:47Partial coverage0 min—
Mon 19 OctAmersfoort Schothorst 13:50Partial coverage0 min—
Sun 18 OctBaarn 13:25+1 min+1 min
Sat 17 OctBaarn 13:25No data—
Fri 16 OctBaarn 13:41No data—
Thu 15 OctBaarn 13:410 min—
Wed 14 OctBaarn 13:410 min—
Tue 13 OctBaarn 13:410 min—
Mon 12 OctBaarn 13:410 min—
Sun 11 OctAmersfoort Schothorst 13:47Partial coverage0 min—
Sat 10 OctAmersfoort Schothorst 13:49Partial coverage+2 min+2 min
Fri 9 OctAmersfoort Schothorst 13:47Partial coverage0 min—
Thu 8 OctAmersfoort Schothorst 13:48Partial coverage+1 min—
Wed 7 OctAmersfoort Schothorst 13:51Partial coverage+3 min+5 min
Tue 6 OctAmersfoort Schothorst 13:47Partial coverage0 min—
Mon 5 OctAmersfoort Schothorst 13:460 min—