Train Arriva 32460 Maastricht Randwyck – Roermond

Maastricht Randwyck 17:05 → Roermond 17:56 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 17:05 from Maastricht Randwyck · Thu 5 Nov

Next departure 17:05 today · Maastricht Randwyck
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 0 full · 13 partial · 15 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 0 full · 15 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 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

  • Mon 26 Oct Max en route +3 min · last fix heading to Echt +3 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

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

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:05on time on time
17:08 / 17:11— —
17:16— —
17:22— —
17:25 / 17:27— —
17:31 / 17:38— —
17:43— —
17:47— —
17:56— —

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 17:59Partial coverage0 min—
Tue 3 NovEcht 17:59No data—
Mon 2 NovEcht 17:59No data—
Sun 1 NovEcht 18:02No data—
Sat 31 OctEcht 18:02Partial coverage0 min—
Fri 30 OctEcht 18:01No data—
Thu 29 OctEcht 18:01No data—
Wed 28 OctEcht 18:01Partial coverage0 min—
Tue 27 OctEcht 18:01No data—
Mon 26 OctEcht 18:02Partial coverage+3 min+3 min
Sun 25 OctEcht 18:07No data—
Sat 24 OctEcht 18:02Partial coverage0 min—
Fri 23 OctEcht 18:10No data—
Thu 22 OctEcht 17:55No data—
Wed 21 OctEcht 18:01No data—
Tue 20 OctEcht 18:01Partial coverage0 min—
Mon 19 OctEcht 18:01No data—
Sun 18 OctEcht 18:04Partial coverage0 min—
Sat 17 OctEcht 18:07No data—
Fri 16 OctEcht 18:02No data—
Thu 15 OctEcht 18:01No data—
Tue 13 OctEcht 18:01No data—
Mon 12 OctEcht 18:01Partial coverage0 min—
Sun 11 OctEcht 18:02Partial coverage0 min—
Sat 10 OctEcht 18:05Partial coverage+2 min+2 min
Fri 9 OctEcht 18:01Partial coverage0 min—
Thu 8 OctEcht 17:58Partial coverage0 min—
Wed 7 OctEcht 18:01Partial coverage0 min—
Tue 6 OctEcht 18:01Partial coverage0 min—
Mon 5 OctEcht 18:01Partial coverage0 min—