Train NS 1542 Amersfoort Centraal – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 12:54 from Amersfoort Centraal · Sun 8 Nov

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 17
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
12:54on time on time
13:05 / 13:09≈ on time ≈ on time
13:29on time +1 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
Sat 7 NovHilversum 13:29Partial coverage0 min—
Fri 6 NovHilversum 13:29No data—
Thu 5 NovHilversum 13:52No data—
Wed 4 NovHilversum 13:290 min—
Tue 3 NovHilversum 13:29No data—
Mon 2 NovHilversum 13:29No data—
Sun 1 NovAmersfoort Centraal 13:33+2 min+2 min
Sat 31 OctHilversum 13:33Partial coverage+1 min+1 min
Fri 30 OctHilversum 13:23No data—
Thu 29 OctHilversum 13:310 min—
Wed 28 OctHilversum 13:310 min—
Tue 27 OctHilversum 13:31No data—
Mon 26 OctHilversum 13:24No data—
Mon 19 OctHilversum 13:300 min—
Sun 18 OctAmersfoort Centraal 13:060 min—
Sat 17 OctAmersfoort Centraal 13:25No data—
Fri 16 OctHilversum 13:310 min—
Thu 15 OctHilversum 13:31No data—
Wed 14 OctHilversum 13:300 min—
Tue 13 OctHilversum 13:33No data—
Mon 12 OctHilversum 13:31No data—
Sun 11 OctHilversum 13:30Partial coverage0 min—
Sat 10 OctHilversum 13:30Partial coverage+1 min—
Fri 9 OctHilversum 13:33+1 min+1 min
Thu 8 OctHilversum 13:300 min—
Wed 7 OctHilversum 13:310 min—
Tue 6 OctHilversum 13:300 min—
Mon 5 OctHilversum 13:310 min+1 min
Fri 2 OctHilversum 13:23No data—
Thu 1 OctHilversum 13:23No data—