Train NS 7615 Nijmegen – Zutphen

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 06:03 from Nijmegen · Fri 6 Nov

Next departure 06:03 today · Nijmegen
On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 1 full · 20 partial · 0 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 1 full · 22 partial · 40 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Tue 3 Nov Max en route +6 min · last fix heading to Brummen +6 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Brummen +4 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Brummen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 80% W n=5
  • 80% T n=5
  • 100% 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, 23 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
06:03on time on time
06:06— —
06:11— —
06:15— —
06:20 / 06:25— —
06:27— —
06:31— —
06:34— —
06:38— —
06:43 / 06:44— —
06:48— —
06:54— —

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
Thu 5 NovBrummen 07:04Partial coverage0 min—
Wed 4 NovBrummen 07:04Partial coverage+3 min+3 min
Tue 3 NovBrummen 07:08Partial coverage+6 min+6 min
Mon 2 NovBrummen 07:04Partial coverage0 min—
Fri 30 OctBrummen 07:05Partial coverage+2 min+2 min
Thu 29 OctBrummen 07:04Partial coverage0 min—
Wed 28 OctBrummen 07:04Partial coverage+1 min+1 min
Tue 27 OctBrummen 07:05Partial coverage+1 min+1 min
Mon 26 OctBrummen 07:04Partial coverage0 min—
Fri 23 OctBrummen 07:05Partial coverage+2 min+2 min
Thu 22 OctBrummen 07:04Partial coverage0 min—
Wed 21 OctBrummen 07:05Partial coverage+1 min+1 min
Tue 20 OctBrummen 07:04Partial coverage0 min—
Mon 19 OctBrummen 07:04Partial coverage0 min—
Fri 16 OctBrummen 07:04Partial coverage0 min—
Thu 15 OctBrummen 07:04Partial coverage+1 min+1 min
Wed 14 OctBrummen 07:05Partial coverage+2 min+2 min
Tue 13 OctBrummen 07:04Partial coverage0 min—
Mon 12 OctBrummen 07:05+1 min+1 min
Fri 9 OctBrummen 07:05Partial coverage+1 min+1 min
Thu 8 OctBrummen 07:07Partial coverage+4 min+4 min
Wed 7 OctBrummen 07:06Partial coverage+3 min+3 min
Tue 6 OctBrummen 07:04Partial coverage0 min—
Mon 5 OctBrummen 07:04No data—
Fri 2 OctBrummen 07:04No data—
Thu 1 OctBrummen 07:04No data—
Wed 30 SeptBrummen 07:04No data—
Tue 29 SeptBrummen 07:05No data—
Mon 28 SeptBrummen 07:04No data—
Fri 25 SeptBrummen 07:04No data—