Train NS 1559 Amsterdam Centraal – Deventer

Amsterdam Centraal 16:31 → Deventer 17:44 Daily 1 h 13 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Apeldoorn at 18:03 +9 min

  1. Amsterdam Centraal16:31
  2. Hilversum16:50
  3. Amersfoort Centraal17:03
  4. Apeldoorn17:32
  5. Deventer17:44

Next service: tomorrow 16:31 from Amsterdam Centraal · Wed 18 Nov

Next departure 16:31 tomorrow · Amsterdam Centraal
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 11 full · 8 partial · 5 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 17 full · 11 partial · 47 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: +3 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 9 Nov Max en route +11 min · last fix heading to Apeldoorn +10 min
  • Tue 17 Nov Max en route +12 min · last fix heading to Apeldoorn +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
16:31on time on time
16:50 / 16:52≈ on time ≈ on time
17:03 / 17:06≈ on time ≈ +1 min
17:32 / 17:34≈ on time ≈ +1 min
17:44on 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
Tue 17 NovApeldoorn 18:03Partial coverage+9 min+12 min
Mon 16 NovApeldoorn 17:48Partial coverage+2 min+2 min
Sun 15 NovHilversum 17:08+1 min+2 min
Sat 14 NovHilversum 17:08+1 min+3 min
Fri 13 NovApeldoorn 17:480 min—
Thu 12 NovApeldoorn 17:48Partial coverage+1 min+1 min
Wed 11 NovApeldoorn 17:48Partial coverage0 min—
Tue 10 NovApeldoorn 17:48Partial coverage0 min—
Mon 9 NovApeldoorn 18:04Partial coverage+10 min+11 min
Sun 8 NovHilversum 17:080 min+2 min
Sat 7 NovHilversum 17:040 min—
Fri 6 NovApeldoorn 17:480 min—
Thu 5 NovApeldoorn 17:48No data—
Wed 4 NovApeldoorn 17:48No data—
Tue 3 NovApeldoorn 17:48Partial coverage0 min—
Mon 2 NovApeldoorn 17:48No data—
Sun 1 NovHilversum 17:060 min+2 min
Sat 31 OctHilversum 17:060 min—
Fri 30 OctApeldoorn 17:500 min—
Thu 29 OctApeldoorn 18:220 min—
Wed 28 OctDieren 18:23No data—
Tue 27 OctApeldoorn 18:34No data—
Mon 26 OctDieren 18:30+2 min+2 min
Mon 19 OctApeldoorn 17:48Partial coverage0 min—
Sun 18 OctHilversum 17:050 min—
Sat 17 OctHilversum 17:05No data—
Fri 16 OctHilversum 17:10No data—
Thu 15 OctHilversum 17:10No data—
Wed 14 OctHilversum 17:12No data—
Tue 13 OctHilversum 17:10No data—