Train NS 4097 Alkmaar → Amsterdam Centraal
NS 4097 Alkmaar–Amsterdam Centraal: final delay under 3 min on 15 of its 15 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 05:47 (GMT+1).
An alert on this phone or computer when the 4097 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 +2 min
Next service: tomorrow 00:31 from Alkmaar · 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
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 27
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=4
- 100% W n=4
- 100% T n=7
- 100% F n=5
- 100% S n=1
- 100% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 27 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 |
|---|---|---|---|
| 00:31 | on time | on time | |
| 00:36 | ≈ on time | ≈ on time | |
| 00:41 | ≈ on time | ≈ on time | |
| 00:45 / 00:48 | ≈ on time | ≈ on time | |
| 00:53 | ≈ on time | ≈ on time | |
| 00:56 | ≈ on time | ≈ on time | |
| 00:59 | ≈ on time | ≈ on time | |
| 01:02 | ≈ on time | ≈ on time | |
| 01:05 | ≈ on time | ≈ on time | |
| 01:11 | ≈ on time | ≈ on time | |
| 01:17 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 20 Nov | — 01:18 | +2 min | +2 min |
| Thu 19 Nov | — 01:18 | 0 min | — |
| Wed 18 Nov | — 01:18 | 0 min | — |
| Mon 16 Nov | Amsterdam Sloterdijk 01:28 | 0 min | — |
| Fri 13 Nov | — 01:19 | 0 min | +2 min |
| Thu 12 Nov | — 01:59 | 0 min | — |
| Wed 11 Nov | — 01:18 | 0 min | — |
| Tue 10 Nov | — 01:18 | 0 min | — |
| Mon 9 Nov | Amsterdam Sloterdijk 01:24 | 0 min | — |
| Fri 6 Nov | — 01:39 | 0 min | — |
| Thu 5 Nov | — 01:19 | 0 min | — |
| Wed 4 Nov | — 01:19 | 0 min | — |
| Tue 3 Nov | — 01:18 | 0 min | — |
| Thu 29 Oct | — 01:21 | 0 min | — |
| Mon 26 Oct | Amsterdam Sloterdijk 01:26 | 0 min | — |
| Fri 23 Oct | — 01:37 | 0 min | — |
| Thu 22 Oct | — 01:18 | 0 min | — |
| Tue 20 Oct | — 01:18 | 0 min | — |
| Mon 19 Oct | Amsterdam Sloterdijk 01:25 | 0 min | — |
| Sun 18 Oct | Amsterdam Sloterdijk 01:42 | 0 min | — |
| Sat 17 Oct | — 01:35 | 0 min | — |
| Fri 16 Oct | — 01:18 | 0 min | — |
| Thu 15 Oct | — 01:19 | 0 min | — |
| Wed 14 Oct | — 01:19 | 0 min | — |
| Tue 13 Oct | — 01:21 | 0 min | — |
| Mon 12 Oct | Amsterdam Sloterdijk 01:30 | 0 min | — |
| Thu 8 Oct | — 01:22 | 0 min | — |
| Mon 5 Oct | Amsterdam Sloterdijk 01:25 | No data | — |
| Mon 28 Sept | Amsterdam Sloterdijk 01:28 | No data | — |
| Mon 21 Sept | Amsterdam Sloterdijk 01:26 | No data | — |