Train NS 2766 Maastricht → Alkmaar
NS 2766 Maastricht–Alkmaar: final delay under 3 min on 4 of its 5 runs with data in the last 30 days (80%). Median final delay: 0 min. Running now, on time. Expected at Alkmaar: 20:29. TrainsRadar data as of 22 Nov 2026, 18:16 (GMT+1).
An alert on this phone or computer when the 2766 is 5 min or more late, every day it runs. No account, no email.
Running now · updated 18:16
Heading to Alkmaar 0 min
Estimated arrival at Alkmaar 20:29 · 88 km/h
- Maastricht17:27
- Roermond18:00
- Eindhoven Centraal18:31
- Utrecht Centraal19:21
- Amsterdam Centraal19:50
- Zaandam20:06
- Alkmaar20:29
Today it is running no worse than usual: typical arrival delay is 0 min; 80% of the last 5 runs arrived on time.
Last 30 days
Arrival delay at Alkmaar, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 15 Nov Max en route +14 min · last fix heading to Castricum +14 min
- Sun 11 Oct Max en route +9 min · last fix heading to Castricum +7 min
Distribution · 90 days
7 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 71% · 5
- 3–10 min 14% · 1
- 10–30 min 14% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 100% S n=2
- 60% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 7 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 | Today |
|---|---|---|---|---|
| 17:27 | on time | on time | ||
| 17:43 / 17:46 | ≈ on time | ≈ +1 min | ||
| 18:00 / 18:01 | ≈ on time | ≈ +2 min | ||
| 18:15 | ≈ on time | ≈ +3 min | ||
| 18:31 / 18:34 | ≈ on time | ≈ +4 min | ||
| 18:53 / 18:54 | ≈ +1 min | ≈ +5 min | ||
| 19:21 / 19:24 | ≈ +1 min | ≈ +6 min | ||
| 19:42 | ≈ +1 min | ≈ +8 min | ||
| 19:50 / 19:53 | ≈ +1 min | ≈ +8 min | ||
| 19:58 | ≈ +1 min | ≈ +8 min | ||
| 20:06 | ≈ +1 min | ≈ +9 min | ||
| 20:20 | ≈ +1 min | ≈ +10 min | ||
| 20:29 | +1 min | +10 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 |
|---|---|---|---|
| Sun 22 Nov | Weert 18:14Partial coverage | 0 min | — |
| Sun 15 Nov | Castricum 20:57 | +14 min | +14 min |
| Sun 8 Nov | Amsterdam Sloterdijk 20:19 | +2 min | +3 min |
| Sat 7 Nov | Amsterdam Sloterdijk 20:19 | 0 min | — |
| Sun 1 Nov | Castricum 20:39 | No data | — |
| Sun 25 Oct | Castricum 20:35 | No data | — |
| Sat 24 Oct | Amsterdam Sloterdijk 20:24 | 0 min | — |
| Sun 18 Oct | Castricum 20:35 | 0 min | — |
| Sun 11 Oct | Castricum 20:45 | +7 min | +9 min |
| Sun 4 Oct | Bovenkarspel Flora 21:04 | No data | — |
| Sun 27 Sept | Castricum 20:51 | No data | — |
| Sun 20 Sept | Castricum 20:35 | No data | — |
| Sun 13 Sept | Castricum 20:35 | No data | — |
| Sun 6 Sept | Castricum 20:35 | No data | — |
| Sun 30 Aug | Castricum 20:43 | No data | — |