Train Arriva 32281 Nijmegen – Roermond

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: tomorrow 22:08 from Nijmegen · Tue 17 Nov

Next departure 22:08 tomorrow · Nijmegen
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 1 full · 4 partial · 3 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 1 full · 5 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 6 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
22:08on time on time
22:11— —
22:16— —
22:20 / 22:22— —
22:29 / 22:32— —
22:37 / 22:38— —
22:44 / 22:45— —
22:58— —
23:01 / 23:03— —
23:08— —
23:14 / 23:15— —
23:20— —
23:26— —

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
Sun 15 NovSwalmen 23:34Partial coverage0 min—
Sat 14 NovBlerick 23:12Partial coverage0 min—
Sun 8 NovSwalmen 23:34Partial coverage0 min—
Sat 7 NovSwalmen 23:34Partial coverage+1 min+2 min
Sun 1 NovSwalmen 23:34No data—
Sat 31 OctSwalmen 23:34No data—
Sun 25 OctSwalmen 23:35No data—
Sun 18 OctSwalmen 23:350 min+1 min
Sat 17 OctSwalmen 23:34No data—
Sun 11 OctSwalmen 23:34Partial coverage0 min—
Sun 4 OctVierlingsbeek 22:51No data—
Sat 3 OctVierlingsbeek 22:51No data—
Sun 27 SeptSwalmen 23:34No data—
Sat 26 SeptSwalmen 23:34No data—
Sun 20 SeptBlerick 23:12No data—
Sat 19 SeptBlerick 23:08No data—
Sun 13 SeptBlerick 23:13No data—
Sat 12 SeptBlerick 23:12No data—
Sun 6 SeptSwalmen 23:36No data—
Sat 5 SeptVenray 22:59No data—
Sun 30 AugBlerick 23:12No data—
Sat 29 AugVierlingsbeek 22:52No data—
Sun 23 AugBlerick 23:15No data—
Sat 22 AugBlerick 23:07No data—