Train NS 1531 Amsterdam Centraal – Deventer

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

✓ Today’s run finished

Today, last fix heading to Apeldoorn at 10:48 No data

  1. Amsterdam Centraal09:31
  2. Hilversum09:50
  3. Amersfoort Centraal10:03
  4. Apeldoorn10:32
  5. Deventer10:44

Next service: tomorrow 09:31 from Amsterdam Centraal · Sat 7 Nov

Next departure 09:31 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 11 full · 5 partial · 8 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 11 full · 7 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=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 100% 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, 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
09:31on time on time
09:50 / 09:52≈ on time ≈ on time
10:03 / 10:06≈ on time ≈ on time
10:32 / 10:34≈ on time ≈ on time
10: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 10:48No data—
Thu 5 NovApeldoorn 10:48Partial coverage0 min—
Wed 4 NovApeldoorn 10:48Partial coverage0 min—
Tue 3 NovApeldoorn 10:48No data—
Mon 2 NovApeldoorn 10:54Partial coverage0 min—
Sun 1 NovHilversum 10:080 min+2 min
Sat 31 OctHilversum 10:070 min—
Fri 30 OctApeldoorn 10:480 min—
Thu 29 OctDieren 11:230 min—
Wed 28 OctDieren 11:29No data—
Tue 27 OctDieren 11:24No data—
Mon 26 OctDieren 11:23No data—
Mon 19 OctApeldoorn 10:48Partial coverage0 min—
Sun 18 OctHilversum 10:050 min—
Sat 17 OctHilversum 10:180 min—
Fri 16 OctHilversum 10:10No data—
Thu 15 OctHilversum 10:58No data—
Wed 14 OctHilversum 10:110 min—
Tue 13 OctHilversum 10:100 min—
Mon 12 OctHilversum 10:100 min—
Sun 11 OctHilversum 10:060 min—
Sat 10 OctHilversum 10:06No data—
Fri 9 OctApeldoorn 10:480 min—
Thu 8 OctApeldoorn 10:48Partial coverage0 min—
Wed 7 OctApeldoorn 10:48Partial coverage0 min—
Tue 6 OctApeldoorn 10:48Partial coverage0 min—
Mon 5 OctApeldoorn 10:49No data—
Fri 2 OctApeldoorn 10:48No data—
Thu 1 OctApeldoorn 10:48No data—
Wed 30 SeptApeldoorn 10:49No data—