Train NS 1562 Deventer – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

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

Next departure 17:19 today · Deventer
On-time · 30 days
75%
12/16 runs under 3 min
RT coverage: 7 full · 9 partial · 7 no data
On-time · 90 days
78%
21/27 runs under 3 min
RT coverage: 13 full · 14 partial · 47 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Sun 15 Nov Max en route +17 min · last fix heading to Hilversum +17 min
  • Tue 10 Nov Max en route +8 min · last fix heading to Amersfoort Centraal +8 min
  • Wed 7 Oct Max en route +8 min · last fix heading to Hilversum +7 min
  • Mon 9 Nov Max en route +5 min · last fix heading to Hilversum +5 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Hilversum +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 19% · 5
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 67% T n=3
  • 50% W n=2
  • 0% T n=2
  • 100% F n=4
  • 100% S n=5
  • 80% 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:19on time on time
17:29 / 17:30≈ on time ≈ on time
17:54 / 17:56≈ on time ≈ +1 min
18:07 / 18:09≈ on time ≈ +1 min
18:29on 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
Tue 17 NovHilversum 18:29Partial coverage+1 min+2 min
Mon 16 NovHilversum 18:30Partial coverage+1 min+2 min
Sun 15 NovHilversum 18:44+17 min+17 min
Sat 14 NovHilversum 18:290 min—
Fri 13 NovHilversum 18:29Partial coverage+1 min—
Thu 12 NovHilversum 18:34Partial coverage+4 min+4 min
Wed 11 NovHilversum 18:34Partial coverage+3 min+3 min
Tue 10 NovAmersfoort Centraal 18:24Partial coverage+8 min+8 min
Mon 9 NovHilversum 18:34Partial coverage+5 min+5 min
Sun 8 NovHilversum 18:300 min—
Sat 7 NovHilversum 18:29+1 min+1 min
Fri 6 NovHilversum 18:29Partial coverage0 min—
Thu 5 NovHilversum 18:34No data—
Wed 4 NovHilversum 18:34No data—
Tue 3 NovHilversum 18:29No data—
Mon 2 NovHilversum 18:29No data—
Sun 1 NovHilversum 18:290 min—
Sat 31 OctHilversum 18:35+2 min+3 min
Fri 30 OctHilversum 18:30Partial coverage0 min—
Thu 29 OctAmersfoort Centraal 18:31No data—
Wed 28 OctHilversum 18:30No data—
Tue 27 OctAmersfoort Centraal 18:31No data—
Mon 26 OctHilversum 18:350 min—
Mon 19 OctHilversum 18:31Partial coverage0 min—
Sun 18 OctAmersfoort Centraal 18:050 min—
Sat 17 OctAmersfoort Centraal 18:060 min—
Fri 16 OctHilversum 18:30No data—
Thu 15 OctHilversum 18:30No data—
Wed 14 OctHilversum 18:31No data—
Tue 13 OctHilversum 18:30No data—