Train Arriva 32240 Roermond – Nijmegen

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

Running now · updated 13:33

Heading to Nijmegen No data

Estimated arrival at Nijmegen 13:22

  1. Roermond12:04
  2. Reuver12:14
  3. Venlo12:27
  4. Venray12:44
  5. Boxmeer12:56
  6. Mook-Molenhoek13:12
  7. Nijmegen13:22
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 5 full · 8 partial · 16 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 5 full · 10 partial · 73 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 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

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

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

On-time by weekday

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

Stops and timetable

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

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