Train NS 7627 Nijmegen → Zutphen

Nijmegen 09:03 → Zutphen 09:54 Daily 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

NS 7627 Nijmegen–Zutphen: final delay under 3 min on 21 of its 24 runs with data in the last 30 days (88%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 22:58 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Brummen at 10:04 +2 min

  1. Nijmegen09:03
  2. Elst09:11
  3. Arnhem Centraal09:20
  4. Arnhem Presikhaaf09:31
  5. Velp09:34
  6. Brummen09:48
  7. Zutphen09:54

Next service: tomorrow 09:03 from Nijmegen · Mon 23 Nov

Next departure 09:03 tomorrow · Nijmegen
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 20 full · 4 partial · 6 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 29 full · 6 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Sat 21 Nov Max en route +6 min · last fix heading to Brummen +6 min
  • Thu 19 Nov Max en route +5 min · last fix heading to Brummen +5 min
  • Sat 14 Nov Max en route +3 min · last fix heading to Brummen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 32
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=6
  • 67% T n=3
  • 100% F n=3
  • 71% S n=7
  • 100% S n=6

Stops and timetable

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

Last 90 days, 35 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
09:03on time on time
09:06≈ on time ≈ on time
09:11≈ on time ≈ on time
09:15≈ on time ≈ +1 min
09:20 / 09:25≈ on time ≈ +1 min
09:27≈ on time ≈ +1 min
09:31≈ on time ≈ +1 min
09:34≈ on time ≈ +2 min
09:38≈ on time ≈ +2 min
09:43 / 09:44≈ on time ≈ +2 min
09:48≈ on time ≈ +2 min
09:54on time +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
Sun 22 NovBrummen 10:04Partial coverage+2 min+2 min
Sat 21 NovBrummen 10:09+6 min+6 min
Fri 20 NovBrummen 10:040 min—
Thu 19 NovBrummen 10:08+5 min+5 min
Wed 18 NovBrummen 10:120 min+8 min
Tue 17 NovBrummen 10:04+3 min+3 min
Mon 16 NovBrummen 10:04+1 min—
Sun 15 NovBrummen 10:02Partial coverage0 min—
Sat 14 NovBrummen 10:04+3 min+3 min
Fri 13 NovBrummen 10:040 min—
Thu 12 NovBrummen 10:020 min—
Wed 11 NovBrummen 10:040 min—
Tue 10 NovBrummen 10:04+2 min+2 min
Mon 9 NovBrummen 10:04+1 min—
Sun 8 NovBrummen 10:04Partial coverage+1 min—
Sat 7 NovBrummen 10:04+1 min+1 min
Fri 6 NovBrummen 10:04No data—
Thu 5 NovBrummen 10:04No data—
Wed 4 NovBrummen 10:040 min—
Tue 3 NovBrummen 10:040 min—
Mon 2 NovBrummen 10:120 min—
Sun 1 NovBrummen 10:05Partial coverage0 min—
Sat 31 OctBrummen 10:050 min—
Fri 30 OctBrummen 10:04No data—
Thu 29 OctBrummen 10:04No data—
Wed 28 OctBrummen 10:040 min—
Tue 27 OctBrummen 10:04No data—
Mon 26 OctBrummen 10:040 min—
Sun 25 OctBrummen 10:06No data—
Sat 24 OctBrummen 10:040 min—