Train Arriva 32251 Nijmegen – Roermond

Nijmegen 14:38 → Roermond 15:56 Daily 1 h 18 min · 13 stops Arriva

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 14:38 from Nijmegen · Sun 8 Nov

Next departure 14:38 today · Nijmegen
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 3 full · 7 partial · 18 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 3 full · 12 partial · 72 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

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

  • Early 0% · 0
  • On time 100% · 15
  • 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=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=1

Stops and timetable

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

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