Train NS 1535 Amsterdam Centraal → Deventer
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).
An alert on this phone or computer when the 1535 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Friday 20 November 0 min
Next service: tomorrow 10:30 from Amsterdam Centraal · Mon 23 Nov
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 10:30 | on 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:44 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 20 Nov | Apeldoorn 11:48Partial coverage | 0 min | — |
| Thu 19 Nov | Apeldoorn 11:48 | 0 min | — |
| Wed 18 Nov | Apeldoorn 11:54 | +5 min | +5 min |
| Tue 17 Nov | Apeldoorn 11:48 | 0 min | — |
| Mon 16 Nov | Apeldoorn 11:49 | 0 min | +1 min |
| Sun 15 Nov | Hilversum 11:05 | 0 min | — |
| Sat 14 Nov | Hilversum 11:08 | +2 min | +2 min |
| Fri 13 Nov | Apeldoorn 11:48Partial coverage | 0 min | — |
| Thu 12 Nov | Apeldoorn 11:49 | +5 min | +5 min |
| Wed 11 Nov | Apeldoorn 11:48 | 0 min | — |
| Tue 10 Nov | Apeldoorn 11:48 | 0 min | — |
| Mon 9 Nov | Apeldoorn 11:48 | 0 min | — |
| Sun 8 Nov | Hilversum 11:04 | 0 min | — |
| Sat 7 Nov | Hilversum 11:04 | 0 min | — |
| Fri 6 Nov | Apeldoorn 11:48 | No data | — |
| Thu 5 Nov | Apeldoorn 11:52 | 0 min | — |
| Wed 4 Nov | Apeldoorn 11:48 | 0 min | — |
| Tue 3 Nov | Apeldoorn 11:49 | No data | — |
| Mon 2 Nov | Apeldoorn 11:48 | 0 min | — |
| Sun 1 Nov | Hilversum 11:06 | 0 min | — |
| Sat 31 Oct | Hilversum 11:06 | 0 min | — |
| Fri 30 Oct | Apeldoorn 11:49Partial coverage | 0 min | — |
| Thu 29 Oct | Dieren 12:26 | 0 min | — |
| Wed 28 Oct | Dieren 12:23 | 0 min | — |
| Tue 27 Oct | Dieren 12:23 | No data | — |
| Mon 26 Oct | Dieren 12:23 | 0 min | — |
| Mon 19 Oct | Apeldoorn 11:50 | 0 min | — |
| Sun 18 Oct | Hilversum 11:05 | 0 min | — |
| Sat 17 Oct | Hilversum 11:05 | No data | — |
| Fri 16 Oct | Hilversum 11:10 | 0 min | — |