Train NS 7673 Nijmegen – Zutphen

Nijmegen 20:33 → Zutphen 21:24 Daily 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +4 min

Next service: today 20:33 from Nijmegen · Thu 5 Nov

Next departure 20:33 today · Nijmegen
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 14 full · 3 partial · 12 no data
On-time · 90 days
84%
16/19 runs under 3 min
RT coverage: 16 full · 3 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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 23 Oct Max en route +7 min · last fix heading to — +7 min
  • Fri 16 Oct Max en route +4 min · last fix heading to — +4 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 16
  • 3–10 min 16% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 50% W n=2
  • 100% T n=2
  • 33% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 19 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
20:33on time on time
20:36≈ on time ≈ on time
20:41≈ on time ≈ +1 min
20:45≈ on time ≈ +1 min
20:50 / 20:55≈ on time ≈ +1 min
20:57≈ on time ≈ +2 min
21:01≈ on time ≈ +2 min
21:04≈ on time ≈ +2 min
21:08≈ on time ≈ +3 min
21:13 / 21:14≈ on time ≈ +3 min
21:18≈ on time ≈ +3 min
21:24on time +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

DateLast stopFinalMax
Wed 4 Nov— 21:32+4 min+4 min
Tue 3 Nov— 21:240 min—
Mon 2 Nov— 21:240 min—
Sun 1 NovArnhem Zuid 20:590 min—
Sat 31 OctBrummen 21:35Partial coverage0 min—
Fri 30 Oct— 21:34No data—
Thu 29 Oct— 21:25+2 min+2 min
Wed 28 Oct— 21:28No data—
Tue 27 Oct— 21:26No data—
Mon 26 Oct— 21:310 min—
Sun 25 OctArnhem Zuid 21:00No data—
Sat 24 OctBrummen 21:32No data—
Fri 23 Oct— 21:34+7 min+7 min
Thu 22 Oct— 21:25No data—
Wed 21 Oct— 21:25No data—
Tue 20 Oct— 21:21No data—
Mon 19 Oct— 21:26No data—
Sun 18 OctArnhem Zuid 21:02+1 min+1 min
Sat 17 OctBrummen 21:35Partial coverage0 min—
Fri 16 Oct— 21:32+4 min+4 min
Thu 15 Oct— 21:29No data—
Wed 14 Oct— 21:25No data—
Tue 13 Oct— 21:28No data—
Mon 12 Oct— 21:250 min—
Sun 11 OctArnhem Zuid 21:02+2 min+2 min
Sat 10 OctBrummen 21:32Partial coverage0 min—
Fri 9 Oct— 21:210 min+1 min
Thu 8 Oct— 21:250 min—
Wed 7 Oct— 21:250 min—
Tue 6 Oct— 21:240 min—