Train NS 2761 Alkmaar – Maastricht
It has not run yet today
Last recorded run: Sunday 8 November 0 min
Next service: today 15:57 from Alkmaar · Mon 9 Nov
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
- Tue 6 Oct Max en route +29 min · last fix heading to Eindhoven Centraal +28 min
- Sat 31 Oct Max en route +15 min · last fix heading to Sittard +15 min
- Sun 1 Nov Max en route +12 min · last fix heading to Amsterdam Amstel +12 min
- Fri 23 Oct Max en route +6 min · last fix heading to Sittard +6 min
- Mon 5 Oct Max en route +7 min · last fix heading to Schiedam Centrum +6 min
Distribution · 90 days
34 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 82% · 28
- 3–10 min 9% · 3
- 10–30 min 9% · 3
- 30+ min 0% · 0
On-time by weekday
- 80% M n=5
- 80% T n=5
- 100% W n=5
- 100% T n=5
- 80% F n=5
- 80% S n=5
- 50% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 34 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 |
|---|---|---|---|
| 15:57 | on time | on time | |
| 16:05 | ≈ on time | ≈ on time | |
| 16:19 | ≈ on time | ≈ +1 min | |
| 16:25 / 16:26 | ≈ on time | ≈ +1 min | |
| 16:32 / 16:35 | ≈ on time | ≈ +1 min | |
| 16:43 | ≈ on time | ≈ +2 min | |
| 17:01 / 17:04 | ≈ on time | ≈ +2 min | |
| 17:32 / 17:34 | ≈ on time | ≈ +3 min | |
| 17:54 / 17:57 | ≈ on time | ≈ +4 min | |
| 18:15 | ≈ on time | ≈ +5 min | |
| 18:28 / 18:30 | ≈ on time | ≈ +5 min | |
| 18:45 / 18:46 | ≈ on time | ≈ +6 min | |
| 19:00 | on time | +6 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 8 Nov | Sittard 18:59Partial coverage | 0 min | — |
| Sat 7 Nov | Sittard 18:59 | 0 min | — |
| Fri 6 Nov | Sittard 18:59 | +2 min | +3 min |
| Thu 5 Nov | Eindhoven Centraal 19:19 | 0 min | — |
| Wed 4 Nov | Weert 19:02 | 0 min | — |
| Tue 3 Nov | Eindhoven Centraal 19:05 | 0 min | — |
| Mon 2 Nov | Eindhoven Centraal 18:09 | 0 min | — |
| Sun 1 Nov | Amsterdam Amstel 17:31 | +12 min | +12 min |
| Sat 31 Oct | Sittard 19:17 | +15 min | +15 min |
| Fri 30 Oct | Sittard 19:04 | 0 min | — |
| Thu 29 Oct | Eindhoven Centraal 18:11 | 0 min | — |
| Wed 28 Oct | Eindhoven Centraal 19:01 | 0 min | — |
| Tue 27 Oct | Eindhoven Centraal 18:11 | 0 min | — |
| Mon 26 Oct | Eindhoven Centraal 19:01 | 0 min | — |
| Sun 25 Oct | Sittard 19:04 | No data | — |
| Sat 24 Oct | Sittard 19:08 | +2 min | +2 min |
| Fri 23 Oct | Sittard 19:10 | +6 min | +6 min |
| Thu 22 Oct | Roermond 18:44 | 0 min | — |
| Wed 21 Oct | Roermond 19:02 | 0 min | — |
| Tue 20 Oct | Utrecht Centraal 18:53 | 0 min | — |
| Mon 19 Oct | Roermond 19:06 | 0 min | — |
| Sun 18 Oct | Sittard 19:13 | 0 min | +1 min |
| Sat 17 Oct | Sittard 19:33 | 0 min | — |
| Fri 16 Oct | Sittard 19:11 | 0 min | — |
| Thu 15 Oct | Roermond 18:44 | 0 min | — |
| Wed 14 Oct | Sittard 19:09 | 0 min | — |
| Tue 13 Oct | Roermond 19:03 | 0 min | — |
| Mon 12 Oct | Roermond 19:05 | 0 min | — |
| Sun 11 Oct | Ede-Wageningen 17:55 | +4 min | +4 min |
| Sat 10 Oct | Sittard 19:18 | +1 min | — |