Train NS 7613 Nijmegen – Zutphen
✓ Today’s run finished
Today, last fix heading to Brummen at 06:37 No data
- Nijmegen05:33
- Elst05:41
- Arnhem Centraal05:50
- Arnhem Presikhaaf06:01
- Velp06:04
- Brummen06:18
- Zutphen06:24
Next service: Monday 05:33 from Nijmegen · Mon 9 Nov
Last 30 days
Arrival delay at Zutphen, 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 3 Nov Max en route +5 min · last fix heading to Brummen +5 min
- Fri 30 Oct Max en route +4 min · last fix heading to Brummen +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 91% · 20
- 3–10 min 9% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 80% T n=5
- 100% W n=5
- 100% T n=5
- 75% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 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 |
|---|---|---|---|
| 05:33 | on time | on time | |
| 05:36 | ≈ on time | ≈ on time | |
| 05:41 | ≈ on time | ≈ +1 min | |
| 05:45 | ≈ on time | ≈ +1 min | |
| 05:50 / 05:55 | ≈ on time | ≈ +1 min | |
| 05:57 | ≈ +1 min | ≈ +2 min | |
| 06:01 | ≈ +1 min | ≈ +2 min | |
| 06:04 | ≈ +1 min | ≈ +2 min | |
| 06:08 | ≈ +1 min | ≈ +2 min | |
| 06:13 / 06:14 | ≈ +1 min | ≈ +3 min | |
| 06:18 | ≈ +1 min | ≈ +3 min | |
| 06:24 | +1 min | +4 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 | Brummen 06:37 | No data | — |
| Thu 5 Nov | Brummen 06:34Partial coverage | 0 min | — |
| Wed 4 Nov | Brummen 06:34Partial coverage | +2 min | +2 min |
| Tue 3 Nov | Brummen 06:38Partial coverage | +5 min | +5 min |
| Mon 2 Nov | Brummen 06:34 | No data | — |
| Fri 30 Oct | Brummen 06:36 | +4 min | +4 min |
| Thu 29 Oct | Brummen 06:34Partial coverage | 0 min | — |
| Wed 28 Oct | Brummen 06:34Partial coverage | +1 min | +1 min |
| Tue 27 Oct | Brummen 06:34Partial coverage | 0 min | — |
| Mon 26 Oct | Brummen 06:34 | +1 min | +1 min |
| Fri 23 Oct | Brummen 06:34 | +1 min | +1 min |
| Thu 22 Oct | Brummen 06:34Partial coverage | 0 min | — |
| Wed 21 Oct | Brummen 06:34Partial coverage | 0 min | — |
| Tue 20 Oct | Brummen 06:34Partial coverage | 0 min | — |
| Mon 19 Oct | Brummen 06:34 | +1 min | +1 min |
| Fri 16 Oct | Brummen 06:34 | 0 min | — |
| Thu 15 Oct | Brummen 06:34Partial coverage | +2 min | +2 min |
| Wed 14 Oct | Brummen 06:34Partial coverage | 0 min | — |
| Tue 13 Oct | Brummen 06:35Partial coverage | +1 min | +1 min |
| Mon 12 Oct | Brummen 06:35 | +2 min | +2 min |
| Fri 9 Oct | Brummen 06:35 | +3 min | +3 min |
| Thu 8 Oct | Brummen 06:35Partial coverage | +2 min | +2 min |
| Wed 7 Oct | Brummen 06:34Partial coverage | 0 min | — |
| Tue 6 Oct | Brummen 06:34Partial coverage | 0 min | — |
| Mon 5 Oct | Brummen 06:35 | No data | — |
| Fri 2 Oct | Brummen 06:35 | No data | — |
| Thu 1 Oct | Brummen 06:35 | No data | — |
| Wed 30 Sept | Brummen 06:34 | No data | — |
| Tue 29 Sept | Brummen 06:34 | No data | — |
| Mon 28 Sept | Brummen 06:32 | No data | — |