Train Arriva 32250 Roermond – Nijmegen

Roermond 14:34 → Nijmegen 15:52 Daily 1 h 18 min · 13 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 14:34 from Roermond · Sat 7 Nov

Next departure 14: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
88%
14/16 runs under 3 min
RT coverage: 5 full · 11 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 4 Nov Max en route +14 min · last fix heading to Nijmegen Heyendaal +14 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Nijmegen Heyendaal +3 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 88% · 14
  • 3–10 min 6% · 1
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

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