Train Arriva 32258 Roermond – Nijmegen

Roermond 16:34 → Nijmegen 17:52 Daily 1 h 18 min · 13 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 16:34 from Roermond · Thu 5 Nov

Next departure 16:34 today · Roermond
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 5 full · 7 partial · 16 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 5 full · 9 partial · 73 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 Nijmegen, 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 +18 min · last fix heading to Nijmegen Heyendaal +18 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=1
  • 100% 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, 14 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
16:34on time on time
16:39≈ on time ≈ on time
16:44 / 16:45≈ on time ≈ on time
16:51≈ on time ≈ on time
16:57 / 16:59≈ on time ≈ on time
17:01≈ on time ≈ on time
17:14 / 17:15≈ on time ≈ on time
17:20 / 17:21≈ on time ≈ on time
17:26 / 17:30≈ on time ≈ +1 min
17:37 / 17:38≈ on time ≈ +1 min
17:43≈ on time ≈ +1 min
17:48≈ on time ≈ +1 min
17:52on time +1 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
Wed 4 NovNijmegen Heyendaal 18:02Partial coverage0 min—
Tue 3 NovNijmegen Heyendaal 18:02No data—
Mon 2 NovNijmegen Heyendaal 18:02No data—
Sun 1 NovTegelen 17:05No data—
Sat 31 OctTegelen 17:05No data—
Fri 30 OctNijmegen Heyendaal 18:02No data—
Thu 29 OctNijmegen Heyendaal 18:02No data—
Wed 28 OctNijmegen Heyendaal 18:02Partial coverage0 min—
Tue 27 OctNijmegen Heyendaal 18:02No data—
Mon 26 OctNijmegen Heyendaal 18:02Partial coverage+18 min+18 min
Sun 25 OctTegelen 17:06No data—
Sat 24 OctTegelen 17:06+1 min—
Fri 23 OctTegelen 17:07No data—
Thu 22 OctTegelen 17:06No data—
Wed 21 OctTegelen 17:07No data—
Tue 20 OctTegelen 17:060 min—
Mon 19 OctTegelen 17:060 min—
Sun 18 OctTegelen 17:05No data—
Sat 17 OctTegelen 17:08No data—
Fri 16 OctNijmegen Heyendaal 18:03No data—
Thu 15 OctNijmegen Heyendaal 18:02No data—
Tue 13 OctNijmegen Heyendaal 18:02No data—
Mon 12 OctNijmegen Heyendaal 18:02Partial coverage0 min—
Sun 11 OctNijmegen Heyendaal 18:03+1 min—
Sat 10 OctNijmegen Heyendaal 18:030 min—
Fri 9 OctNijmegen Heyendaal 18:02Partial coverage0 min—
Thu 8 OctNijmegen Heyendaal 17:58Partial coverage0 min—
Wed 7 OctNijmegen Heyendaal 18:02Partial coverage0 min—
Tue 6 OctNijmegen Heyendaal 18:02Partial coverage0 min—
Mon 5 OctNijmegen Heyendaal 18:02Partial coverage+1 min—