Train NS 1566 Deventer – Amsterdam Centraal

Deventer 18:18 → Amsterdam Centraal 19:29 Daily 1 h 11 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 18:18 from Deventer · Wed 18 Nov

Next departure 18:18 today · Deventer
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 10 full · 6 partial · 6 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 18 full · 8 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Thu 12 Nov Max en route +15 min · last fix heading to Deventer +15 min
  • Mon 16 Nov Max en route +8 min · last fix heading to Deventer +8 min
  • Mon 5 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 23
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 100% T n=2
  • 100% W n=2
  • 67% 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, 26 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
18:18on time on time
18:28 / 18:30≈ on time ≈ on time
18:54 / 18:56≈ on time ≈ +1 min
19:07 / 19:09≈ on time ≈ +2 min
19:29+1 min +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
Tue 17 NovDeventer 19:33Partial coverage+1 min+1 min
Mon 16 NovDeventer 19:39Partial coverage+8 min+8 min
Sun 15 NovHilversum 19:33+2 min+2 min
Sat 14 NovHilversum 19:290 min—
Fri 13 NovAmersfoort Centraal 19:29Partial coverage+1 min—
Thu 12 NovDeventer 19:48Partial coverage+15 min+15 min
Wed 11 Nov— 19:290 min—
Tue 10 NovDeventer 18:32No data—
Mon 9 Nov— 19:290 min—
Sun 8 NovHilversum 19:290 min—
Sat 7 NovHilversum 19:29+2 min+2 min
Fri 6 NovApeldoorn 19:29Partial coverage+1 min—
Thu 5 Nov— 19:29No data—
Wed 4 Nov— 19:34No data—
Mon 2 NovAmersfoort Centraal 19:29Partial coverage0 min—
Sun 1 NovHilversum 19:290 min—
Sat 31 OctAmersfoort Centraal 19:31+2 min+2 min
Fri 30 OctApeldoorn 19:40No data—
Thu 29 OctArnhem Centraal 19:31+2 min+2 min
Wed 28 OctArnhem Centraal 19:35No data—
Tue 27 OctArnhem Centraal 19:49No data—
Mon 26 OctArnhem Centraal 19:57+2 min+2 min
Mon 19 OctApeldoorn 19:30Partial coverage0 min—
Sun 18 OctAmersfoort Centraal 19:050 min—
Sat 17 OctAmersfoort Centraal 19:07No data—
Fri 16 OctHilversum 19:230 min—
Thu 15 Oct— 19:33No data—
Wed 14 OctHilversum 19:31No data—
Tue 13 Oct— 19:31No data—
Mon 12 Oct— 19:31No data—