Train Arriva 32221 Nijmegen – Roermond

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

✓ Today’s run finished

Today, last fix heading to Swalmen at 08:34 0 min

  1. Nijmegen07:08
  2. Mook-Molenhoek07:16
  3. Boxmeer07:29
  4. Venray07:44
  5. Venlo08:01
  6. Swalmen08:20
  7. Roermond08:26

Next service: tomorrow 07:08 from Nijmegen · Fri 20 Nov

Next departure 07:08 tomorrow · Nijmegen
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 5 full · 16 partial · 9 no data
On-time · 90 days
88%
28/32 runs under 3 min
RT coverage: 11 full · 21 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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
  • Sat 14 Nov Max en route +6 min · last fix heading to Blerick +6 min
  • Tue 17 Nov Max en route +4 min · last fix heading to Swalmen +4 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Swalmen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 28
  • 3–10 min 13% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 83% T n=6
  • 100% W n=5
  • 100% T n=5
  • 67% F n=3
  • 83% S n=6
  • 67% S n=3

Stops and timetable

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

Last 90 days, 32 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
07:08on time on time
07:11≈ on time ≈ on time
07:16≈ on time ≈ +1 min
07:20 / 07:22≈ on time ≈ +1 min
07:29 / 07:32≈ on time ≈ +2 min
07:37 / 07:38≈ on time ≈ +2 min
07:44 / 07:45≈ on time ≈ +3 min
07:58≈ on time ≈ +4 min
08:01 / 08:03≈ on time ≈ +4 min
08:08≈ on time ≈ +4 min
08:14 / 08:15≈ on time ≈ +5 min
08:20≈ on time ≈ +5 min
08:26on time +6 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
Thu 19 NovSwalmen 08:34Partial coverage0 min+1 min
Wed 18 NovSwalmen 08:34Partial coverage0 min+6 min
Tue 17 NovSwalmen 08:39Partial coverage+4 min+4 min
Mon 16 NovSwalmen 08:34Partial coverage+1 min+1 min
Sun 15 NovSwalmen 08:37+1 min+3 min
Sat 14 NovBlerick 08:18+6 min+6 min
Fri 13 NovSwalmen 08:37Partial coverage+2 min+3 min
Thu 12 NovSwalmen 08:34Partial coverage+2 min+2 min
Wed 11 NovSwalmen 08:34Partial coverage0 min—
Tue 10 NovSwalmen 08:34Partial coverage+1 min+2 min
Mon 9 NovSwalmen 08:34Partial coverage0 min—
Sun 8 NovSwalmen 08:34No data—
Sat 7 NovBlerick 08:120 min—
Fri 6 NovSwalmen 08:34No data—
Thu 5 NovSwalmen 08:37No data—
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—