Train Arriva 32260 Roermond – Nijmegen

Roermond 17:04 → Nijmegen 18:22 Daily 1 h 18 min · 13 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:04 from Roermond · Thu 5 Nov

Next departure 17:04 today · Roermond
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 14 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 5 full · 11 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
17:04on time +1 min
17:09≈ on time ≈ +1 min
17:14 / 17:15≈ on time ≈ +1 min
17:21≈ on time ≈ +1 min
17:27 / 17:29≈ on time ≈ +1 min
17:31≈ on time ≈ +1 min
17:44 / 17:45≈ +1 min ≈ +1 min
17:50 / 17:51≈ +1 min ≈ +1 min
17:56 / 18:00≈ +1 min ≈ +1 min
18:07 / 18:08≈ +1 min ≈ +2 min
18:12≈ +1 min ≈ +2 min
18:18≈ +1 min ≈ +2 min
18:22+1 min +2 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 NovMook-Molenhoek 18:24No data—
Tue 3 NovMook-Molenhoek 18:24Partial coverage0 min—
Mon 2 NovCuijk 18:22Partial coverage0 min—
Sun 1 NovTegelen 17:38+2 min+3 min
Sat 31 OctTegelen 17:37+1 min+1 min
Fri 30 OctNijmegen Heyendaal 18:32No data—
Thu 29 OctBoxmeer 18:14No data—
Wed 28 OctMook-Molenhoek 18:26Partial coverage0 min—
Tue 27 OctBoxmeer 18:14No data—
Mon 26 OctCuijk 18:22Partial coverage0 min—
Sun 25 OctTegelen 17:36No data—
Sat 24 OctTegelen 17:35No data—
Fri 23 OctTegelen 17:36No data—
Thu 22 OctTegelen 17:35No data—
Wed 21 OctTegelen 17:36No data—
Tue 20 OctTegelen 17:350 min—
Mon 19 OctTegelen 17:36No data—
Sun 18 OctTegelen 17:36+1 min—
Sat 17 OctTegelen 17:36No data—
Fri 16 OctNijmegen Heyendaal 18:36No data—
Thu 15 OctNijmegen Heyendaal 18:32No data—
Tue 13 OctNijmegen Heyendaal 18:32No data—
Mon 12 OctNijmegen Heyendaal 18:32Partial coverage0 min—
Sun 11 OctNijmegen Heyendaal 18:32Partial coverage0 min—
Sat 10 OctNijmegen Heyendaal 18:32Partial coverage0 min—
Fri 9 OctNijmegen Heyendaal 18:32Partial coverage0 min—
Thu 8 OctBoxmeer 18:140 min—
Wed 7 OctCuijk 18:22Partial coverage0 min—
Tue 6 OctBoxmeer 18:14Partial coverage+1 min+1 min
Mon 5 OctMook-Molenhoek 18:26Partial coverage0 min—