Train NS 1581 Amsterdam Centraal – Amersfoort Centraal

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

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

Next service: today 22:00 from Amsterdam Centraal · Thu 19 Nov

Next departure 22:00 today · Amsterdam Centraal
On-time · 30 days
76%
13/17 runs under 3 min
RT coverage: 14 full · 3 partial · 5 no data
On-time · 90 days
73%
22/30 runs under 3 min
RT coverage: 26 full · 4 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Sun 11 Oct Max en route +48 min · last fix heading to Hilversum +48 min
  • Thu 12 Nov Max en route +13 min · last fix heading to — +12 min
  • Tue 17 Nov Max en route +10 min · last fix heading to — +10 min
  • Fri 9 Oct Max en route +5 min · last fix heading to — +4 min
  • Sun 8 Nov Max en route +5 min · last fix heading to Hilversum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 73% · 22
  • 3–10 min 20% · 6
  • 10–30 min 3% · 1
  • 30+ min 3% · 1

On-time by weekday

  • 83% M n=6
  • 50% T n=2
  • 80% W n=5
  • 33% T n=3
  • 80% F n=5
  • 100% S n=4
  • 60% S n=5

Stops and timetable

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

Last 90 days, 30 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
22:00on time on time
22:20 / 22:22≈ on time ≈ +2 min
22:34on time +4 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 18 Nov— 22:38+1 min+1 min
Tue 17 Nov— 22:54+10 min+10 min
Mon 16 Nov— 22:340 min—
Sun 15 NovHilversum 22:34Partial coverage0 min—
Sat 14 NovHilversum 22:340 min+2 min
Fri 13 Nov— 22:340 min—
Thu 12 Nov— 22:59+12 min+13 min
Wed 11 Nov— 22:340 min—
Mon 9 Nov— 22:340 min—
Sun 8 NovHilversum 22:42Partial coverage+4 min+5 min
Sat 7 NovHilversum 22:340 min—
Fri 6 Nov— 22:340 min+1 min
Thu 5 Nov— 22:38No data—
Wed 4 Nov— 22:34+3 min+3 min
Mon 2 Nov— 22:370 min+3 min
Sun 1 NovHilversum 22:34Partial coverage0 min—
Sat 31 OctHilversum 22:36No data—
Fri 30 Oct— 22:350 min—
Thu 29 Oct— 23:520 min—
Wed 28 Oct— 23:51No data—
Tue 27 Oct— 23:52No data—
Mon 26 Oct— 23:51No data—
Mon 19 Oct— 22:380 min—
Sun 18 OctHilversum 22:350 min—
Sat 17 OctHilversum 22:350 min—
Fri 16 Oct— 22:380 min—
Thu 15 Oct— 22:39No data—
Wed 14 Oct— 22:440 min—
Tue 13 Oct— 22:37No data—
Mon 12 Oct— 22:390 min—