Train Arriva 32262 Roermond – Nijmegen

Roermond 17:34 → Nijmegen 18: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 17:34 from Roermond · Thu 5 Nov

Next departure 17:34 today · Roermond
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 8 full · 6 partial · 14 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 8 full · 8 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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 100% · 16
  • 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=2
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=3

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
17:34on time on time
17:39≈ on time ≈ +1 min
17:44 / 17:45≈ on time ≈ +1 min
17:51≈ on time ≈ +1 min
17:57 / 17:59≈ on time ≈ +1 min
18:01≈ on time ≈ +1 min
18:14 / 18:15≈ on time ≈ +1 min
18:20 / 18:21≈ on time ≈ +1 min
18:26 / 18:30≈ on time ≈ +1 min
18:37 / 18:38≈ on time ≈ +1 min
18:43≈ on time ≈ +1 min
18:48≈ on time ≈ +1 min
18: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 NovVenray 18:29Partial coverage0 min—
Tue 3 NovBlerick 18:14No data—
Mon 2 NovBlerick 18:14No data—
Sun 1 NovTegelen 18:050 min—
Sat 31 OctTegelen 18:06+1 min—
Fri 30 OctNijmegen Heyendaal 19:02No data—
Thu 29 OctBlerick 18:15No data—
Wed 28 OctBlerick 18:11Partial coverage0 min—
Tue 27 OctBlerick 18:15No data—
Mon 26 OctBlerick 18:15Partial coverage0 min—
Sun 25 OctTegelen 18:06No data—
Sat 24 OctTegelen 18:070 min—
Fri 23 OctTegelen 18:05No data—
Thu 22 OctTegelen 18:05No data—
Wed 21 OctTegelen 18:05No data—
Tue 20 OctTegelen 18:050 min—
Mon 19 OctTegelen 18:05No data—
Sun 18 OctTegelen 18:07+1 min—
Sat 17 OctTegelen 18:08No data—
Fri 16 OctNijmegen Heyendaal 19:02No data—
Thu 15 OctBoxmeer 18:44No data—
Tue 13 OctCuijk 18:50No data—
Mon 12 OctMook-Molenhoek 18:57Partial coverage0 min—
Sun 11 OctNijmegen Heyendaal 19:020 min—
Sat 10 OctNijmegen Heyendaal 19:020 min—
Fri 9 OctBoxmeer 18:44Partial coverage0 min—
Thu 8 OctBlerick 18:160 min—
Wed 7 OctBlerick 18:15Partial coverage0 min—
Tue 6 OctBlerick 18:15Partial coverage0 min—
Mon 5 OctBlerick 18:15Partial coverage0 min—