Train Arriva 32257 Nijmegen – Roermond

Nijmegen 16:08 → Roermond 17:26 Daily 1 h 18 min · 13 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 16:08 from Nijmegen · Thu 5 Nov

Next departure 16:08 today · Nijmegen
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 3 full · 9 partial · 16 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 3 full · 11 partial · 73 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 Roermond, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 6 Oct Max en route +3 min · last fix heading to Swalmen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
16:08on time on time
16:11— —
16:16— —
16:20 / 16:22— —
16:29 / 16:32— —
16:37 / 16:38— —
16:44 / 16:45— —
16:58— —
17:01 / 17:03— —
17:08— —
17:14 / 17:15— —
17:20— —
17: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
Wed 4 NovSwalmen 17:34Partial coverage0 min—
Tue 3 NovSwalmen 17:34No data—
Mon 2 NovSwalmen 17:34No data—
Sun 1 NovSwalmen 17:450 min+9 min
Sat 31 OctSwalmen 17:34No data—
Fri 30 OctSwalmen 17:34No data—
Thu 29 OctSwalmen 17:33No data—
Wed 28 OctSwalmen 17:34Partial coverage0 min—
Tue 27 OctSwalmen 17:34Partial coverage0 min—
Mon 26 OctSwalmen 17:34No data—
Sun 25 OctSwalmen 17:34No data—
Sat 24 OctSwalmen 17:34No data—
Fri 23 OctSwalmen 17:34No data—
Thu 22 OctSwalmen 17:35No data—
Wed 21 OctSwalmen 17:34No data—
Tue 20 OctSwalmen 17:340 min—
Mon 19 OctSwalmen 17:34No data—
Sun 18 OctSwalmen 17:35+1 min+1 min
Sat 17 OctSwalmen 17:35No data—
Fri 16 OctSwalmen 17:35No data—
Thu 15 OctSwalmen 17:34No data—
Tue 13 OctSwalmen 17:34No data—
Mon 12 OctSwalmen 17:35Partial coverage0 min—
Sun 11 OctSwalmen 17:35Partial coverage+1 min+1 min
Sat 10 OctSwalmen 17:35Partial coverage0 min—
Fri 9 OctSwalmen 17:34Partial coverage0 min—
Thu 8 OctSwalmen 17:34Partial coverage0 min—
Wed 7 OctSwalmen 17:34Partial coverage0 min—
Tue 6 OctSwalmen 17:34Partial coverage+3 min+3 min
Mon 5 OctSwalmen 17:34Partial coverage+1 min—