Train Arriva 32237 Nijmegen – Roermond

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 11:08 from Nijmegen · Wed 18 Nov

Next departure 11:08 today · Nijmegen
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 9 full · 7 partial · 13 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 10 full · 14 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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