Train NS 1540 Deventer → Amsterdam Centraal
NS 1540 Deventer–Amsterdam Centraal: 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 23 Nov 2026, 00:04 (GMT+1).
An alert on this phone or computer when the 1540 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Friday 20 November 0 min
Next service: today 11:48 from Deventer · Mon 23 Nov
Last 30 days
Arrival delay at Amsterdam Centraal, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 16 Nov Max en route +12 min · last fix heading to Hilversum +12 min
- Sat 14 Nov Max en route +5 min · last fix heading to Hilversum +5 min
Distribution · 90 days
35 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 33
- 3–10 min 3% · 1
- 10–30 min 3% · 1
- 30+ min 0% · 0
On-time by weekday
- 83% M n=6
- 100% T n=5
- 100% W n=5
- 100% T n=5
- 100% F n=4
- 80% S n=5
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 35 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 |
|---|---|---|---|
| 11:48 | on time | on time | |
| 11:58 / 12:00 | ≈ on time | ≈ on time | |
| 12:24 / 12:26 | ≈ on time | ≈ +1 min | |
| 12:37 / 12:39 | ≈ on time | ≈ +2 min | |
| 12:59 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 20 Nov | Hilversum 12:59Partial coverage | 0 min | — |
| Thu 19 Nov | Hilversum 12:59Partial coverage | 0 min | — |
| Wed 18 Nov | Hilversum 12:59Partial coverage | 0 min | — |
| Tue 17 Nov | Hilversum 12:59 | 0 min | — |
| Mon 16 Nov | Hilversum 13:14 | +12 min | +12 min |
| Sun 15 Nov | Hilversum 12:59 | +1 min | +1 min |
| Sat 14 Nov | Hilversum 13:04 | +5 min | +5 min |
| Fri 13 Nov | Hilversum 13:04 | +2 min | +3 min |
| Thu 12 Nov | Hilversum 13:03Partial coverage | +1 min | +1 min |
| Wed 11 Nov | Hilversum 13:03Partial coverage | +2 min | +3 min |
| Tue 10 Nov | Amersfoort Centraal 12:39 | 0 min | — |
| Mon 9 Nov | Hilversum 12:53 | 0 min | — |
| Sun 8 Nov | Hilversum 12:53 | 0 min | — |
| Sat 7 Nov | Hilversum 12:59 | 0 min | — |
| Fri 6 Nov | Hilversum 12:59 | No data | — |
| Thu 5 Nov | Hilversum 13:03Partial coverage | 0 min | — |
| Wed 4 Nov | Hilversum 12:59Partial coverage | 0 min | +2 min |
| Tue 3 Nov | Hilversum 13:04 | 0 min | — |
| Mon 2 Nov | Hilversum 12:58 | 0 min | — |
| Sun 1 Nov | Hilversum 13:01 | 0 min | — |
| Sat 31 Oct | Hilversum 13:18 | +2 min | +4 min |
| Fri 30 Oct | Hilversum 13:03Partial coverage | 0 min | — |
| Thu 29 Oct | Hilversum 13:00 | 0 min | — |
| Wed 28 Oct | Hilversum 13:01 | 0 min | — |
| Tue 27 Oct | Hilversum 13:01 | No data | — |
| Mon 26 Oct | Hilversum 12:55 | No data | — |
| Mon 19 Oct | Hilversum 13:00 | 0 min | — |
| Sun 18 Oct | Amersfoort Centraal 12:35 | 0 min | — |
| Sat 17 Oct | Amersfoort Centraal 12:38 | 0 min | — |
| Fri 16 Oct | Hilversum 13:00 | No data | — |