Train NS 1523 Amsterdam Centraal – Deventer

Amsterdam Centraal 07:31 → Deventer 08:44 Mon, Tue, Wed, Thu, Fri, Sat 1 h 13 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 07:31 from Amsterdam Centraal · Fri 6 Nov

Next departure 07:31 today · Amsterdam Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 11 full · 3 partial · 6 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 11 full · 5 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

  • Sat 17 Oct Max en route +4 min · last fix heading to Hilversum +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=4
  • 100% T n=2
  • 100% F n=3
  • 67% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 16 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
07:31on time on time
07:50 / 07:52≈ on time ≈ on time
08:03 / 08:06≈ on time ≈ on time
08:31 / 08:33≈ on time ≈ on time
08:44on 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
Thu 5 NovApeldoorn 08:47No data—
Wed 4 NovApeldoorn 08:47Partial coverage0 min—
Tue 3 NovApeldoorn 08:47No data—
Mon 2 NovApeldoorn 08:47No data—
Sat 31 OctHilversum 08:060 min—
Fri 30 OctApeldoorn 08:470 min—
Thu 29 OctDieren 09:240 min—
Wed 28 OctDieren 09:230 min—
Tue 27 OctDieren 09:230 min—
Mon 26 OctDieren 09:230 min—
Mon 19 OctApeldoorn 08:47Partial coverage0 min—
Sat 17 OctHilversum 08:09+3 min+4 min
Fri 16 OctHilversum 08:100 min—
Thu 15 OctHilversum 08:09No data—
Wed 14 OctHilversum 08:090 min—
Tue 13 OctHilversum 08:10No data—
Mon 12 OctHilversum 08:10No data—
Sat 10 OctHilversum 08:060 min+1 min
Fri 9 OctApeldoorn 08:470 min—
Thu 8 OctApeldoorn 08:47Partial coverage0 min—
Wed 7 OctApeldoorn 08:47Partial coverage0 min—
Tue 6 OctApeldoorn 08:47Partial coverage0 min—
Mon 5 OctApeldoorn 08:47No data—
Fri 2 OctApeldoorn 08:49No data—
Thu 1 OctApeldoorn 08:59No data—
Wed 30 SeptApeldoorn 08:47No data—
Tue 29 SeptApeldoorn 08:47No data—
Mon 28 SeptApeldoorn 08:47No data—
Fri 25 SeptApeldoorn 08:49No data—
Thu 24 SeptApeldoorn 08:47No data—