Train NS 2773 Alkmaar → Maastricht
NS 2773 Alkmaar–Maastricht: final delay under 3 min on 4 of its 6 runs with data in the last 30 days (67%). Median final delay: 0 min. Running now, on time. Expected at Maastricht: 22:03. TrainsRadar data as of 22 Nov 2026, 20:22 (GMT+1).
An alert on this phone or computer when the 2773 is 5 min or more late, every day it runs. No account, no email.
Running now · updated 20:22
Position estimated from the timetable
Heading to Maastricht 0 min
Estimated arrival at Maastricht 22:03 · 96 km/h
- Alkmaar19:01
- Zaandam19:25
- Amsterdam Centraal19:37
- Utrecht Centraal20:06
- Eindhoven Centraal20:58
- Roermond21:30
- Maastricht22:03
Today it is running no worse than usual: typical arrival delay is 0 min; 67% of the last 6 runs arrived on time.
Last 30 days
Arrival delay at Maastricht, 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 +7 min · last fix heading to Weert +7 min
- Sun 18 Oct Max en route +7 min · last fix heading to Sittard +6 min
- Sun 1 Nov Max en route +3 min · last fix heading to Amsterdam Amstel +3 min
- Sun 11 Oct Max en route +3 min · last fix heading to Ede-Wageningen +3 min
Distribution · 90 days
8 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 50% · 4
- 3–10 min 50% · 4
- 10–30 min 0% · 0
- 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
- 33% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 8 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 |
|---|---|---|---|---|
| 19:01 | on time | on time | ||
| 19:09 | ≈ on time | ≈ on time | ||
| 19:25 | ≈ on time | ≈ +1 min | ||
| 19:31 | ≈ on time | ≈ +1 min | ||
| 19:37 / 19:39 | ≈ on time | ≈ +1 min | ||
| 19:47 | ≈ on time | ≈ +1 min | ||
| 20:06 / 20:09 | ≈ +1 min | ≈ +2 min | ||
| 20:36 / 20:38 | ≈ +1 min | ≈ +3 min | ||
| 20:58 / 21:00 | ≈ +1 min | ≈ +3 min | ||
| 21:17 | ≈ +1 min | ≈ +4 min | ||
| 21:30 / 21:31 | ≈ +1 min | ≈ +4 min | ||
| 21:46 / 21:47 | ≈ +1 min | ≈ +4 min | ||
| 22:03 | +2 min | +5 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 | 's-Hertogenbosch 20:19Partial coverage | 0 min | — |
| Sun 15 Nov | Weert 21:44 | +7 min | +7 min |
| Sun 8 Nov | Sittard 22:02 | 0 min | — |
| Sat 7 Nov | Sittard 21:59 | 0 min | — |
| Sun 1 Nov | Amsterdam Amstel 20:13 | +3 min | +3 min |
| Sun 25 Oct | Sittard 22:02 | No data | — |
| Sat 24 Oct | Sittard 22:01 | 0 min | — |
| Sun 18 Oct | Sittard 22:09Partial coverage | +6 min | +7 min |
| Sat 17 Oct | Amsterdam Sloterdijk 19:46 | No data | — |
| Sun 11 Oct | Ede-Wageningen 20:53 | +3 min | +3 min |
| Sun 4 Oct | Sittard 22:02 | No data | — |
| Sun 27 Sept | Sittard 22:17 | No data | — |
| Sun 20 Sept | Utrecht Centraal 20:25 | No data | — |
| Sun 13 Sept | Sittard 22:01 | No data | — |
| Sun 6 Sept | Weert 21:32 | No data | — |
| Sun 30 Aug | Sittard 22:04 | No data | — |