Train Arriva 732231 Venlo – Roermond

Venlo 10:33 → Roermond 10:56 Daily 0 h 23 min · 5 stops Arriva

✓ Today’s run finished

Today, last fix heading to Swalmen at 11:04 No data

  1. Venlo10:33
  2. Tegelen10:38
  3. Reuver10:44
  4. Swalmen10:50
  5. Roermond10:56

Next service: Monday 10:33 from Venlo · Mon 9 Nov

Next departure 10:33 Monday · Venlo
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 6 full · 5 partial · 16 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 6 full · 6 partial · 42 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: +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

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

  • Early 0% · 0
  • On time 100% · 12
  • 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=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=1

Stops and timetable

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

Last 90 days, 12 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
10:33on time on time
10:38≈ on time ≈ on time
10:44 / 10:45≈ on time ≈ +1 min
10:50≈ on time ≈ +1 min
10:56on time +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
Fri 6 NovSwalmen 11:04No data—
Thu 5 NovSwalmen 11:04No data—
Wed 4 NovSwalmen 11:04Partial coverage+1 min—
Tue 3 NovSwalmen 11:04No data—
Mon 2 NovSwalmen 11:04No data—
Sun 1 NovCuijk 10:08+1 min+1 min
Sat 31 OctCuijk 10:06+1 min+1 min
Fri 30 OctSwalmen 11:05No data—
Thu 29 OctSwalmen 11:05No data—
Wed 28 OctSwalmen 11:05Partial coverage0 min—
Tue 27 OctSwalmen 11:08Partial coverage0 min—
Mon 26 OctSwalmen 11:05No data—
Sun 25 OctCuijk 10:06No data—
Sat 24 OctCuijk 10:060 min—
Fri 23 OctCuijk 10:07No data—
Thu 22 OctCuijk 10:06No data—
Wed 21 OctCuijk 10:06No data—
Tue 20 OctCuijk 10:060 min—
Mon 19 OctCuijk 10:060 min—
Sun 18 OctCuijk 10:06No data—
Sat 17 OctCuijk 10:060 min—
Fri 16 OctSwalmen 11:05No data—
Thu 15 OctSwalmen 11:06No data—
Tue 13 OctSwalmen 11:04No data—
Mon 12 OctSwalmen 11:04No data—
Fri 9 OctSwalmen 11:07Partial coverage+2 min+3 min
Thu 8 OctSwalmen 11:05Partial coverage0 min+1 min
Wed 7 OctTegelen 12:04No data—
Tue 6 OctSwalmen 11:05Partial coverage+1 min—
Mon 5 OctSwalmen 11:04No data—