Train Arriva 32280 Roermond – Nijmegen

Roermond 22:04 → Nijmegen 23:22 Daily 1 h 18 min · 13 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 22:04 from Roermond · Wed 18 Nov

Next departure 22:04 today · Roermond
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 1 full · 4 partial · 3 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 2 full · 6 partial · 18 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: 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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=3
  • 100% S n=5

Stops and timetable

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

Last 90 days, 8 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
22:04on time on time
22:09— —
22:14 / 22:15— —
22:21— —
22:27 / 22:29— —
22:31— —
22:44 / 22:45— —
22:50 / 22:51— —
22:56 / 23:00— —
23:07 / 23:08— —
23:12— —
23:18— —
23:22— —

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 23:32Partial coverage0 min—
Sat 14 NovBoxmeer 23:14Partial coverage0 min—
Sun 8 NovNijmegen Heyendaal 23:32Partial coverage0 min—
Sat 7 NovNijmegen Heyendaal 23:24Partial coverage0 min—
Sun 1 NovTegelen 22:340 min+1 min
Sat 31 OctTegelen 22:35No data—
Sun 25 OctTegelen 22:37No data—
Sat 24 OctTegelen 22:36No data—
Sun 18 OctTegelen 22:37+1 min+2 min
Sat 17 OctTegelen 22:36No data—
Sun 11 OctNijmegen Heyendaal 23:32Partial coverage0 min—
Sat 10 OctRoermond 22:18Partial coverage0 min—
Sun 4 OctNijmegen Heyendaal 23:32No data—
Sat 3 OctNijmegen Heyendaal 23:32No data—
Sun 27 SeptNijmegen Heyendaal 23:32No data—
Sat 26 SeptNijmegen Heyendaal 23:32No data—
Sun 20 SeptNijmegen Heyendaal 23:32No data—
Sat 19 SeptBoxmeer 23:08No data—
Sun 13 SeptNijmegen Heyendaal 23:32No data—
Sat 12 SeptNijmegen Heyendaal 23:32No data—
Sun 6 SeptNijmegen Heyendaal 23:32No data—
Sat 5 SeptVierlingsbeek 23:05No data—
Sun 30 AugNijmegen Heyendaal 23:33No data—
Sat 29 AugBlerick 22:45No data—
Sun 23 AugVierlingsbeek 23:07No data—
Sat 22 AugTegelen 22:36No data—