Train NS 1587 Amsterdam Centraal – Amersfoort Centraal

Amsterdam Centraal 23:30 → Amersfoort Centraal 00: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 23:30 from Amsterdam Centraal · Fri 6 Nov

Next departure 23:30 today · Amsterdam Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 17 full · 2 partial · 2 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 20 full · 2 partial · 6 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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 2 Nov Max en route +3 min · last fix heading to — +3 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 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 50% T n=2
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 100% S n=3
  • 100% S n=4

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
23:30on time on time
23:50 / 23:52≈ on time ≈ +1 min
00:04on time +2 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— 00:04No data—
Wed 4 Nov— 00:040 min—
Mon 2 Nov— 00:08+3 min+3 min
Sun 1 NovHilversum 00:04Partial coverage0 min+2 min
Sat 31 Oct— 00:100 min—
Thu 29 Oct— 01:000 min+5 min
Wed 28 Oct— 01:230 min—
Tue 27 Oct— 01:220 min—
Mon 26 OctHilversum 01:550 min—
Sun 25 OctAmsterdam Centraal 00:120 min—
Sun 18 OctHilversum 00:05Partial coverage0 min—
Sat 17 OctHilversum 00:060 min—
Fri 16 Oct— 00:080 min—
Thu 15 Oct— 00:100 min—
Wed 14 Oct— 00:080 min—
Tue 13 Oct— 00:09No data—
Mon 12 Oct— 00:080 min—
Sun 11 OctHilversum 00:060 min—
Sat 10 Oct— 00:06+1 min+1 min
Fri 9 Oct— 00:050 min—
Thu 8 Oct— 00:05+1 min+1 min
Wed 7 Oct— 00:10+2 min+3 min
Tue 6 Oct— 00:12+4 min+4 min
Mon 5 Oct— 00:050 min—
Sun 20 SeptAmersfoort Centraal 00:19No data—
Sun 6 SeptHilversum 00:06No data—
Sun 23 AugHilversum 00:06No data—
Sat 22 AugHilversum 00:06No data—