Train NS 1529 Amsterdam Centraal – Deventer

Amsterdam Centraal 09:00 → Deventer 10:12 Daily 1 h 12 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Apeldoorn at 10:14 0 min

  1. Amsterdam Centraal09:00
  2. Hilversum09:20
  3. Amersfoort Centraal09:33
  4. Apeldoorn10:00
  5. Deventer10:12

Next service: tomorrow 09:00 from Amsterdam Centraal · Thu 12 Nov

Next departure 09:00 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 15 full · 4 partial · 5 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 19 full · 7 partial · 46 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: 0 min

Last 30 days

Arrival delay at Deventer, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 8 Oct Max en route +9 min · last fix heading to Apeldoorn +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
09:00on time on time
09:20 / 09:22≈ on time ≈ on time
09:33 / 09:36≈ on time ≈ on time
10:00 / 10:02≈ on time ≈ on time
10:12on time on time

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 11 NovApeldoorn 10:14Partial coverage0 min—
Tue 10 NovApeldoorn 10:14+2 min+2 min
Mon 9 NovApeldoorn 10:14Partial coverage0 min—
Sun 8 NovHilversum 09:340 min—
Sat 7 NovHilversum 09:340 min+4 min
Fri 6 NovApeldoorn 10:14No data—
Thu 5 NovApeldoorn 10:14No data—
Wed 4 NovApeldoorn 10:14Partial coverage0 min+2 min
Tue 3 NovApeldoorn 10:140 min—
Mon 2 NovApeldoorn 10:29No data—
Sun 1 NovHilversum 09:370 min—
Sat 31 OctHilversum 09:360 min+1 min
Fri 30 OctApeldoorn 10:16Partial coverage0 min—
Thu 29 OctDieren 11:100 min—
Wed 28 OctDieren 10:520 min—
Tue 27 OctDieren 11:020 min—
Mon 26 OctDieren 10:53No data—
Mon 19 OctApeldoorn 10:160 min—
Sun 18 OctHilversum 09:360 min—
Sat 17 OctHilversum 09:350 min—
Fri 16 OctHilversum 09:400 min—
Thu 15 OctHilversum 10:58No data—
Wed 14 OctHilversum 09:400 min—
Tue 13 OctHilversum 09:390 min—
Mon 12 OctHilversum 09:400 min—
Sun 11 OctHilversum 09:38+1 min+2 min
Sat 10 OctHilversum 09:360 min—
Fri 9 OctApeldoorn 10:17Partial coverage0 min+1 min
Thu 8 OctApeldoorn 10:24Partial coverage+9 min+9 min
Wed 7 OctApeldoorn 10:18Partial coverage0 min—