Train NS 1526 Amersfoort Centraal – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Hilversum at 09:29 0 min

  1. Amersfoort Centraal08:54
  2. Hilversum09:05
  3. Amsterdam Centraal09:29

Next service: tomorrow 08:54 from Amersfoort Centraal · Sun 8 Nov

Next departure 08:54 tomorrow · Amersfoort Centraal
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 12 full · 3 partial · 9 no data
On-time · 90 days
78%
14/18 runs under 3 min
RT coverage: 15 full · 3 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Wed 7 Oct Max en route +10 min · last fix heading to Hilversum +10 min
  • Sat 10 Oct Max en route +7 min · last fix heading to Hilversum +7 min
  • Wed 4 Nov Max en route +7 min · last fix heading to Hilversum +7 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Hilversum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 14
  • 3–10 min 22% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 33% W n=3
  • 50% T n=2
  • 100% F n=2
  • 75% 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, 18 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
08:54on time on time
09:05 / 09:09≈ on time ≈ +2 min
09:29on time +5 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 09:29Partial coverage0 min—
Fri 6 NovHilversum 09:23No data—
Thu 5 NovHilversum 09:34No data—
Wed 4 NovHilversum 09:34+7 min+7 min
Tue 3 NovHilversum 09:29No data—
Mon 2 NovHilversum 09:29No data—
Sun 1 NovHilversum 09:310 min—
Sat 31 OctAmersfoort Centraal 09:30Partial coverage0 min—
Fri 30 OctHilversum 09:30No data—
Thu 29 OctHilversum 09:330 min—
Wed 28 OctHilversum 09:350 min—
Tue 27 OctHilversum 09:330 min—
Mon 26 OctHilversum 09:310 min—
Mon 19 OctHilversum 09:300 min—
Sun 18 OctAmersfoort Centraal 09:07+2 min+2 min
Sat 17 OctAmersfoort Centraal 09:050 min—
Fri 16 OctHilversum 09:310 min—
Thu 15 OctHilversum 10:58No data—
Wed 14 OctHilversum 09:43No data—
Tue 13 OctHilversum 09:35No data—
Mon 12 OctHilversum 09:31No data—
Sun 11 OctHilversum 09:30+1 min+1 min
Sat 10 OctHilversum 09:35Partial coverage+7 min+7 min
Fri 9 OctHilversum 09:36+2 min+3 min
Thu 8 OctHilversum 09:37+4 min+4 min
Wed 7 OctHilversum 09:49+10 min+10 min
Tue 6 OctHilversum 09:300 min—
Mon 5 OctHilversum 09:23No data—
Fri 2 OctHilversum 09:24No data—
Thu 1 OctHilversum 09:27No data—