Train NS 1535 Amsterdam Centraal → Deventer

Amsterdam Centraal 10:30 → Deventer 11:44 Mon, Tue, Wed, Thu, Fri, Sun 1 h 14 min · 5 stops NS (Nederlandse Spoorwegen)

NS 1535 Amsterdam Centraal–Deventer: final delay under 3 min on 21 of its 23 runs with data in the last 30 days (91%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 17:40 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 10:30 from Amsterdam Centraal · Mon 23 Nov

Next departure 10:30 tomorrow · Amsterdam Centraal
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 20 full · 3 partial · 3 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 29 full · 4 partial · 40 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

  • Wed 7 Oct Max en route +13 min · last fix heading to Apeldoorn +13 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Apeldoorn +5 min
  • Wed 18 Nov Max en route +5 min · last fix heading to Apeldoorn +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 30
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 67% W n=6
  • 80% T n=5
  • 100% F n=5
  • 100% 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, 33 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
10:30on time on time
10:50 / 10:52≈ on time ≈ +1 min
11:03 / 11:06≈ on time ≈ +1 min
11:32 / 11:34≈ on time ≈ +2 min
11:44on 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
Fri 20 NovApeldoorn 11:48Partial coverage0 min—
Thu 19 NovApeldoorn 11:480 min—
Wed 18 NovApeldoorn 11:54+5 min+5 min
Tue 17 NovApeldoorn 11:480 min—
Mon 16 NovApeldoorn 11:490 min+1 min
Sun 15 NovHilversum 11:050 min—
Sat 14 NovHilversum 11:08+2 min+2 min
Fri 13 NovApeldoorn 11:48Partial coverage0 min—
Thu 12 NovApeldoorn 11:49+5 min+5 min
Wed 11 NovApeldoorn 11:480 min—
Tue 10 NovApeldoorn 11:480 min—
Mon 9 NovApeldoorn 11:480 min—
Sun 8 NovHilversum 11:040 min—
Sat 7 NovHilversum 11:040 min—
Fri 6 NovApeldoorn 11:48No data—
Thu 5 NovApeldoorn 11:520 min—
Wed 4 NovApeldoorn 11:480 min—
Tue 3 NovApeldoorn 11:49No data—
Mon 2 NovApeldoorn 11:480 min—
Sun 1 NovHilversum 11:060 min—
Sat 31 OctHilversum 11:060 min—
Fri 30 OctApeldoorn 11:49Partial coverage0 min—
Thu 29 OctDieren 12:260 min—
Wed 28 OctDieren 12:230 min—
Tue 27 OctDieren 12:23No data—
Mon 26 OctDieren 12:230 min—
Mon 19 OctApeldoorn 11:500 min—
Sun 18 OctHilversum 11:050 min—
Sat 17 OctHilversum 11:05No data—
Fri 16 OctHilversum 11:100 min—