Train NS 2725 Alkmaar – Maastricht
✓ Today’s run finished
Today, last fix heading to Sittard at 10:09 0 min
- Alkmaar06:57
- Zaandam07:19
- Amsterdam Centraal07:32
- Utrecht Centraal08:01
- Eindhoven Centraal08:54
- Sittard09:45
- Maastricht10:00
Next service: tomorrow 06: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
- Mon 26 Oct Max en route +10 min · last fix heading to Sittard +10 min
- Sat 24 Oct Max en route +9 min · last fix heading to Sittard +9 min
- Thu 8 Oct Max en route +5 min · last fix heading to Sittard +4 min
Distribution · 90 days
22 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 19
- 3–10 min 9% · 2
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 100% T n=4
- 100% W n=5
- 80% T n=5
- 100% F n=4
- 0% S n=1
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 22 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 |
|---|---|---|---|
| 06:57 | on time | on time | |
| 07:05 | ≈ on time | ≈ on time | |
| 07:19 | ≈ on time | ≈ on time | |
| 07:25 / 07:26 | ≈ on time | ≈ on time | |
| 07:32 / 07:34 | ≈ on time | ≈ on time | |
| 07:42 | ≈ on time | ≈ on time | |
| 08:01 / 08:04 | ≈ on time | ≈ on time | |
| 08:32 / 08:34 | ≈ on time | ≈ on time | |
| 08:54 / 08:57 | ≈ on time | ≈ on time | |
| 09:15 | ≈ on time | ≈ on time | |
| 09:28 / 09:30 | ≈ on time | ≈ on time | |
| 09:45 / 09:46 | ≈ on time | ≈ on time | |
| 10:00 | on time | on time |
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 | Sittard 10:09Partial coverage | 0 min | — |
| Wed 4 Nov | Sittard 09:59Partial coverage | 0 min | — |
| Tue 3 Nov | Sittard 10:02Partial coverage | 0 min | — |
| Mon 2 Nov | Sittard 09:59 | No data | — |
| Fri 30 Oct | Sittard 10:02 | 0 min | — |
| Thu 29 Oct | Sittard 10:02 | 0 min | — |
| Wed 28 Oct | Sittard 10:02 | 0 min | — |
| Tue 27 Oct | Sittard 10:01 | 0 min | — |
| Mon 26 Oct | Sittard 10:00Partial coverage | +10 min | +10 min |
| Sat 24 Oct | Sittard 10:18 | +9 min | +9 min |
| Fri 23 Oct | Sittard 10:04 | 0 min | — |
| Thu 22 Oct | Sittard 10:02 | 0 min | — |
| Wed 21 Oct | Sittard 10:01 | 0 min | — |
| Tue 20 Oct | Sittard 10:01 | 0 min | — |
| Mon 19 Oct | Sittard 10:07Partial coverage | 0 min | — |
| Fri 16 Oct | Sittard 10:05 | 0 min | — |
| Thu 15 Oct | Roermond 10:58 | 0 min | — |
| Wed 14 Oct | Sittard 10:01 | 0 min | — |
| Tue 13 Oct | Sittard 10:02 | No data | — |
| Mon 12 Oct | Sittard 10:02 | 0 min | — |
| Fri 9 Oct | Sittard 10:05 | 0 min | — |
| Thu 8 Oct | Sittard 10:08Partial coverage | +4 min | +5 min |
| Wed 7 Oct | Sittard 10:02Partial coverage | 0 min | — |
| Tue 6 Oct | Sittard 10:03Partial coverage | +1 min | +1 min |
| Mon 5 Oct | Schiedam Centrum 08:44 | No data | — |
| Fri 2 Oct | Sittard 10:04 | No data | — |
| Thu 1 Oct | Sittard 10:00 | No data | — |
| Wed 30 Sept | Sittard 10:01 | No data | — |
| Tue 29 Sept | Sittard 10:01 | No data | — |
| Mon 28 Sept | Sittard 10:00 | No data | — |