Train NS 1564 Deventer – Amsterdam Centraal

Deventer 17:48 → Amsterdam Centraal 18:59 Daily 1 h 11 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +6 min

Next service: today 17:48 from Deventer · Tue 17 Nov

Next departure 17:48 today · Deventer
On-time · 30 days
72%
13/18 runs under 3 min
RT coverage: 9 full · 9 partial · 5 no data
On-time · 90 days
78%
21/27 runs under 3 min
RT coverage: 14 full · 13 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

Arrival delay at Amsterdam Centraal, 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 5 Oct Max en route +13 min · last fix heading to Apeldoorn +13 min
  • Mon 9 Nov Max en route +13 min · last fix heading to Apeldoorn +13 min
  • Wed 11 Nov Max en route +7 min · last fix heading to Apeldoorn +7 min
  • Mon 16 Nov Max en route +6 min · last fix heading to Amersfoort Centraal +6 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Apeldoorn +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 21
  • 3–10 min 15% · 4
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 57% M n=7
  • 100% T n=3
  • 67% W n=3
  • 50% T n=2
  • 67% F n=3
  • 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, 27 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:48on time on time
17:58 / 18:00≈ on time ≈ on time
18:24 / 18:26≈ on time ≈ +1 min
18:37 / 18:39≈ on time ≈ +1 min
18:59on 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
Mon 16 NovAmersfoort Centraal 19:05Partial coverage+6 min+6 min
Sun 15 NovHilversum 19:04+2 min+6 min
Sat 14 NovHilversum 18:59+2 min+2 min
Fri 13 NovHilversum 19:04Partial coverage+3 min+3 min
Thu 12 NovApeldoorn 19:07Partial coverage+4 min+4 min
Wed 11 NovApeldoorn 19:04Partial coverage+7 min+7 min
Tue 10 NovApeldoorn 18:14Partial coverage0 min—
Mon 9 NovApeldoorn 19:19Partial coverage+13 min+13 min
Sun 8 NovHilversum 18:590 min—
Sat 7 NovHilversum 18:590 min—
Fri 6 NovHilversum 18:59Partial coverage+1 min—
Thu 5 NovApeldoorn 18:59No data—
Wed 4 NovApeldoorn 19:12No data—
Tue 3 NovApeldoorn 18:59No data—
Mon 2 NovApeldoorn 19:03Partial coverage+2 min+2 min
Sun 1 NovHilversum 18:590 min—
Sat 31 OctAmersfoort Centraal 19:000 min—
Fri 30 OctHilversum 19:05No data—
Thu 29 OctApeldoorn 18:14No data—
Wed 28 OctApeldoorn 19:030 min—
Tue 27 OctApeldoorn 19:020 min—
Mon 26 OctApeldoorn 19:050 min—
Mon 19 OctHilversum 19:01Partial coverage0 min—
Sun 18 OctAmersfoort Centraal 18:420 min—
Sat 17 OctAmersfoort Centraal 18:40No data—
Fri 16 OctHilversum 19:03No data—
Thu 15 OctAmersfoort Centraal 19:05No data—
Wed 14 OctHilversum 19:01No data—
Tue 13 OctHilversum 19:02No data—
Mon 12 OctHilversum 19:000 min—