Train NS 1516 Amersfoort Centraal – Amsterdam Centraal

Amersfoort Centraal 06:24 → Amsterdam Centraal 06:59 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 3 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:24 from Amersfoort Centraal · Mon 9 Nov

Next departure 06:24 Monday · Amersfoort Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 11 full · 8 partial · 2 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 12 full · 10 partial · 38 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
06:24on time on time
06:35 / 06:39≈ on time ≈ +1 min
06:59on time +2 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
Fri 6 NovAmersfoort Centraal 07:23No data—
Thu 5 NovHilversum 07:04No data—
Wed 4 NovHilversum 06:59Partial coverage+1 min+2 min
Tue 3 NovHilversum 06:59Partial coverage+1 min+1 min
Mon 2 NovHilversum 06:590 min—
Fri 30 OctHilversum 07:03+2 min+2 min
Thu 29 OctAmersfoort Centraal 07:00+1 min+1 min
Wed 28 OctHilversum 07:01Partial coverage+1 min+2 min
Tue 27 OctHilversum 07:01Partial coverage0 min—
Mon 26 OctHilversum 07:00Partial coverage0 min—
Fri 23 OctHilversum 06:58+2 min+2 min
Thu 22 OctHilversum 07:00Partial coverage0 min—
Wed 21 OctHilversum 07:00Partial coverage0 min—
Tue 20 OctHilversum 07:000 min—
Mon 19 OctHilversum 07:00Partial coverage0 min—
Fri 16 OctHilversum 07:000 min—
Thu 15 OctHilversum 07:000 min—
Wed 14 OctHilversum 07:05+2 min+3 min
Tue 13 OctHilversum 07:000 min—
Mon 12 OctHilversum 07:000 min—
Fri 9 OctHilversum 07:05+3 min+3 min
Thu 8 OctHilversum 07:03Partial coverage+2 min+3 min
Wed 7 OctHilversum 07:03Partial coverage+2 min+2 min
Tue 6 OctHilversum 07:01+1 min+2 min
Mon 5 OctHilversum 06:54No data—
Fri 2 OctHilversum 06:53No data—
Thu 1 OctHilversum 06:53No data—
Wed 30 SeptHilversum 06:53No data—
Tue 29 SeptHilversum 06:53No data—
Mon 28 SeptHilversum 06:53No data—