Train NS 1573 Amsterdam Centraal – Amersfoort Centraal

Amsterdam Centraal 20:00 → Amersfoort Centraal 20:34 Daily 0 h 34 min · 3 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 20:00 from Amsterdam Centraal · Sat 7 Nov

Next departure 20:00 today · Amsterdam Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 14 full · 3 partial · 5 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 18 full · 3 partial · 12 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +1 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

Worst days

  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 67% T n=3
  • 100% W n=3
  • 100% T n=3
  • 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 (3 stops).

Last 90 days, 21 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:00on time on time
20:20 / 20:22≈ on time ≈ +2 min
20:34on time +3 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 Nov— 20:340 min—
Thu 5 Nov— 20:350 min—
Wed 4 Nov— 20:39+3 min+3 min
Tue 3 Nov— 20:370 min—
Sun 1 NovHilversum 20:34No data—
Sat 31 OctHilversum 20:38Partial coverage+1 min+3 min
Fri 30 Oct— 21:020 min—
Thu 29 Oct— 21:510 min—
Wed 28 Oct— 22:040 min—
Tue 27 Oct— 21:540 min—
Mon 26 Oct— 21:560 min—
Mon 19 Oct— 20:520 min—
Sun 18 OctHilversum 20:350 min—
Sat 17 OctHilversum 20:360 min—
Fri 16 Oct— 20:38No data—
Thu 15 Oct— 20:46No data—
Wed 14 Oct— 20:44No data—
Tue 13 Oct— 20:38No data—
Mon 12 Oct— 20:370 min—
Sun 11 OctHilversum 20:36Partial coverage0 min+2 min
Sat 10 OctHilversum 20:36Partial coverage0 min—
Fri 9 Oct— 20:38+1 min+1 min
Thu 8 Oct— 20:50+1 min—
Wed 7 Oct— 20:360 min—
Tue 6 Oct— 20:43+4 min+4 min
Mon 5 Oct— 20:42+3 min+3 min
Sun 20 SeptAmersfoort Centraal 20:48No data—
Sat 19 SeptAmersfoort Centraal 20:50No data—
Sun 6 SeptHilversum 20:36No data—
Sat 5 SeptHilversum 20:36No data—