Train NS 1561 Amsterdam Centraal – Deventer

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

It has not run yet today

Last recorded run: Thursday 19 November +4 min

Next service: today 17:00 from Amsterdam Centraal · Fri 20 Nov

Next departure 17:00 today · Amsterdam Centraal
On-time · 30 days
68%
15/22 runs under 3 min
RT coverage: 12 full · 10 partial · 3 no data
On-time · 90 days
76%
26/34 runs under 3 min
RT coverage: 20 full · 14 partial · 40 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: +7 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 12 Nov Max en route +16 min · last fix heading to Apeldoorn +16 min
  • Sat 14 Nov Max en route +10 min · last fix heading to Hilversum +10 min
  • Sun 15 Nov Max en route +8 min · last fix heading to Hilversum +7 min
  • Tue 17 Nov Max en route +9 min · last fix heading to Apeldoorn +7 min
  • Sun 8 Nov Max en route +6 min · last fix heading to Hilversum +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 26
  • 3–10 min 18% · 6
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 80% T n=5
  • 83% W n=6
  • 50% T n=4
  • 100% F n=4
  • 75% S n=4
  • 40% S n=5

Stops and timetable

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

Last 90 days, 34 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
17:00on time on time
17:20 / 17:22≈ on time ≈ +2 min
17:33 / 17:36≈ on time ≈ +3 min
18:00 / 18:02≈ on time ≈ +5 min
18:12on time +6 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
Thu 19 NovApeldoorn 18:19Partial coverage+4 min+6 min
Wed 18 NovApeldoorn 18:18+5 min+6 min
Tue 17 NovApeldoorn 18:19Partial coverage+7 min+9 min
Mon 16 NovApeldoorn 18:15Partial coverage0 min—
Sun 15 NovHilversum 17:49+7 min+8 min
Sat 14 NovHilversum 17:49+10 min+10 min
Fri 13 NovApeldoorn 18:18Partial coverage+2 min+3 min
Thu 12 NovApeldoorn 18:44Partial coverage+16 min+16 min
Wed 11 NovApeldoorn 18:14Partial coverage0 min—
Tue 10 NovApeldoorn 18:14+1 min+1 min
Mon 9 NovApeldoorn 18:14Partial coverage0 min—
Sun 8 NovHilversum 17:45+6 min+6 min
Sat 7 NovHilversum 17:340 min—
Fri 6 NovApeldoorn 18:14Partial coverage0 min—
Thu 5 NovApeldoorn 18:14No data—
Wed 4 NovApeldoorn 18:14Partial coverage0 min—
Tue 3 NovApeldoorn 18:14No data—
Mon 2 NovApeldoorn 18:14No data—
Sun 1 NovHilversum 17:360 min—
Sat 31 OctHilversum 17:360 min—
Fri 30 OctApeldoorn 18:16Partial coverage0 min—
Thu 29 OctApeldoorn 18:530 min—
Wed 28 OctApeldoorn 18:510 min—
Tue 27 OctApeldoorn 18:520 min—
Mon 26 OctApeldoorn 18:590 min—
Mon 19 OctApeldoorn 18:210 min—
Sun 18 OctHilversum 17:350 min—
Sat 17 OctHilversum 17:35No data—
Fri 16 OctHilversum 17:41No data—
Thu 15 OctHilversum 17:39No data—