Train NS 2765 Alkmaar – Maastricht
It has not run yet today
Last recorded run: Thursday 5 November 0 min
Next service: today 16:57 from Alkmaar · Fri 6 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 +12 min · last fix heading to Utrecht Centraal +12 min
- Wed 4 Nov Max en route +11 min · last fix heading to Utrecht Centraal +11 min
- Fri 23 Oct Max en route +6 min · last fix heading to Weert +6 min
- Sun 11 Oct Max en route +3 min · last fix heading to Ede-Wageningen +3 min
Distribution · 90 days
29 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 25
- 3–10 min 7% · 2
- 10–30 min 7% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 75% T n=4
- 80% W n=5
- 100% T n=4
- 75% F n=4
- 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, 29 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 |
|---|---|---|---|
| 16:57 | on time | on time | |
| 17:05 | ≈ on time | ≈ on time | |
| 17:19 | ≈ on time | ≈ +1 min | |
| 17:25 / 17:26 | ≈ on time | ≈ +1 min | |
| 17:32 / 17:34 | ≈ on time | ≈ +1 min | |
| 17:42 | ≈ on time | ≈ +1 min | |
| 18:01 / 18:04 | ≈ on time | ≈ +2 min | |
| 18:31 / 18:33 | ≈ on time | ≈ +2 min | |
| 18:54 / 18:57 | ≈ on time | ≈ +3 min | |
| 19:15 | ≈ on time | ≈ +3 min | |
| 19:28 / 19:30 | ≈ on time | ≈ +4 min | |
| 19:45 / 19:46 | ≈ on time | ≈ +4 min | |
| 20:00 | on time | +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 |
|---|---|---|---|
| Thu 5 Nov | Utrecht Centraal 20:28Partial coverage | 0 min | — |
| Wed 4 Nov | Utrecht Centraal 20:22 | +11 min | +11 min |
| Tue 3 Nov | Utrecht Centraal 18:59 | 0 min | — |
| Mon 2 Nov | Utrecht Centraal 19:59 | 0 min | — |
| Sun 1 Nov | Amsterdam Amstel 18:11 | +1 min | +1 min |
| Sat 31 Oct | Sittard 20:16 | +1 min | +4 min |
| Fri 30 Oct | 's-Hertogenbosch 18:52 | 0 min | — |
| Thu 29 Oct | Amsterdam Amstel 20:01 | 0 min | — |
| Wed 28 Oct | Utrecht Centraal 18:56 | +1 min | +1 min |
| Tue 27 Oct | Utrecht Centraal 20:23 | No data | — |
| Mon 26 Oct | Utrecht Centraal 18:55 | 0 min | — |
| Sun 25 Oct | Sittard 20:32 | No data | — |
| Sat 24 Oct | Sittard 20:04 | 0 min | — |
| Fri 23 Oct | Weert 20:14 | +6 min | +6 min |
| Thu 22 Oct | 's-Hertogenbosch 18:56 | 0 min | — |
| Wed 21 Oct | 's-Hertogenbosch 20:02 | 0 min | — |
| Tue 20 Oct | Zaandam 19:00 | 0 min | — |
| Mon 19 Oct | 's-Hertogenbosch 20:04 | 0 min | — |
| Sun 18 Oct | Sittard 20:02 | 0 min | +2 min |
| Sat 17 Oct | Sittard 20:02 | 0 min | — |
| Fri 16 Oct | Sittard 20:04 | 0 min | — |
| Thu 15 Oct | Amsterdam Amstel 18:02 | No data | — |
| Wed 14 Oct | Sittard 20:02 | 0 min | — |
| Tue 13 Oct | 's-Hertogenbosch 20:29 | 0 min | — |
| Mon 12 Oct | 's-Hertogenbosch 20:01 | 0 min | — |
| Sun 11 Oct | Ede-Wageningen 18:54 | +3 min | +3 min |
| Sat 10 Oct | Sittard 20:02 | 0 min | — |
| Fri 9 Oct | Utrecht Centraal 18:23 | 0 min | — |
| Thu 8 Oct | Amsterdam Amstel 22:06 | 0 min | +1 min |
| Wed 7 Oct | Amsterdam Amstel 02:28Partial coverage | 0 min | +18 min |