Train NS 7681 Nijmegen – Arnhem Centraal

Nijmegen 22:33 → Arnhem Centraal 22:50 Daily 0 h 17 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 22:33 from Nijmegen · Sun 8 Nov

Next departure 22:33 today · Nijmegen
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 9 full · 5 partial · 13 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 14 full · 5 partial · 29 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: +2 min

Last 30 days

Arrival delay at Arnhem Centraal, 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 9 Oct Max en route +7 min · last fix heading to — +7 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 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 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
22:33on time +1 min
22:36≈ on time ≈ +4 min
22:41≈ on time ≈ +4 min
22:45≈ on time ≈ +4 min
22:50on 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
Sat 7 NovArnhem Zuid 22:59Partial coverage0 min—
Fri 6 Nov— 22:52+1 min—
Thu 5 Nov— 22:49No data—
Wed 4 Nov— 22:490 min—
Mon 2 Nov— 22:490 min—
Sun 1 NovArnhem Zuid 22:59Partial coverage0 min—
Sat 31 OctArnhem Zuid 23:03Partial coverage0 min—
Thu 29 Oct— 22:55+2 min+2 min
Wed 28 Oct— 22:53No data—
Tue 27 Oct— 22:54No data—
Mon 26 Oct— 22:51No data—
Sun 25 OctArnhem Zuid 23:05No data—
Sat 24 OctNijmegen Lent 22:53No data—
Fri 23 Oct— 23:01+5 min+5 min
Thu 22 Oct— 22:52No data—
Wed 21 Oct— 22:51No data—
Tue 20 Oct— 23:10No data—
Mon 19 Oct— 22:530 min—
Sun 18 OctArnhem Zuid 23:01Partial coverage+1 min+1 min
Sat 17 OctArnhem Zuid 23:05No data—
Fri 16 Oct— 22:53+1 min+1 min
Thu 15 Oct— 22:53No data—
Wed 14 Oct— 22:51No data—
Tue 13 Oct— 23:00No data—
Mon 12 Oct— 22:510 min—
Sun 11 OctArnhem Zuid 23:00Partial coverage0 min—
Sat 10 Oct— 22:52+2 min+2 min
Fri 9 Oct— 23:04+7 min+7 min
Thu 8 Oct— 22:56+2 min+2 min
Wed 7 Oct— 22:510 min—