Train NS 1545 Amsterdam Centraal – Deventer

Amsterdam Centraal 12:59 → Deventer 14: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 12:59 from Amsterdam Centraal · Tue 17 Nov

Next departure 12:59 today · Amsterdam Centraal
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 9 full · 9 partial · 5 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 15 full · 13 partial · 46 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: +5 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 +8 min · last fix heading to Apeldoorn +8 min
  • Sat 7 Nov Max en route +8 min · last fix heading to Hilversum +7 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Hilversum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 25
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=3
  • 100% W n=4
  • 100% T n=3
  • 67% F n=3
  • 50% 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, 28 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
12:59on time on time
13:20 / 13:22≈ on time ≈ +1 min
13:33 / 13:36≈ on time ≈ +1 min
14:00 / 14:02≈ on time ≈ +2 min
14:12on time +3 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 14:15Partial coverage+1 min+1 min
Sun 15 NovHilversum 13:340 min—
Sat 14 NovHilversum 13:340 min+3 min
Fri 13 NovApeldoorn 14:28Partial coverage+8 min+8 min
Thu 12 NovApeldoorn 14:17Partial coverage+1 min—
Wed 11 NovApeldoorn 14:14Partial coverage0 min—
Tue 10 NovApeldoorn 14:15Partial coverage0 min—
Mon 9 NovApeldoorn 14:14Partial coverage0 min—
Sun 8 NovHilversum 13:340 min—
Sat 7 NovHilversum 13:49+7 min+8 min
Fri 6 NovApeldoorn 14:17No data—
Thu 5 NovApeldoorn 14:14No data—
Wed 4 NovApeldoorn 14:14Partial coverage0 min—
Tue 3 NovApeldoorn 14:14No data—
Mon 2 NovApeldoorn 14:14No data—
Sun 1 NovHilversum 13:370 min+2 min
Sat 31 OctHilversum 13:36+4 min+4 min
Fri 30 OctApeldoorn 14:16Partial coverage0 min—
Thu 29 OctDieren 14:520 min—
Wed 28 OctDieren 14:54No data—
Tue 27 OctDieren 14:530 min—
Mon 26 OctDieren 14:520 min—
Mon 19 OctApeldoorn 14:16Partial coverage0 min—
Sun 18 OctHilversum 13:37+1 min+1 min
Sat 17 OctHilversum 13:41No data—
Fri 16 OctHilversum 13:39No data—
Thu 15 OctHilversum 13:40No data—
Wed 14 OctHilversum 13:400 min—
Tue 13 OctHilversum 13:40No data—
Mon 12 OctHilversum 13:460 min—