Train NS 2777 Alkmaar – Maastricht
It does not run today
Last recorded run: Sunday 4 October No data
Next service: tomorrow 20:01 from Alkmaar · Sun 11 Oct
Next departure 20:01 tomorrow · Alkmaar
On-time · 30 days
—
Too little data (0/4 runs with data)
RT coverage: 0 full · 0 partial · 4 no data
On-time · 90 days
—
Too little data (0/11 runs with data)
RT coverage: 0 full · 0 partial · 11 no data
Typical delay
—
Needs at least 5 runs with data (0 so far)
P90
—
Needs at least 5 runs with data (0 so far)
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
Distribution · 90 days
No runs with a known final delay yet.
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
| Stop | Sched. |
|---|---|
| 20:01 | |
| 20:09 | |
| 20:25 | |
| 20:31 | |
| 20:37 / 20:39 | |
| 20:47 | |
| 21:06 / 21:09 | |
| 21:36 / 21:38 | |
| 21:58 / 22:00 | |
| 22:17 | |
| 22:30 / 22:31 | |
| 22:46 / 22:47 | |
| 23:03 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 4 Oct | Sittard 23:02 | No data | — |
| Sun 27 Sept | Sittard 23:03 | No data | — |
| Sun 20 Sept | Utrecht Centraal 21:25 | No data | — |
| Sun 13 Sept | Sittard 23:03 | No data | — |
| Sun 6 Sept | Weert 22:35 | No data | — |
| Sun 30 Aug | Sittard 23:06 | No data | — |
| Sun 16 Aug | Amsterdam Amstel 21:02 | No data | — |
| Sun 9 Aug | Sittard 23:05 | No data | — |
| Sun 2 Aug | Sittard 23:02 | No data | — |
| Sun 26 Jul | Sittard 23:02 | No data | — |
| Sun 19 Jul | 's-Hertogenbosch 21:52 | No data | — |