Train NS 5849 Amsterdam Centraal – Amersfoort Vathorst

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

✓ Today’s run finished

Today, last fix heading to Amersfoort Schothorst at 15:18 No data

  1. Amsterdam Centraal14:11
  2. Amsterdam Science Park14:19
  3. Weesp14:27
  4. Bussum Zuid14:38
  5. Hilversum14:44
  6. Amersfoort Schothorst15:03
  7. Amersfoort Vathorst15:07

Next service: tomorrow 14:11 from Amsterdam Centraal · Fri 6 Nov

Next departure 14:11 tomorrow · Amsterdam Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 3 full · 14 partial · 13 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 4 full · 15 partial · 70 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

Worst days

  • Sat 24 Oct Max en route +6 min · last fix heading to Amersfoort Schothorst +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • 67% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 19 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
14:11on time on time
14:16— —
14:19— —
14:22— —
14:27 / 14:29— —
14:35— —
14:38— —
14:42— —
14:44 / 14:45— —
14:51— —
14:58 / 14:59— —
15:03— —
15: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.

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