Train NS 1570 Amersfoort Centraal – Amsterdam Centraal

Amersfoort Centraal 19:54 → Amsterdam Centraal 20:29 Daily 0 h 35 min · 3 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +3 min

Next service: today 19:54 from Amersfoort Centraal · Thu 5 Nov

Next departure 19:54 today · Amersfoort Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 9 full · 4 partial · 8 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 11 full · 4 partial · 15 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 10 Oct Max en route +12 min · last fix heading to Hilversum +12 min
  • Mon 5 Oct Max en route +7 min · last fix heading to — +5 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 7% · 1
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=1
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 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:54on time on time
20:05 / 20:09≈ on time ≈ +1 min
20:29on 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
Wed 4 Nov— 20:34+3 min+3 min
Sun 1 NovHilversum 20:24Partial coverage0 min—
Sat 31 OctHilversum 20:30Partial coverage0 min—
Fri 30 Oct— 20:34No data—
Thu 29 Oct— 20:300 min—
Wed 28 Oct— 20:330 min—
Tue 27 Oct— 20:33No data—
Mon 26 Oct— 20:31No data—
Mon 19 Oct— 20:330 min—
Sun 18 OctAmersfoort Centraal 20:06+1 min—
Sat 17 OctAmersfoort Centraal 20:10No data—
Fri 16 OctAmersfoort Centraal 20:34No data—
Thu 15 Oct— 20:33No data—
Wed 14 Oct— 20:30No data—
Tue 13 Oct— 20:31No data—
Mon 12 Oct— 20:300 min—
Sun 11 OctHilversum 20:30Partial coverage0 min—
Sat 10 OctHilversum 20:46Partial coverage+12 min+12 min
Fri 9 Oct— 20:300 min—
Thu 8 Oct— 20:380 min—
Wed 7 Oct— 20:35+2 min+2 min
Tue 6 Oct— 20:270 min—
Mon 5 Oct— 20:41+5 min+7 min
Sun 20 SeptHilversum 20:25No data—
Sat 19 SeptHilversum 20:25No data—
Sun 6 SeptAmersfoort Centraal 20:08No data—
Sat 5 SeptAmersfoort Centraal 20:08No data—
Sun 23 AugAmsterdam Muiderpoort 20:41No data—
Sat 22 AugAmsterdam Muiderpoort 20:41No data—
Fri 21 AugAmsterdam Muiderpoort 20:40No data—