Train NS 1547 Amsterdam Centraal – Deventer

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

It has not run yet today

Last recorded run: Monday 16 November +2 min

Next service: today 13:31 from Amsterdam Centraal · Tue 17 Nov

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

  • Mon 9 Nov Max en route +11 min · last fix heading to Apeldoorn +9 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 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=2
  • 100% W n=4
  • 100% T n=3
  • 100% F n=3
  • 100% S n=5
  • 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
13:31on time on time
13:50 / 13:52≈ on time ≈ on time
14:03 / 14:06≈ on time ≈ on time
14:32 / 14:34≈ on time ≈ on time
14:44on time on time

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 14:50Partial coverage+2 min+3 min
Sun 15 NovHilversum 14:050 min—
Sat 14 NovHilversum 14:040 min—
Fri 13 NovApeldoorn 14:52+1 min+2 min
Thu 12 NovApeldoorn 14:49Partial coverage0 min—
Wed 11 NovApeldoorn 14:48Partial coverage+1 min+1 min
Tue 10 NovApeldoorn 14:480 min—
Mon 9 NovApeldoorn 15:03Partial coverage+9 min+11 min
Sun 8 NovHilversum 14:070 min+2 min
Sat 7 NovHilversum 14:040 min—
Fri 6 NovApeldoorn 14:48No data—
Thu 5 NovApeldoorn 14:48No data—
Wed 4 NovApeldoorn 14:49Partial coverage+2 min+3 min
Tue 3 NovApeldoorn 14:48No data—
Mon 2 NovApeldoorn 14:48No data—
Sun 1 NovHilversum 14:070 min—
Sat 31 OctHilversum 14:070 min+1 min
Fri 30 OctApeldoorn 14:480 min—
Thu 29 OctDieren 15:230 min—
Wed 28 OctDieren 15:230 min—
Tue 27 OctDieren 15:24No data—
Mon 26 OctDieren 15:37No data—
Mon 19 OctApeldoorn 14:48Partial coverage0 min—
Sun 18 OctHilversum 14:060 min—
Sat 17 OctHilversum 14:360 min—
Fri 16 OctHilversum 14:10No data—
Thu 15 OctHilversum 14:10No data—
Wed 14 OctHilversum 14:09No data—
Tue 13 OctHilversum 14:09No data—
Mon 12 OctHilversum 14:090 min—