Train Arriva 32255 Nijmegen – Roermond

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 15:38 from Nijmegen · Fri 6 Nov

Next departure 15:38 today · Nijmegen
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 3 full · 10 partial · 15 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 3 full · 13 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Fri 9 Oct Max en route +4 min · last fix heading to Swalmen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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