Train NS 5893 Amsterdam Centraal – Amersfoort Centraal

Amsterdam Centraal 01:12 → Amersfoort Centraal 01:58 Fri, Sat 0 h 46 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 01:50

Heading to Amersfoort Centraal 0 min

Estimated arrival at Amersfoort Centraal 01:58 · 31 km/h

  1. Amsterdam Centraal01:12
  2. Amsterdam Science Park01:21
  3. Diemen01:23
  4. Naarden-Bussum01:36
  5. Hilversum Media Park01:43
  6. Hilversum01:45
  7. Amersfoort Centraal01:58

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 7 runs arrived on time.

On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 7 full · 0 partial · 0 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 7 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 7 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 10Today
01:12on time on time
01:18≈ on time ≈ on time
01:21≈ on time ≈ on time
01:23≈ on time ≈ on time
01:29 / 01:30≈ on time ≈ on time
01:36≈ on time ≈ on time
01:39≈ on time ≈ on time
01:43≈ on time ≈ on time
01:45 / 01:46≈ on time ≈ on time
01:52≈ on time ≈ on time
01:58on time on time

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
Sat 7 Nov— 01:490 min—
Sun 25 Oct— 02:000 min—
Sat 24 Oct— 02:040 min—
Sun 18 OctHilversum 01:530 min—
Sat 17 Oct— 02:050 min—
Sun 11 Oct— 02:000 min—
Sat 10 Oct— 01:590 min—