Train NS 1553 Amsterdam Centraal – Deventer

Amsterdam Centraal 14:59 → Deventer 16:12 Daily 1 h 13 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 14:59 from Amsterdam Centraal · Tue 17 Nov

Next departure 14:59 today · Amsterdam Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 8 full · 9 partial · 6 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 14 full · 13 partial · 47 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Fri 13 Nov Max en route +13 min · last fix heading to Apeldoorn +12 min
  • Sat 10 Oct 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 93% · 25
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=3
  • 100% T n=4
  • 75% F n=4
  • 75% 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
14:59on time on time
15:20 / 15:22≈ on time ≈ on time
15:33 / 15:36≈ on time ≈ +1 min
16:00 / 16:02≈ on time ≈ +1 min
16:12on time +1 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 NovApeldoorn 16:18Partial coverage+1 min+3 min
Sun 15 NovHilversum 15:350 min—
Sat 14 NovHilversum 15:340 min—
Fri 13 NovApeldoorn 16:34Partial coverage+12 min+13 min
Thu 12 NovApeldoorn 16:14Partial coverage0 min+1 min
Wed 11 NovApeldoorn 16:14Partial coverage0 min—
Tue 10 NovApeldoorn 16:14Partial coverage0 min—
Mon 9 NovApeldoorn 16:14Partial coverage0 min—
Sun 8 NovHilversum 15:340 min—
Sat 7 NovHilversum 15:340 min—
Fri 6 NovApeldoorn 16:14No data—
Thu 5 NovApeldoorn 16:15Partial coverage0 min—
Wed 4 NovApeldoorn 16:14Partial coverage0 min—
Tue 3 NovApeldoorn 16:14No data—
Mon 2 NovApeldoorn 16:18No data—
Sun 1 NovHilversum 15:38+1 min+1 min
Sat 31 OctHilversum 15:360 min—
Fri 30 OctApeldoorn 16:16Partial coverage0 min—
Thu 29 OctDieren 16:520 min—
Wed 28 OctDieren 16:52No data—
Tue 27 OctDieren 16:54No data—
Mon 26 OctDieren 16:53No data—
Mon 19 OctApeldoorn 16:170 min—
Sun 18 OctHilversum 15:350 min—
Sat 17 OctHilversum 15:35No data—
Fri 16 OctHilversum 15:390 min—
Thu 15 OctHilversum 15:41No data—
Wed 14 OctHilversum 15:39No data—
Tue 13 OctHilversum 15:48No data—
Mon 12 OctHilversum 15:40+1 min+1 min