Train Arriva 32228 Roermond – Nijmegen

Roermond 09:04 → Nijmegen 10:22 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 09:04 from Roermond · Sat 7 Nov

Next departure 09:04 today · Roermond
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 6 full · 8 partial · 14 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 7 full · 10 partial · 70 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: +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

  • Sun 18 Oct Max en route +8 min · last fix heading to Tegelen +8 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
09:04on time +1 min
09:09≈ on time ≈ +2 min
09:14 / 09:15≈ on time ≈ +2 min
09:21≈ on time ≈ +2 min
09:27 / 09:29≈ +1 min ≈ +2 min
09:31≈ +1 min ≈ +2 min
09:44 / 09:45≈ +1 min ≈ +3 min
09:50 / 09:51≈ +1 min ≈ +3 min
09:56 / 10:00≈ +1 min ≈ +3 min
10:07 / 10:08≈ +1 min ≈ +4 min
10:12≈ +1 min ≈ +4 min
10:18≈ +1 min ≈ +4 min
10:22+1 min +4 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 10:33No data—
Thu 5 NovNijmegen Heyendaal 10:32No data—
Wed 4 NovNijmegen Heyendaal 10:33Partial coverage+1 min—
Tue 3 NovNijmegen Heyendaal 10:32Partial coverage0 min—
Mon 2 NovNijmegen Heyendaal 10:34Partial coverage0 min—
Sun 1 NovTegelen 09:37+1 min—
Sat 31 OctTegelen 09:37+2 min+2 min
Fri 30 OctNijmegen Heyendaal 10:32No data—
Thu 29 OctNijmegen Heyendaal 10:33Partial coverage0 min—
Wed 28 OctNijmegen Heyendaal 10:32Partial coverage0 min—
Tue 27 OctNijmegen Heyendaal 10:33Partial coverage0 min—
Mon 26 OctNijmegen Heyendaal 10:33No data—
Sun 25 OctTegelen 09:37No data—
Sat 24 OctTegelen 09:36No data—
Fri 23 OctTegelen 09:35No data—
Thu 22 OctTegelen 09:36No data—
Wed 21 OctTegelen 09:35No data—
Tue 20 OctTegelen 09:360 min—
Mon 19 OctTegelen 09:37No data—
Sun 18 OctTegelen 09:42+8 min+8 min
Sat 17 OctTegelen 09:36+1 min—
Fri 16 OctNijmegen Heyendaal 10:32No data—
Thu 15 OctNijmegen Heyendaal 10:33No data—
Tue 13 OctNijmegen Heyendaal 10:36No data—
Mon 12 OctNijmegen Heyendaal 10:33No data—
Sun 11 OctNijmegen Heyendaal 10:32Partial coverage0 min—
Sat 10 OctNijmegen Heyendaal 10:320 min—
Fri 9 OctNijmegen Heyendaal 10:33Partial coverage+1 min—
Thu 8 OctNijmegen Heyendaal 10:32Partial coverage0 min—
Wed 7 OctNijmegen Heyendaal 12:020 min—