Train NS 1519 Amsterdam Centraal – Deventer

Amsterdam Centraal 06:31 → Deventer 07:42 Mon, Tue, Wed, Thu, Fri 1 h 11 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 06:31 from Amsterdam Centraal · Mon 9 Nov

Next departure 06:31 tomorrow · Amsterdam Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 11 full · 4 partial · 1 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 11 full · 8 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Mon 12 Oct Max en route +4 min · last fix heading to Hilversum +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
06:31on time on time
06:50 / 06:52≈ on time ≈ +1 min
07:03 / 07:06≈ on time ≈ +1 min
07:30 / 07:32≈ on time ≈ +2 min
07:42on time +2 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
Fri 6 NovApeldoorn 07:44No data—
Thu 5 NovApeldoorn 07:59Partial coverage0 min—
Wed 4 NovApeldoorn 07:44Partial coverage0 min—
Tue 3 NovApeldoorn 07:44Partial coverage+1 min+1 min
Mon 2 NovApeldoorn 07:440 min—
Fri 30 OctApeldoorn 07:46Partial coverage0 min—
Thu 29 OctDieren 08:230 min—
Wed 28 OctDieren 08:240 min—
Tue 27 OctDieren 08:250 min—
Mon 26 OctDieren 08:370 min—
Mon 19 OctApeldoorn 07:460 min—
Fri 16 OctHilversum 07:100 min—
Thu 15 OctHilversum 07:100 min—
Wed 14 OctHilversum 07:10+1 min+1 min
Tue 13 OctHilversum 07:13+2 min+2 min
Mon 12 OctHilversum 07:13+4 min+4 min
Fri 9 OctApeldoorn 07:46Partial coverage0 min—
Thu 8 OctApeldoorn 07:46Partial coverage0 min—
Wed 7 OctApeldoorn 07:48Partial coverage+2 min+2 min
Tue 6 OctApeldoorn 07:46Partial coverage0 min—
Mon 5 OctApeldoorn 07:47No data—
Fri 2 OctApeldoorn 07:46No data—
Thu 1 OctApeldoorn 07:46No data—
Wed 30 SeptApeldoorn 07:46No data—
Tue 29 SeptApeldoorn 07:52No data—
Mon 28 SeptApeldoorn 07:46No data—
Fri 25 SeptApeldoorn 07:46No data—
Thu 24 SeptApeldoorn 07:46No data—
Wed 23 SeptApeldoorn 07:46No data—
Tue 22 SeptApeldoorn 07:46No data—