Train NS 7618 Arnhem Centraal – Nijmegen

Arnhem Centraal 06:41 → Nijmegen 06:59 Daily 0 h 18 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November +1 min

Next service: today 06:41 from Arnhem Centraal · Sun 15 Nov

Next departure 06:41 today · Arnhem Centraal
On-time · 30 days
81%
22/27 runs under 3 min
RT coverage: 23 full · 4 partial · 2 no data
On-time · 90 days
87%
33/38 runs under 3 min
RT coverage: 33 full · 5 partial · 48 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Tue 3 Nov Max en route +23 min · last fix heading to Nijmegen Dukenburg +23 min
  • Mon 19 Oct Max en route +8 min · last fix heading to Nijmegen Dukenburg +6 min
  • Tue 10 Nov Max en route +6 min · last fix heading to Nijmegen Dukenburg +6 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Nijmegen Dukenburg +3 min
  • Wed 11 Nov Max en route +3 min · last fix heading to Nijmegen Dukenburg +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 33
  • 3–10 min 11% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 67% T n=6
  • 67% W n=6
  • 100% T n=6
  • 100% F n=5
  • 100% S n=6
  • 100% S n=4

Stops and timetable

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

Last 90 days, 38 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:41on time on time
06:46≈ on time ≈ +1 min
06:50≈ on time ≈ +2 min
06:55≈ on time ≈ +2 min
06:59on 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
Sat 14 NovNijmegen Lent 07:09Partial coverage+1 min+1 min
Fri 13 NovNijmegen Dukenburg 07:220 min—
Thu 12 NovNijmegen Dukenburg 07:220 min—
Wed 11 NovNijmegen Dukenburg 07:24+3 min+3 min
Tue 10 NovNijmegen Dukenburg 07:27+6 min+6 min
Mon 9 NovNijmegen Dukenburg 07:220 min—
Sun 8 NovNijmegen Lent 07:09+1 min+1 min
Sat 7 NovNijmegen Lent 07:09Partial coverage0 min—
Fri 6 NovNijmegen Dukenburg 07:19No data—
Thu 5 NovNijmegen Dukenburg 07:240 min—
Wed 4 NovNijmegen Dukenburg 07:24+3 min+3 min
Tue 3 NovNijmegen Dukenburg 07:38+23 min+23 min
Mon 2 NovNijmegen Dukenburg 07:240 min—
Sun 1 NovNijmegen Lent 07:090 min—
Sat 31 OctNijmegen Lent 07:10Partial coverage0 min—
Fri 30 OctNijmegen Dukenburg 07:22+1 min+1 min
Thu 29 OctNijmegen Dukenburg 07:220 min—
Wed 28 OctNijmegen Dukenburg 07:210 min—
Tue 27 OctNijmegen Dukenburg 07:210 min—
Mon 26 OctNijmegen Dukenburg 07:210 min—
Sun 25 OctNijmegen Lent 07:09No data—
Sat 24 OctNijmegen Lent 07:100 min—
Fri 23 OctNijmegen Dukenburg 07:210 min—
Thu 22 OctNijmegen Dukenburg 07:210 min—
Wed 21 OctNijmegen Dukenburg 07:210 min—
Tue 20 OctNijmegen Dukenburg 07:210 min—
Mon 19 OctNijmegen Dukenburg 07:26+6 min+8 min
Sun 18 OctNijmegen Lent 07:100 min—
Sat 17 OctNijmegen Lent 07:10Partial coverage0 min—
Fri 16 OctNijmegen Dukenburg 07:220 min—