Train Arriva 32465 Roermond – Maastricht Randwyck

Roermond 18:04 → Maastricht Randwyck 18:55 Daily 0 h 51 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 18:04 from Roermond · Thu 5 Nov

Next departure 18:04 today · Roermond
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 13 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 66 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 Maastricht Randwyck, 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=2
  • 100% T n=3
  • 100% W n=3
  • — T n=0
  • 100% F n=2
  • 100% S n=2
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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 10
18:04on time on time
18:12— —
18:16— —
18:22 / 18:31— —
18:35— —
18:39— —
18:44 / 18:45— —
18:50 / 18:52— —
18:55— —

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 NovEcht 18:58Partial coverage0 min—
Tue 3 NovEcht 18:24No data—
Mon 2 NovRoermond 18:18No data—
Sun 1 NovMaastricht 19:04Partial coverage0 min—
Sat 31 OctMaastricht 19:06Partial coverage0 min—
Fri 30 OctMaastricht 19:06No data—
Wed 28 OctEcht 18:26Partial coverage0 min—
Tue 27 OctRoermond 18:18Partial coverage0 min—
Mon 26 OctRoermond 18:18No data—
Sun 25 OctMaastricht 19:06No data—
Sat 24 OctMaastricht 19:08No data—
Fri 23 OctMaastricht 19:06Partial coverage+1 min+1 min
Thu 22 OctBunde 18:59No data—
Wed 21 OctBeek-Elsloo 18:53No data—
Tue 20 OctBunde 18:50Partial coverage0 min—
Mon 19 OctBeek-Elsloo 18:53No data—
Sun 18 OctMaastricht 19:07Partial coverage+1 min+2 min
Sat 17 OctMaastricht 19:06No data—
Fri 16 OctMaastricht 19:06No data—
Thu 15 OctSusteren 18:30No data—
Tue 13 OctBeek-Elsloo 18:50No data—
Mon 12 OctBunde 18:59Partial coverage0 min—
Sun 11 OctMaastricht 19:06Partial coverage0 min—
Sat 10 OctMaastricht 19:06Partial coverage0 min—
Fri 9 OctGeleen-Lutterade 18:49Partial coverage+1 min+1 min
Wed 7 OctRoermond 18:18Partial coverage0 min—
Tue 6 OctRoermond 18:18Partial coverage0 min—
Mon 5 OctEcht 18:26Partial coverage0 min—
Sun 4 OctMaastricht 19:06No data—
Sat 3 OctMaastricht 19:06No data—