Train Arriva 32275 Nijmegen – Roermond

Nijmegen 20:38 → Roermond 21:56 Daily 1 h 18 min · 13 stops Arriva

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 20:38 from Nijmegen · Fri 13 Nov

Next departure 20:38 today · Nijmegen
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 3 full · 1 partial · 4 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 4 full · 2 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

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
20:38on time on time
20:41— —
20:46— —
20:50 / 20:52— —
20:59 / 21:02— —
21:07 / 21:08— —
21:14 / 21:15— —
21:28— —
21:31 / 21:33— —
21:38— —
21:44 / 21:45— —
21:50— —
21:56— —

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 8 NovSwalmen 22:04Partial coverage0 min+1 min
Sat 7 NovBlerick 21:43+1 min—
Sun 1 NovSwalmen 22:040 min—
Sat 31 OctSwalmen 22:06No data—
Sun 25 OctSwalmen 22:05No data—
Sat 24 OctSwalmen 21:59No data—
Sun 18 OctSwalmen 22:060 min+2 min
Sat 17 OctSwalmen 22:04No data—
Sun 11 OctSwalmen 22:05Partial coverage0 min—
Sat 10 OctBlerick 21:42+2 min+2 min
Sun 4 OctVierlingsbeek 21:22No data—
Sat 3 OctVierlingsbeek 21:21No data—
Sun 27 SeptSwalmen 22:04No data—
Sat 26 SeptBlerick 21:43No data—
Sun 20 SeptBlerick 21:42No data—
Sat 19 SeptBlerick 21:42No data—
Sun 13 SeptBlerick 21:42No data—
Sat 12 SeptBlerick 21:43No data—
Sun 6 SeptSwalmen 22:05No data—
Sat 5 SeptBlerick 21:42No data—
Sun 30 AugBlerick 21:43No data—
Sat 29 AugBlerick 21:43No data—
Sun 23 AugSwalmen 22:05No data—
Sat 22 AugSwalmen 22:06No data—
Sun 16 AugSwalmen 22:06No data—