Train NS 1537 Amsterdam Centraal – Deventer

Amsterdam Centraal 11:00 → Deventer 12:12 Daily 1 h 12 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 11:00 from Amsterdam Centraal · Fri 6 Nov

Next departure 11:00 today · Amsterdam Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 9 full · 6 partial · 8 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 9 full · 8 partial · 49 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 50% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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
11:00on time on time
11:20 / 11:22≈ on time ≈ +1 min
11:33 / 11:36≈ on time ≈ +1 min
12:00 / 12:02≈ on time ≈ +2 min
12:12on 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
Thu 5 NovApeldoorn 12:14Partial coverage0 min—
Wed 4 NovApeldoorn 12:14Partial coverage0 min—
Tue 3 NovApeldoorn 12:14Partial coverage0 min—
Mon 2 NovApeldoorn 12:19Partial coverage0 min—
Sun 1 NovHilversum 11:39+1 min+5 min
Sat 31 OctHilversum 11:360 min—
Fri 30 OctApeldoorn 12:16No data—
Thu 29 OctDieren 12:520 min—
Wed 28 OctDieren 12:520 min—
Tue 27 OctDieren 12:52No data—
Mon 26 OctDieren 12:52No data—
Mon 19 OctApeldoorn 12:16Partial coverage0 min—
Sun 18 OctHilversum 11:350 min—
Sat 17 OctHilversum 11:35No data—
Fri 16 OctHilversum 11:410 min—
Thu 15 OctHilversum 11:39No data—
Wed 14 OctHilversum 11:51No data—
Tue 13 OctHilversum 11:44No data—
Mon 12 OctHilversum 11:52No data—
Sun 11 OctHilversum 11:38+2 min+2 min
Sat 10 OctHilversum 11:42+4 min+9 min
Fri 9 OctApeldoorn 12:160 min—
Thu 8 OctApeldoorn 12:16Partial coverage0 min—
Wed 7 OctApeldoorn 12:16Partial coverage0 min—
Tue 6 OctApeldoorn 12:16Partial coverage0 min—
Mon 5 OctApeldoorn 12:16No data—
Fri 2 OctApeldoorn 12:16No data—
Thu 1 OctApeldoorn 12:16No data—
Wed 30 SeptApeldoorn 12:16No data—
Tue 29 SeptApeldoorn 12:16No data—