Train Arriva 32215 Nijmegen – Roermond

Nijmegen 05:38 → Roermond 06:56 Mon, Tue, Wed, Thu, Fri, Sat 1 h 18 min · 13 stops Arriva

✓ Today’s run finished

Today, last fix heading to Swalmen at 07:07 No data

  1. Nijmegen05:38
  2. Mook-Molenhoek05:46
  3. Boxmeer06:00
  4. Venray06:14
  5. Venlo06:31
  6. Swalmen06:50
  7. Roermond06:56

Next service: tomorrow 05:38 from Nijmegen · Sat 7 Nov

Next departure 05:38 tomorrow · Nijmegen
On-time · 30 days
81%
17/21 runs under 3 min
RT coverage: 9 full · 12 partial · 4 no data
On-time · 90 days
83%
19/23 runs under 3 min
RT coverage: 9 full · 14 partial · 48 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Mon 26 Oct Max en route +16 min · last fix heading to Swalmen +16 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Swalmen +4 min
  • Thu 15 Oct Max en route +4 min · last fix heading to Swalmen +4 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Swalmen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 19
  • 3–10 min 13% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=5
  • 67% W n=3
  • 80% T n=5
  • 67% F n=3
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
05:38on time on time
05:41≈ on time ≈ on time
05:46≈ on time ≈ +1 min
05:50 / 05:52≈ on time ≈ +1 min
06:00 / 06:02≈ on time ≈ +1 min
06:07 / 06:08≈ on time ≈ +2 min
06:14 / 06:15≈ on time ≈ +2 min
06:28≈ on time ≈ +3 min
06:31 / 06:33≈ on time ≈ +3 min
06:38≈ on time ≈ +4 min
06:44 / 06:45≈ on time ≈ +4 min
06:50≈ +1 min ≈ +5 min
06:56+1 min +5 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
Fri 6 NovSwalmen 07:07No data—
Thu 5 NovSwalmen 07:04Partial coverage0 min—
Wed 4 NovSwalmen 07:09Partial coverage+4 min+5 min
Tue 3 NovSwalmen 07:07Partial coverage+2 min+2 min
Mon 2 NovSwalmen 07:04No data—
Sat 31 OctSwalmen 07:050 min+1 min
Fri 30 OctSwalmen 07:08Partial coverage+3 min+4 min
Thu 29 OctSwalmen 07:05Partial coverage+1 min+1 min
Wed 28 OctSwalmen 07:07Partial coverage+2 min+3 min
Tue 27 OctSwalmen 07:06Partial coverage+1 min+1 min
Mon 26 OctSwalmen 07:21+16 min+16 min
Sat 24 OctSwalmen 07:06+1 min+1 min
Fri 23 OctSwalmen 07:04No data—
Thu 22 OctSwalmen 07:08+2 min+3 min
Wed 21 OctSwalmen 07:04No data—
Tue 20 OctSwalmen 07:05+1 min—
Mon 19 OctSwalmen 07:050 min—
Sat 17 OctSwalmen 07:06+1 min+2 min
Fri 16 OctSwalmen 07:05Partial coverage0 min+1 min
Thu 15 OctSwalmen 07:08Partial coverage+4 min+4 min
Tue 13 OctSwalmen 07:06Partial coverage+1 min+2 min
Mon 12 OctSwalmen 07:040 min—
Sat 10 OctSwalmen 07:040 min—
Fri 9 OctSwalmen 07:06Partial coverage+1 min+2 min
Thu 8 OctSwalmen 07:06Partial coverage+1 min+2 min
Wed 7 OctSwalmen 07:05Partial coverage0 min—
Tue 6 OctSwalmen 07:06Partial coverage+2 min+2 min
Mon 5 OctSwalmen 07:06No data—
Fri 2 OctSwalmen 07:05No data—
Thu 1 OctSwalmen 07:04No data—