Train NS 1539 Amsterdam Centraal – Deventer

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 11:31 from Amsterdam Centraal · Sat 7 Nov

Next departure 11:31 today · Amsterdam Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 11 full · 3 partial · 9 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 12 full · 6 partial · 49 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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:31on time on time
11:50 / 11:52≈ on time ≈ on time
12:03 / 12:06≈ on time ≈ on time
12:32 / 12:34≈ on time ≈ on time
12: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
Fri 6 NovApeldoorn 12:48No data—
Thu 5 NovApeldoorn 12:48No data—
Wed 4 NovApeldoorn 12:48Partial coverage0 min—
Tue 3 NovApeldoorn 12:48No data—
Mon 2 NovApeldoorn 12:48Partial coverage0 min—
Sun 1 NovHilversum 12:070 min—
Sat 31 OctHilversum 12:060 min—
Fri 30 OctApeldoorn 12:480 min—
Thu 29 OctDieren 13:250 min—
Wed 28 OctDieren 13:23No data—
Tue 27 OctDieren 13:23No data—
Mon 26 OctDieren 13:25No data—
Mon 19 OctApeldoorn 12:48Partial coverage0 min—
Sun 18 OctHilversum 12:05+2 min+2 min
Sat 17 OctHilversum 12:050 min—
Fri 16 OctHilversum 12:10No data—
Thu 15 OctHilversum 12:09No data—
Wed 14 OctHilversum 12:160 min—
Tue 13 OctHilversum 12:10No data—
Mon 12 OctHilversum 12:100 min—
Sun 11 OctHilversum 12:060 min—
Sat 10 OctHilversum 12:060 min—
Fri 9 OctApeldoorn 12:480 min—
Thu 8 OctApeldoorn 12:48Partial coverage0 min—
Wed 7 OctApeldoorn 12:49Partial coverage+1 min—
Tue 6 OctApeldoorn 12:48Partial coverage0 min—
Mon 5 OctApeldoorn 12:480 min—
Fri 2 OctApeldoorn 12:48No data—
Thu 1 OctApeldoorn 12:48No data—
Wed 30 SeptApeldoorn 12:48No data—