Train NS 7670 Zutphen → Nijmegen

Zutphen 19:07 → Nijmegen 19:58 Daily 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

NS 7670 Zutphen–Nijmegen: final delay under 3 min on 17 of its 20 runs with data in the last 30 days (85%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 12:50 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November +4 min

Next service: today 19:07 from Zutphen · Sun 22 Nov

Next departure 19:07 today · Zutphen
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 14 full · 6 partial · 9 no data
On-time · 90 days
73%
22/30 runs under 3 min
RT coverage: 22 full · 8 partial · 32 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +3 min

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

  • Sun 1 Nov Max en route +28 min · last fix heading to Arnhem Centraal +28 min
  • Sat 10 Oct Max en route +12 min · last fix heading to Nijmegen Lent +9 min
  • Fri 9 Oct Max en route +8 min · last fix heading to — +8 min
  • Thu 8 Oct Max en route +7 min · last fix heading to — +7 min
  • Fri 23 Oct Max en route +6 min · last fix heading to Velp +6 min

Distribution · 90 days

30 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 73% · 22
  • 3–10 min 23% · 7
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 75% T n=4
  • 40% F n=5
  • 60% S n=5
  • 60% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 stops).

Last 90 days, 30 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.

StopSched.Usually 9 days in 10
19:07on time on time
19:12≈ on time ≈ +1 min
19:17 / 19:19≈ on time ≈ +2 min
19:24≈ on time ≈ +3 min
19:28≈ on time ≈ +3 min
19:31≈ on time ≈ +4 min
19:34 / 19:35≈ on time ≈ +4 min
19:37 / 19:41≈ on time ≈ +5 min
19:46≈ on time ≈ +6 min
19:50≈ +1 min ≈ +7 min
19:55≈ +1 min ≈ +8 min
19:58+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

DateLast stopFinalMax
Sat 21 NovNijmegen Lent 20:13Partial coverage+4 min+4 min
Fri 20 NovBrummen 20:04Partial coverage+3 min+3 min
Thu 19 Nov— 20:02+1 min+2 min
Wed 18 Nov— 19:590 min—
Tue 17 Nov— 19:180 min—
Mon 16 Nov— 19:590 min—
Sun 15 NovNijmegen Lent 20:09Partial coverage+1 min+2 min
Sat 14 NovNijmegen Lent 20:09Partial coverage0 min—
Fri 13 Nov— 19:59+2 min+2 min
Thu 12 Nov— 19:590 min—
Wed 11 Nov— 19:59+1 min+1 min
Tue 10 Nov— 19:590 min—
Mon 9 Nov— 19:590 min—
Sun 8 NovNijmegen Lent 20:09Partial coverage0 min—
Sat 7 NovNijmegen Lent 20:09Partial coverage0 min—
Fri 6 Nov— 19:590 min—
Thu 5 Nov— 20:08No data—
Wed 4 Nov— 19:59+1 min+1 min
Tue 3 Nov— 19:59No data—
Mon 2 Nov— 19:38No data—
Sun 1 NovArnhem Centraal 20:52+28 min+28 min
Sat 31 OctNijmegen Lent 20:11+2 min+3 min
Fri 30 Oct— 19:59No data—
Thu 29 Oct— 19:340 min—
Wed 28 Oct— 19:59No data—
Tue 27 Oct— 20:12No data—
Mon 26 OctElst 19:59No data—
Sun 25 OctNijmegen Lent 20:09No data—
Sat 24 OctNijmegen Lent 20:09No data—
Fri 23 OctVelp 20:12+6 min+6 min