Train Arriva 32273 Nijmegen – Roermond

Nijmegen 20:08 → Roermond 21:26 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 20:08 from Nijmegen · Tue 17 Nov

Next departure 20:08 today · Nijmegen
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 · 19 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Roermond, 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
20:08on time on time
20:11— —
20:16— —
20:20 / 20:22— —
20:29 / 20:32— —
20:37 / 20:38— —
20:44 / 20:45— —
20:58— —
21:01 / 21:03— —
21:08— —
21:14 / 21:15— —
21:20— —
21:26— —

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 NovSwalmen 21:34Partial coverage0 min+10 min
Sat 14 NovSwalmen 21:34Partial coverage+1 min+1 min
Sun 8 NovSwalmen 21:34Partial coverage+1 min—
Sat 7 NovSwalmen 21:34Partial coverage+1 min—
Sun 1 NovSwalmen 21:340 min—
Sat 31 OctSwalmen 21:37No data—
Sun 25 OctSwalmen 21:34No data—
Sat 24 OctSwalmen 21:35No data—
Sun 18 OctSwalmen 21:36+1 min+2 min
Sat 17 OctSwalmen 21:35No data—
Sun 11 OctSwalmen 21:36Partial coverage0 min+1 min
Sat 10 OctSwalmen 21:34Partial coverage0 min—
Sun 4 OctVierlingsbeek 20:53No data—
Sat 3 OctVierlingsbeek 20:51No data—
Sun 27 SeptSwalmen 21:36No data—
Sat 26 SeptSwalmen 21:34No data—
Sun 20 SeptBlerick 21:13No data—
Sat 19 SeptBlerick 21:13No data—
Sun 13 SeptBlerick 21:13No data—
Sat 12 SeptBlerick 21:12No data—
Sun 6 SeptSwalmen 21:34No data—
Sat 5 SeptSwalmen 21:36No data—
Sun 30 AugBlerick 21:13No data—
Sat 29 AugBlerick 21:12No data—
Sun 23 AugSwalmen 21:36No data—
Sat 22 AugSwalmen 21:35No data—
Fri 21 AugVierlingsbeek 20:52No data—