Train Arriva 32276 Roermond – Nijmegen

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

It has not run yet today

Last recorded run: Sunday 8 November +1 min

Next service: today 21:04 from Roermond · Sat 14 Nov

Next departure 21:04 today · Roermond
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 2 full · 2 partial · 4 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 2 full · 4 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

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

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

  • Early 0% · 0
  • On time 100% · 6
  • 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=2
  • 100% S n=4

Stops and timetable

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

Last 90 days, 6 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
21:04on time on time
21:09— —
21:14 / 21:15— —
21:21— —
21:27 / 21:29— —
21:31— —
21:44 / 21:45— —
21:50 / 21:51— —
21:56 / 22:00— —
22:07 / 22:08— —
22:12— —
22:18— —
22: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 8 NovNijmegen Heyendaal 22:33Partial coverage+1 min+1 min
Sat 7 NovNijmegen Heyendaal 22:32Partial coverage0 min—
Sun 1 NovTegelen 21:340 min—
Sat 31 OctTegelen 21:39No data—
Sun 25 OctTegelen 21:35No data—
Sat 24 OctTegelen 21:36No data—
Sun 18 OctTegelen 21:38+2 min+3 min
Sat 17 OctTegelen 21:38No data—
Sun 11 OctNijmegen Heyendaal 22:32Partial coverage0 min—
Sat 10 OctBoxmeer 22:14Partial coverage0 min—
Sun 4 OctNijmegen Heyendaal 22:33No data—
Sat 3 OctNijmegen Heyendaal 22:32No data—
Sun 27 SeptNijmegen Heyendaal 22:33No data—
Sat 26 SeptNijmegen Heyendaal 22:32No data—
Sun 20 SeptNijmegen Heyendaal 22:32No data—
Sat 19 SeptNijmegen Heyendaal 22:32No data—
Sun 13 SeptNijmegen Heyendaal 22:32No data—
Sat 12 SeptNijmegen Heyendaal 22:32No data—
Sun 6 SeptNijmegen Heyendaal 22:32No data—
Sat 5 SeptNijmegen Heyendaal 22:32No data—
Sun 30 AugNijmegen Heyendaal 22:33No data—
Sat 29 AugNijmegen Heyendaal 22:32No data—
Sun 23 AugVierlingsbeek 22:05No data—
Sat 22 AugVierlingsbeek 22:06No data—