Train Arriva 32241 Nijmegen – Roermond

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 12:08 from Nijmegen · Tue 17 Nov

Next departure 12:08 today · Nijmegen
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 7 full · 10 partial · 12 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 9 full · 16 partial · 62 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: +3 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

  • Wed 11 Nov Max en route +8 min · last fix heading to Swalmen +7 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Swalmen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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
12:08on time on time
12:11≈ on time ≈ on time
12:16≈ on time ≈ on time
12:20 / 12:22≈ on time ≈ on time
12:29 / 12:32≈ on time ≈ +1 min
12:37 / 12:38≈ on time ≈ +1 min
12:44 / 12:45≈ on time ≈ +1 min
12:58≈ on time ≈ +1 min
13:01 / 13:03≈ on time ≈ +1 min
13:08≈ on time ≈ +1 min
13:14 / 13:15≈ on time ≈ +1 min
13:20≈ on time ≈ +1 min
13:26on time +1 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
Mon 16 NovSwalmen 13:43Partial coverage0 min+8 min
Sun 15 NovBlerick 13:15+2 min+2 min
Sat 14 NovSwalmen 13:34Partial coverage0 min—
Fri 13 NovSwalmen 13:37Partial coverage+2 min+3 min
Thu 12 NovSwalmen 13:38Partial coverage+3 min+4 min
Wed 11 NovSwalmen 13:42Partial coverage+7 min+8 min
Tue 10 NovSwalmen 13:34Partial coverage+1 min+1 min
Mon 9 NovSwalmen 13:39Partial coverage0 min+8 min
Sun 8 NovBlerick 13:120 min—
Sat 7 NovSwalmen 13:34Partial coverage0 min—
Fri 6 NovSwalmen 13:34No data—
Thu 5 NovSwalmen 13:34No data—
Wed 4 NovSwalmen 13:34Partial coverage+1 min+2 min
Tue 3 NovSwalmen 13:34No data—
Mon 2 NovSwalmen 13:34No data—
Sun 1 NovSwalmen 13:37+1 min+1 min
Sat 31 OctSwalmen 13:350 min—
Fri 30 OctSwalmen 13:35No data—
Thu 29 OctSwalmen 13:41No data—
Wed 28 OctSwalmen 13:350 min—
Tue 27 OctSwalmen 13:39Partial coverage0 min—
Mon 26 OctSwalmen 13:34No data—
Sun 25 OctSwalmen 13:36No data—
Sat 24 OctSwalmen 13:350 min+1 min
Fri 23 OctSwalmen 13:34No data—
Thu 22 OctSwalmen 13:35No data—
Wed 21 OctSwalmen 13:34No data—
Tue 20 OctSwalmen 13:340 min—
Mon 19 OctSwalmen 13:36No data—
Sun 18 OctSwalmen 13:350 min—