Train NS 1571 Amsterdam Centraal – Amersfoort Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 19:30 from Amsterdam Centraal · Fri 6 Nov

Next departure 19:30 today · Amsterdam Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 11 full · 2 partial · 10 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 13 full · 2 partial · 19 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: +3 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

  • Mon 5 Oct Max en route +7 min · last fix heading to — +7 min
  • Sat 10 Oct Max en route +6 min · last fix heading to Hilversum +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 13
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
19:30on time on time
19:50 / 19:52≈ on time ≈ +2 min
20:04on 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
Thu 5 Nov— 20:04No data—
Wed 4 Nov— 20:09+3 min+3 min
Tue 3 Nov— 20:04No data—
Mon 2 Nov— 20:04No data—
Sun 1 NovAmsterdam Centraal 20:040 min—
Sat 31 OctHilversum 20:08Partial coverage+2 min+3 min
Fri 30 Oct— 20:050 min—
Thu 29 Oct— 21:21+1 min+2 min
Wed 28 Oct— 21:230 min—
Tue 27 Oct— 21:22No data—
Mon 26 Oct— 21:32No data—
Mon 19 Oct— 20:360 min—
Sun 18 OctHilversum 20:06+3 min+3 min
Sat 17 OctHilversum 20:05No data—
Fri 16 OctHilversum 20:09No data—
Thu 15 Oct— 20:08No data—
Wed 14 OctAmsterdam Centraal 20:09No data—
Tue 13 Oct— 20:19No data—
Mon 12 Oct— 20:080 min—
Sun 11 OctHilversum 20:060 min—
Sat 10 OctHilversum 20:12Partial coverage+3 min+6 min
Fri 9 Oct— 20:060 min—
Thu 8 Oct— 20:530 min+1 min
Tue 6 Oct— 20:050 min—
Mon 5 Oct— 20:11+7 min+7 min
Sun 20 SeptAmersfoort Centraal 20:18No data—
Sat 19 SeptAmersfoort Centraal 20:20No data—
Sun 6 SeptHilversum 20:07No data—
Sat 5 SeptHilversum 20:06No data—
Fri 28 AugAmsterdam Centraal 19:44No data—