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: Sunday 15 November +1 min

Next service: today 17:34 from Roermond · Mon 16 Nov

Next departure 17:34 today · Roermond
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 14 full · 4 partial · 11 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 20 full · 6 partial · 61 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 26
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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 ≈ on time
17:44 / 17:45≈ on time ≈ on time
17:51≈ on time ≈ on time
17:57 / 17:59≈ on time ≈ on time
18:01≈ on time ≈ on time
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:42≈ 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
Sun 15 NovNijmegen Heyendaal 19:03Partial coverage+1 min+1 min
Sat 14 NovNijmegen Heyendaal 19:04Partial coverage+1 min+1 min
Fri 13 NovNijmegen Heyendaal 19:02+1 min—
Thu 12 NovVierlingsbeek 18:34+1 min+2 min
Wed 11 NovBlerick 18:140 min—
Tue 10 NovVierlingsbeek 18:340 min—
Mon 9 NovBlerick 18:140 min—
Sun 8 NovNijmegen Heyendaal 19:02Partial coverage0 min—
Sat 7 NovNijmegen Heyendaal 19:02Partial coverage0 min—
Fri 6 NovMook-Molenhoek 18:57+1 min—
Thu 5 NovBlerick 18:09No data—
Wed 4 NovVenray 18:290 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:110 min—
Tue 27 OctBlerick 18:15No data—
Mon 26 OctBlerick 18:150 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—