Train NS 1569 Amsterdam Centraal – Amersfoort Centraal

Amsterdam Centraal 19:03 → Amersfoort Centraal 19:36 Daily 0 h 33 min · 3 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +11 min

Next service: today 19:03 from Amsterdam Centraal · Tue 17 Nov

Next departure 19:03 today · Amsterdam Centraal
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 9 full · 4 partial · 8 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 16 full · 6 partial · 23 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 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 +23 min · last fix heading to — +23 min
  • Mon 16 Nov Max en route +11 min · last fix heading to — +11 min
  • Wed 11 Nov Max en route +4 min · last fix heading to — +4 min

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 86% · 19
  • 3–10 min 5% · 1
  • 10–30 min 9% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 100% T n=1
  • 67% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • 100% S n=3

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
19:03on time on time
19:22 / 19:24≈ on time ≈ +5 min
19:36on time +7 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
Mon 16 Nov— 19:49+11 min+11 min
Sun 15 NovHilversum 19:42Partial coverage+2 min+3 min
Sat 14 NovHilversum 19:38Partial coverage0 min—
Fri 13 Nov— 19:370 min—
Thu 12 Nov— 19:390 min—
Wed 11 Nov— 19:44+4 min+4 min
Mon 9 Nov— 19:380 min—
Sun 8 NovHilversum 19:38No data—
Sat 7 NovHilversum 19:39Partial coverage+1 min+1 min
Fri 6 Nov— 19:37+1 min+1 min
Thu 5 Nov— 19:39No data—
Wed 4 Nov— 19:38No data—
Mon 2 Nov— 19:38No data—
Sun 1 NovHilversum 19:38No data—
Sat 31 OctHilversum 19:38Partial coverage0 min—
Fri 30 Oct— 19:41No data—
Thu 29 Oct— 20:510 min—
Wed 28 Oct— 20:560 min—
Tue 27 Oct— 20:52No data—
Mon 26 Oct— 20:58No data—
Mon 19 Oct— 19:370 min—
Sun 18 OctHilversum 19:350 min—
Sat 17 OctHilversum 19:35No data—
Fri 16 OctHilversum 19:39No data—
Thu 15 Oct— 19:40No data—
Wed 14 OctHilversum 19:42No data—
Tue 13 Oct— 19:38No data—
Mon 12 Oct— 19:400 min—
Sun 11 OctHilversum 19:38Partial coverage0 min—
Sat 10 OctHilversum 19:39Partial coverage0 min—