Train NS 7614 Arnhem Centraal – Nijmegen

Arnhem Centraal 05:41 → Nijmegen 05:59 Mon, Tue, Wed, Thu, Fri 0 h 18 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Nijmegen Lent at 06:09 No data

  1. Arnhem Centraal05:41
  2. Arnhem Zuid05:47
  3. Elst05:51
  4. Nijmegen Lent05:56
  5. Nijmegen05:59

Next service: Monday 05:41 from Arnhem Centraal · Mon 9 Nov

Next departure 05:41 Monday · Arnhem Centraal
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 20 full · 1 partial · 1 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 40 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: +3 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 13 Oct Max en route +4 min · last fix heading to Nijmegen Lent +4 min
  • Wed 14 Oct Max en route +3 min · last fix heading to Nijmegen Lent +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 91% · 21
  • 3–10 min 9% · 2
  • 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
  • 100% 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 (5 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
05:41on time on time
05:47≈ on time ≈ +1 min
05:51≈ on time ≈ +2 min
05:56≈ on time ≈ +2 min
05: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
Fri 6 NovNijmegen Lent 06:09No data—
Thu 5 NovNijmegen Lent 06:09Partial coverage+2 min+2 min
Wed 4 NovNijmegen Lent 06:09+1 min+1 min
Tue 3 NovNijmegen Lent 06:09+3 min+3 min
Mon 2 NovNijmegen Lent 06:090 min—
Fri 30 OctNijmegen Lent 06:10+1 min+1 min
Thu 29 OctNijmegen Lent 06:100 min—
Wed 28 OctNijmegen Lent 06:090 min—
Tue 27 OctNijmegen Lent 06:100 min—
Mon 26 OctNijmegen Lent 06:11+2 min+2 min
Fri 23 OctNijmegen Lent 06:11+2 min+2 min
Thu 22 OctNijmegen Lent 06:100 min—
Wed 21 OctNijmegen Lent 06:100 min—
Tue 20 OctNijmegen Lent 06:100 min—
Mon 19 OctNijmegen Lent 06:11+1 min+1 min
Fri 16 OctNijmegen Lent 06:100 min—
Thu 15 OctNijmegen Lent 06:100 min—
Wed 14 OctNijmegen Lent 06:11+3 min+3 min
Tue 13 OctNijmegen Lent 06:12+4 min+4 min
Mon 12 OctNijmegen Lent 06:090 min—
Fri 9 OctNijmegen Lent 06:100 min—
Thu 8 OctNijmegen Lent 06:100 min—
Wed 7 OctNijmegen Lent 06:090 min—
Tue 6 OctNijmegen Lent 06:09+2 min+2 min
Mon 5 OctNijmegen Lent 06:09No data—
Fri 2 OctNijmegen Lent 06:11No data—
Thu 1 OctNijmegen Lent 06:11No data—
Wed 30 SeptNijmegen Lent 06:09No data—
Tue 29 SeptNijmegen Lent 06:09No data—
Mon 28 SeptNijmegen Lent 06:09No data—