Train NS 1530 Amersfoort Centraal – Amsterdam Centraal

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

Running now · updated 10:05

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 10:29 · 24 km/h

  1. Amersfoort Centraal09:54
  2. Hilversum10:05
  3. Amsterdam Centraal10:29

Today it is running no worse than usual: typical arrival delay is 0 min; 94% of the last 17 runs arrived on time.

On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 15 full · 2 partial · 7 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 19 full · 2 partial · 48 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

Worst days

  • Sat 17 Oct Max en route +3 min · last fix heading to Amersfoort Centraal +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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