Train NS 2925 Den Helder – Nijmegen
It does not run today
Last recorded run: Sunday 1 November 0 min
Next service: tomorrow 06:04 from Den Helder · Fri 6 Nov
Last 30 days
Arrival delay at Nijmegen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sat 31 Oct Max en route +26 min · last fix heading to Sittard +24 min
Distribution · 90 days
9 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 8
- 3–10 min 0% · 0
- 10–30 min 11% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- 100% F n=3
- 67% S n=3
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (19 stops).
Last 90 days, 9 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:04 | on time | on time | |
| 06:08 | ≈ on time | ≈ on time | |
| 06:14 / 06:16 | ≈ on time | ≈ on time | |
| 06:22 | ≈ on time | ≈ +1 min | |
| 06:32 | ≈ on time | ≈ +1 min | |
| 06:37 | ≈ on time | ≈ +2 min | |
| 06:40 / 06:43 | ≈ on time | ≈ +2 min | |
| 06:49 | ≈ on time | ≈ +2 min | |
| 06:55 | ≈ on time | ≈ +2 min | |
| 07:08 | ≈ on time | ≈ +3 min | |
| 07:15 | ≈ on time | ≈ +3 min | |
| 07:21 / 07:27 | ≈ on time | ≈ +4 min | |
| 07:35 | ≈ on time | ≈ +4 min | |
| 07:39 / 07:40 | ≈ on time | ≈ +4 min | |
| 07:58 / 08:09 | ≈ on time | ≈ +5 min | |
| 08:27 | ≈ +1 min | ≈ +7 min | |
| 08:33 | ≈ +1 min | ≈ +7 min | |
| 08:43 / 08:50 | ≈ +1 min | ≈ +7 min | |
| 09:02 | +1 min | +8 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 1 Nov | Arnhem Centraal 09:07Partial coverage | 0 min | — |
| Sat 31 Oct | Sittard 10:51 | +24 min | +26 min |
| Fri 30 Oct | Amsterdam Sloterdijk 07:49 | +1 min | — |
| Sun 25 Oct | Sittard 10:05 | No data | — |
| Sun 18 Oct | Sittard 10:04 | +1 min | — |
| Sat 17 Oct | Sittard 10:07 | +1 min | +6 min |
| Fri 16 Oct | Amsterdam Sloterdijk 07:49 | 0 min | — |
| Sun 11 Oct | Ede-Wageningen 08:50 | +1 min | — |
| Sat 10 Oct | Sittard 10:04 | 0 min | — |
| Fri 9 Oct | Amsterdam Sloterdijk 07:48 | +2 min | +2 min |
| Mon 5 Oct | Sittard 10:02 | No data | — |
| Sun 4 Oct | Sittard 10:01 | No data | — |
| Sat 3 Oct | Sittard 10:02 | No data | — |
| Fri 2 Oct | Amsterdam Sloterdijk 07:50 | No data | — |
| Sun 27 Sept | Sittard 10:03 | No data | — |
| Sat 26 Sept | Amsterdam Amstel 08:02 | No data | — |
| Fri 25 Sept | Amsterdam Sloterdijk 07:49 | No data | — |
| Sun 20 Sept | Utrecht Centraal 08:23 | No data | — |
| Sat 19 Sept | Utrecht Centraal 08:23 | No data | — |
| Fri 18 Sept | Amsterdam Sloterdijk 07:50 | No data | — |
| Sun 13 Sept | Sittard 10:02 | No data | — |
| Sat 12 Sept | Sittard 10:02 | No data | — |
| Fri 11 Sept | Amsterdam Sloterdijk 07:48 | No data | — |
| Sun 6 Sept | Weert 09:31 | No data | — |
| Sat 5 Sept | Weert 09:31 | No data | — |
| Fri 4 Sept | Amsterdam Sloterdijk 07:48 | No data | — |
| Sun 30 Aug | Sittard 10:03 | No data | — |
| Sat 29 Aug | Sittard 10:12 | No data | — |
| Fri 28 Aug | Amsterdam Sloterdijk 07:48 | No data | — |
| Sun 23 Aug | Sittard 10:10 | No data | — |