Train NS 2929 Den Helder – Nijmegen
It does not run today
Last recorded run: Friday 6 November No data
Next service: Friday 07:04 from Den Helder · Fri 13 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
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 100% · 9
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- 100% F n=3
- 100% 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 |
|---|---|---|---|
| 07:04 | on time | on time | |
| 07:08 | ≈ on time | ≈ on time | |
| 07:14 / 07:16 | ≈ on time | ≈ on time | |
| 07:22 | ≈ on time | ≈ on time | |
| 07:32 | ≈ on time | ≈ on time | |
| 07:37 | ≈ on time | ≈ on time | |
| 07:40 / 07:43 | ≈ on time | ≈ on time | |
| 07:49 | ≈ on time | ≈ on time | |
| 07:55 | ≈ on time | ≈ on time | |
| 08:08 | ≈ on time | ≈ +1 min | |
| 08:15 | ≈ on time | ≈ +1 min | |
| 08:21 / 08:27 | ≈ on time | ≈ +1 min | |
| 08:35 | ≈ on time | ≈ +1 min | |
| 08:39 / 08:40 | ≈ on time | ≈ +1 min | |
| 08:58 / 09:09 | ≈ on time | ≈ +1 min | |
| 09:27 | ≈ on time | ≈ +1 min | |
| 09:33 | ≈ on time | ≈ +1 min | |
| 09:43 / 09:50 | ≈ on time | ≈ +1 min | |
| 10:02 | on time | +2 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 | Amsterdam Sloterdijk 08:48 | No data | — |
| Sun 1 Nov | Arnhem Centraal 10:04Partial coverage | 0 min | — |
| Sat 31 Oct | Sittard 11:04 | 0 min | — |
| Fri 30 Oct | Amsterdam Sloterdijk 08:49 | 0 min | — |
| Sun 25 Oct | Sittard 11:04 | No data | — |
| Sun 18 Oct | Sittard 11:04 | 0 min | — |
| Sat 17 Oct | Sittard 11:05 | 0 min | — |
| Fri 16 Oct | Amsterdam Sloterdijk 08:48 | 0 min | — |
| Sun 11 Oct | Ede-Wageningen 09:52 | +2 min | +2 min |
| Sat 10 Oct | Sittard 11:04 | 0 min | +1 min |
| Fri 9 Oct | Amsterdam Sloterdijk 08:48 | +1 min | +1 min |
| Mon 5 Oct | Sittard 11:11 | No data | — |
| Sun 4 Oct | Sittard 11:02 | No data | — |
| Sat 3 Oct | Sittard 11:01 | No data | — |
| Fri 2 Oct | Amsterdam Sloterdijk 08:58 | No data | — |
| Sun 27 Sept | Sittard 11:02 | No data | — |
| Sat 26 Sept | Amsterdam Amstel 09:01 | No data | — |
| Fri 25 Sept | Amsterdam Sloterdijk 08:49 | No data | — |
| Sun 20 Sept | Utrecht Centraal 09:23 | No data | — |
| Sat 19 Sept | Utrecht Centraal 09:23 | No data | — |
| Fri 18 Sept | Amsterdam Sloterdijk 08:48 | No data | — |
| Sun 13 Sept | Sittard 11:02 | No data | — |
| Sat 12 Sept | Sittard 11:02 | No data | — |
| Fri 11 Sept | Amsterdam Sloterdijk 08:49 | No data | — |
| Sun 6 Sept | Weert 10:33 | No data | — |
| Sat 5 Sept | Weert 10:31 | No data | — |
| Fri 4 Sept | Amsterdam Sloterdijk 08:48 | No data | — |
| Sun 30 Aug | Sittard 11:01 | No data | — |
| Sat 29 Aug | Sittard 11:05 | No data | — |
| Fri 28 Aug | Amsterdam Sloterdijk 08:48 | No data | — |