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