Train Arriva 32463 Roermond – Maastricht Randwyck

Roermond 17:34 → Maastricht Randwyck 18:25 Daily 0 h 51 min · 9 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:34 from Roermond · Fri 6 Nov

Next departure 17:34 today · Roermond
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 1 full · 11 partial · 16 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 1 full · 14 partial · 72 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

Worst days

  • Sun 18 Oct Max en route +5 min · last fix heading to Maastricht +5 min

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 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 67% 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
17:34on time on time
17:42— —
17:46— —
17:52 / 18:01— —
18:05— —
18:09— —
18:14 / 18:15— —
18:20 / 18:22— —
18:25— —

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 NovBeek-Elsloo 18:23No data—
Wed 4 NovBunde 18:29No data—
Tue 3 NovBeek-Elsloo 18:23No data—
Mon 2 NovBeek-Elsloo 18:23No data—
Sun 1 NovMaastricht 18:34Partial coverage0 min—
Sat 31 OctMaastricht 18:37Partial coverage0 min—
Fri 30 OctMaastricht 18:36No data—
Thu 29 OctSittard 18:15No data—
Wed 28 OctBeek-Elsloo 18:23Partial coverage0 min—
Tue 27 OctGeleen-Lutterade 18:19No data—
Mon 26 OctBeek-Elsloo 18:23Partial coverage0 min—
Sun 25 OctMaastricht 18:36No data—
Sat 24 OctMaastricht 18:37Partial coverage0 min—
Fri 23 OctMaastricht 18:36No data—
Thu 22 OctMaastricht 18:36No data—
Wed 21 OctMaastricht 18:34No data—
Tue 20 OctMaastricht 18:36Partial coverage0 min—
Mon 19 OctMaastricht 18:36No data—
Sun 18 OctMaastricht 18:41Partial coverage+5 min+5 min
Sat 17 OctMaastricht 18:39No data—
Fri 16 OctMaastricht 18:39No data—
Thu 15 OctMaastricht 18:36No data—
Tue 13 OctMaastricht 18:36No data—
Mon 12 OctMaastricht 18:32Partial coverage0 min—
Sun 11 OctMaastricht 18:36Partial coverage0 min—
Sat 10 OctMaastricht 18:38Partial coverage+1 min+1 min
Fri 9 OctMaastricht 18:36Partial coverage0 min—
Thu 8 OctSittard 18:160 min—
Wed 7 OctBeek-Elsloo 18:28Partial coverage0 min—
Tue 6 OctSittard 18:15Partial coverage0 min—