Train NS 7649 Nijmegen → Arnhem Centraal
NS 7649 Nijmegen–Arnhem Centraal: final delay under 3 min on 19 of its 21 runs with data in the last 30 days (90%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 14:32 (GMT+1).
An alert on this phone or computer when the 7649 is 5 min or more late, every day it runs. No account, no email.
Running now · updated 14:31
Heading to Arnhem Centraal No data
Estimated arrival at Arnhem Centraal 14:50 · 0 km/h
- Nijmegen14:33
- Nijmegen Lent14:36
- Elst14:41
- Arnhem Zuid14:45
- Arnhem Centraal14:50
Last 30 days
Arrival delay at Arnhem Centraal, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 19 Nov Max en route +4 min · last fix heading to Brummen +4 min
- Mon 16 Nov Max en route +3 min · last fix heading to Brummen +3 min
Distribution · 90 days
33 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 31
- 3–10 min 6% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 80% M n=5
- 100% T n=5
- 100% W n=6
- 67% T n=3
- 100% F n=3
- 100% S n=6
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 33 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 | Today |
|---|---|---|---|---|
| 14:33 | on time | on time | ||
| 14:36 | ≈ on time | ≈ +1 min | ||
| 14:41 | ≈ +1 min | ≈ +1 min | ||
| 14:45 | ≈ +1 min | ≈ +2 min | ||
| 14:50 | +1 min | +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 |
|---|---|---|---|
| Sun 22 Nov | Nijmegen 14:29Partial coverage | No data | — |
| Sat 21 Nov | Brummen 15:34 | +2 min | +2 min |
| Fri 20 Nov | Brummen 15:34 | +1 min | +1 min |
| Thu 19 Nov | Brummen 15:34 | +4 min | +4 min |
| Wed 18 Nov | Brummen 15:34 | +3 min | +3 min |
| Tue 17 Nov | Brummen 15:34 | 0 min | — |
| Mon 16 Nov | Brummen 15:34 | +3 min | +3 min |
| Sun 15 Nov | Arnhem Zuid 15:00Partial coverage | 0 min | — |
| Sat 14 Nov | Brummen 15:34 | 0 min | — |
| Fri 13 Nov | Brummen 15:34 | +2 min | +2 min |
| Thu 12 Nov | Brummen 15:34 | +3 min | +3 min |
| Wed 11 Nov | Brummen 15:34 | 0 min | — |
| Tue 10 Nov | Brummen 15:34 | +1 min | +1 min |
| Mon 9 Nov | Brummen 15:34 | 0 min | — |
| Sun 8 Nov | Arnhem Zuid 14:59Partial coverage | 0 min | — |
| Sat 7 Nov | Brummen 15:34 | 0 min | — |
| Fri 6 Nov | Brummen 15:34 | No data | — |
| Thu 5 Nov | Brummen 15:35 | No data | — |
| Wed 4 Nov | Brummen 15:34 | +1 min | +1 min |
| Tue 3 Nov | Brummen 15:34 | No data | — |
| Mon 2 Nov | Brummen 15:34 | No data | — |
| Sun 1 Nov | Arnhem Zuid 15:02Partial coverage | +1 min | +1 min |
| Sat 31 Oct | Brummen 15:35 | 0 min | — |
| Fri 30 Oct | Brummen 15:35 | No data | — |
| Thu 29 Oct | Brummen 15:34 | No data | — |
| Wed 28 Oct | Brummen 15:34 | 0 min | — |
| Tue 27 Oct | Brummen 15:34 | 0 min | — |
| Mon 26 Oct | Brummen 15:34 | No data | — |
| Sun 25 Oct | Arnhem Zuid 15:00 | No data | — |
| Sat 24 Oct | Brummen 15:34 | 0 min | — |