Train NS 1572 Amersfoort Centraal – Amsterdam Centraal

Amersfoort Centraal 20:24 → Amsterdam Centraal 20:59 Daily 0 h 35 min · 3 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +7 min

Next service: today 20:24 from Amersfoort Centraal · Mon 16 Nov

Next departure 20:24 today · Amersfoort Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 15 full · 3 partial · 5 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 23 full · 4 partial · 16 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

Worst days

  • Sun 15 Nov Max en route +7 min · last fix heading to Hilversum +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=3
  • 100% T n=3
  • 100% F n=5
  • 100% S n=4
  • 80% S n=5

Stops and timetable

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

Last 90 days, 27 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
20:24on time on time
20:35 / 20:39≈ on time ≈ on time
20:59on 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
Sun 15 NovHilversum 21:04Partial coverage+7 min+7 min
Sat 14 NovHilversum 20:59+1 min+1 min
Fri 13 Nov— 21:04+1 min+2 min
Thu 12 Nov— 20:590 min—
Wed 11 Nov— 20:590 min—
Tue 10 Nov— 20:340 min—
Mon 9 Nov— 20:590 min—
Sun 8 NovHilversum 20:59Partial coverage0 min—
Sat 7 NovHilversum 20:590 min—
Fri 6 Nov— 20:590 min—
Thu 5 Nov— 21:00No data—
Wed 4 Nov— 21:03+2 min+2 min
Tue 3 Nov— 21:02No data—
Mon 2 Nov— 20:59No data—
Sun 1 NovHilversum 20:53Partial coverage0 min—
Sat 31 OctHilversum 21:000 min—
Fri 30 Oct— 21:030 min—
Thu 29 Oct— 21:000 min—
Wed 28 Oct— 21:00No data—
Tue 27 Oct— 21:01No data—
Mon 26 Oct— 21:050 min—
Mon 19 Oct— 21:030 min—
Sun 18 OctAmersfoort Centraal 20:410 min—
Sat 17 OctAmersfoort Centraal 20:37No data—
Fri 16 Oct— 21:00+1 min—
Thu 15 Oct— 21:03No data—
Wed 14 Oct— 21:00No data—
Tue 13 Oct— 21:01No data—
Mon 12 Oct— 21:010 min—
Sun 11 OctHilversum 21:00Partial coverage0 min—