Train NS 1557 Amsterdam Centraal – Deventer

Amsterdam Centraal 16:03 → Deventer 17:19 Mon, Tue, Wed, Thu, Fri 1 h 16 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 11 November +6 min

Next service: today 16:03 from Amsterdam Centraal · Thu 12 Nov

Next departure 16:03 today · Amsterdam Centraal
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 12 full · 3 partial · 4 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 17 full · 5 partial · 42 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Wed 11 Nov Max en route +6 min · last fix heading to Apeldoorn +6 min
  • Mon 9 Nov Max en route +5 min · last fix heading to Apeldoorn +4 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Apeldoorn +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 19
  • 3–10 min 14% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 67% T n=3
  • 80% W n=5
  • 100% T n=3
  • 100% F n=3
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 22 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:03on time on time
16:23 / 16:26≈ on time ≈ +1 min
16:37 / 16:44≈ on time ≈ +1 min
17:08 / 17:09≈ on time ≈ +2 min
17:19on 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
Wed 11 NovApeldoorn 17:33Partial coverage+6 min+6 min
Tue 10 NovApeldoorn 17:24Partial coverage+3 min+3 min
Mon 9 NovApeldoorn 17:29+4 min+5 min
Fri 6 NovApeldoorn 17:24+1 min—
Thu 5 NovApeldoorn 17:240 min—
Wed 4 NovApeldoorn 17:23Partial coverage0 min—
Tue 3 NovApeldoorn 17:23No data—
Mon 2 NovApeldoorn 17:230 min—
Fri 30 OctApeldoorn 17:240 min—
Thu 29 OctDieren 17:570 min—
Wed 28 OctDieren 17:520 min—
Tue 27 OctDieren 18:08No data—
Mon 26 OctDieren 17:54+2 min+2 min
Mon 19 OctApeldoorn 17:230 min—
Sun 18 OctHilversum 16:370 min+1 min
Sat 17 OctHilversum 16:350 min—
Fri 16 OctHilversum 16:40No data—
Thu 15 OctHilversum 16:39No data—
Wed 14 OctHilversum 16:520 min—
Tue 13 OctHilversum 16:400 min—
Mon 12 OctHilversum 16:440 min—
Fri 9 OctApeldoorn 17:23+1 min+1 min
Thu 8 OctAmersfoort Centraal 23:260 min—
Wed 7 OctApeldoorn 17:23Partial coverage0 min—
Tue 6 OctApeldoorn 17:23Partial coverage0 min—
Mon 5 OctHilversum 16:370 min—
Fri 2 OctApeldoorn 17:23No data—
Thu 1 OctApeldoorn 17:23No data—
Wed 30 SeptApeldoorn 17:23No data—
Tue 29 SeptApeldoorn 17:23No data—