Train NS 1551 Amsterdam Centraal – Deventer

Amsterdam Centraal 14:30 → Deventer 15:44 Daily 1 h 14 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Apeldoorn at 15:48 0 min

  1. Amsterdam Centraal14:30
  2. Hilversum14:50
  3. Amersfoort Centraal15:03
  4. Apeldoorn15:32
  5. Deventer15:44

Next service: Monday 14:30 from Amsterdam Centraal · Mon 23 Nov

Next departure 14:30 Monday · Amsterdam Centraal
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 18 full · 3 partial · 5 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 26 full · 4 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Sat 10 Oct Max en route +11 min · last fix heading to Hilversum +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=5
  • 100% T n=4
  • 100% 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, 30 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:30on time on time
14:50 / 14:52≈ on time ≈ on time
15:03 / 15:06≈ on time ≈ on time
15:32 / 15:34≈ on time ≈ +1 min
15:44on 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
Fri 20 NovApeldoorn 15:48Partial coverage0 min—
Thu 19 NovApeldoorn 15:480 min—
Wed 18 NovApeldoorn 15:480 min—
Tue 17 NovApeldoorn 15:480 min—
Mon 16 NovApeldoorn 15:49+2 min+2 min
Sun 15 NovHilversum 15:040 min+1 min
Sat 14 NovHilversum 15:040 min—
Fri 13 NovApeldoorn 15:49Partial coverage0 min—
Thu 12 NovApeldoorn 15:480 min—
Wed 11 NovApeldoorn 15:490 min+2 min
Tue 10 NovApeldoorn 15:480 min—
Mon 9 NovApeldoorn 15:480 min—
Sun 8 NovHilversum 15:040 min—
Sat 7 NovHilversum 15:040 min+1 min
Fri 6 NovApeldoorn 15:48No data—
Thu 5 NovApeldoorn 15:48No data—
Wed 4 NovApeldoorn 15:480 min—
Tue 3 NovApeldoorn 15:48No data—
Mon 2 NovApeldoorn 15:48No data—
Sun 1 NovHilversum 15:060 min—
Sat 31 OctHilversum 15:060 min—
Fri 30 OctApeldoorn 15:48Partial coverage0 min—
Thu 29 OctDieren 16:240 min—
Wed 28 OctDieren 16:230 min—
Tue 27 OctDieren 16:26No data—
Mon 26 OctDieren 16:340 min—
Mon 19 OctApeldoorn 15:490 min—
Sun 18 OctHilversum 15:050 min—
Sat 17 OctHilversum 15:06No data—
Fri 16 OctHilversum 15:10No data—