Train NS 7613 Nijmegen → Zutphen

Nijmegen 05:33 → Zutphen 06:24 Mon, Tue, Wed, Thu, Fri 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

NS 7613 Nijmegen–Zutphen: final delay under 3 min on 13 of its 18 runs with data in the last 30 days (72%). Median final delay: +2 min. TrainsRadar data as of 23 Nov 2026, 00:41 (GMT+1).

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 05:33 from Nijmegen · Mon 23 Nov

Next departure 05:33 today · Nijmegen
On-time · 30 days
72%
13/18 runs under 3 min
RT coverage: 15 full · 3 partial · 2 no data
On-time · 90 days
84%
27/32 runs under 3 min
RT coverage: 26 full · 6 partial · 30 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 min

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

  • Fri 13 Nov Max en route +16 min · last fix heading to Brummen +16 min
  • Wed 18 Nov Max en route +6 min · last fix heading to Brummen +6 min
  • 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
  • Tue 17 Nov Max en route +4 min · last fix heading to Brummen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 27
  • 3–10 min 13% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 71% T n=7
  • 86% W n=7
  • 100% T n=7
  • 67% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 32 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
05:33on time on time
05:37≈ on time ≈ on time
05:41≈ on time ≈ +1 min
05:45≈ on time ≈ +1 min
05:50 / 05:55≈ on time ≈ +2 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 +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

DateLast stopFinalMax
Fri 20 NovBrummen 06:34Partial coverage0 min—
Thu 19 NovBrummen 06:34+3 min+3 min
Wed 18 NovBrummen 06:34+6 min+6 min
Tue 17 NovBrummen 06:34+4 min+4 min
Mon 16 NovBrummen 06:340 min—
Fri 13 NovBrummen 06:49Partial coverage+16 min+16 min
Thu 12 NovBrummen 06:34+1 min+1 min
Wed 11 NovBrummen 06:34+2 min+2 min
Tue 10 NovBrummen 06:34+1 min+1 min
Mon 9 NovBrummen 06:34+3 min+3 min
Fri 6 NovBrummen 06:37No data—
Thu 5 NovBrummen 06:340 min—
Wed 4 NovBrummen 06:34+2 min+2 min
Tue 3 NovBrummen 06:38+5 min+5 min
Mon 2 NovBrummen 06:34No data—
Fri 30 OctBrummen 06:36Partial coverage+4 min+4 min
Thu 29 OctBrummen 06:340 min—
Wed 28 OctBrummen 06:34+1 min+1 min
Tue 27 OctBrummen 06:340 min—
Mon 26 OctBrummen 06:34+1 min+1 min
Fri 23 OctBrummen 06:34Partial coverage+1 min+1 min
Thu 22 OctBrummen 06:340 min—
Wed 21 OctBrummen 06:340 min—
Tue 20 OctBrummen 06:340 min—
Mon 19 OctBrummen 06:34+1 min+1 min
Fri 16 OctBrummen 06:34Partial coverage0 min—
Thu 15 OctBrummen 06:34+2 min+2 min
Wed 14 OctBrummen 06:340 min—
Tue 13 OctBrummen 06:35+1 min+1 min
Mon 12 OctBrummen 06:35+2 min+2 min