Train Arriva 32221 Nijmegen – Roermond

Nijmegen 07:08 → Roermond 08:26 Daily 1 h 18 min · 13 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 07:08 from Nijmegen · Thu 5 Nov

Full trip card
Next departure 07:08 today · Nijmegen
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 8 full · 11 partial · 9 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 8 full · 12 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Roermond, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 18 Oct Max en route +8 min · last fix heading to Swalmen +7 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Swalmen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
Nijmegen
07:08on time on time
Nijmegen Heyendaal
07:11≈ on time ≈ +1 min
Mook-Molenhoek
07:16≈ on time ≈ +1 min
Cuijk
07:20 / 07:22≈ on time ≈ +1 min
Boxmeer
07:29 / 07:32≈ on time ≈ +2 min
Vierlingsbeek
07:37 / 07:38≈ on time ≈ +2 min
Venray
07:44 / 07:45≈ on time ≈ +2 min
Blerick
07:58≈ on time ≈ +3 min
Venlo
08:01 / 08:03≈ on time ≈ +3 min
Tegelen
08:08≈ on time ≈ +3 min
Reuver
08:14 / 08:15≈ on time ≈ +3 min
Swalmen
08:20≈ on time ≈ +3 min
Roermond
08:26on 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
Wed 4 NovSwalmen 08:34Partial coverage0 min+1 min
Tue 3 NovSwalmen 08:38Partial coverage0 min—
Mon 2 NovSwalmen 08:37No data—
Sun 1 NovSwalmen 08:34No data—
Sat 31 OctSwalmen 08:37+2 min+3 min
Fri 30 OctSwalmen 08:36Partial coverage0 min—
Thu 29 OctSwalmen 08:38Partial coverage0 min—
Wed 28 OctSwalmen 08:40Partial coverage0 min—
Tue 27 OctSwalmen 08:37Partial coverage0 min—
Mon 26 OctSwalmen 08:35Partial coverage0 min—
Sun 25 OctSwalmen 08:34No data—
Sat 24 OctSwalmen 08:350 min—
Fri 23 OctSwalmen 08:36No data—
Thu 22 OctSwalmen 08:36No data—
Wed 21 OctSwalmen 08:36No data—
Tue 20 OctSwalmen 08:340 min—
Mon 19 OctSwalmen 08:350 min—
Sun 18 OctSwalmen 08:42+7 min+8 min
Sat 17 OctSwalmen 08:350 min+2 min
Fri 16 OctSwalmen 08:36No data—
Thu 15 OctSwalmen 08:37Partial coverage0 min—
Tue 13 OctSwalmen 08:37No data—
Mon 12 OctSwalmen 08:37No data—
Sun 11 OctSwalmen 08:340 min—
Sat 10 OctBlerick 08:120 min—
Fri 9 OctSwalmen 08:39Partial coverage+4 min+4 min
Thu 8 OctSwalmen 08:46Partial coverage0 min—
Wed 7 OctSwalmen 08:36Partial coverage+1 min+1 min
Tue 6 OctSwalmen 08:35Partial coverage0 min+1 min
Mon 5 OctSwalmen 08:35No data—