Train Arriva 32418 Maastricht Randwyck – Roermond

Maastricht Randwyck 06:35 → Roermond 07:26 Mon, Tue, Wed, Thu, Fri, Sat 0 h 51 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Echt at 07:34 No data

  1. Maastricht Randwyck06:35
  2. Maastricht06:38
  3. Beek-Elsloo06:52
  4. Geleen-Lutterade06:55
  5. Sittard07:01
  6. Echt07:17
  7. Roermond07:26

Next service: tomorrow 06:35 from Maastricht Randwyck · Fri 6 Nov

Next departure 06:35 tomorrow · Maastricht Randwyck
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 0 full · 23 partial · 2 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 0 full · 24 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 3 Nov Max en route +4 min · last fix heading to Echt +4 min
  • Fri 30 Oct Max en route +3 min · last fix heading to Echt +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 22
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 100% W n=4
  • 100% T n=4
  • 75% F n=4
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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
06:35on time on time
06:38 / 06:41— —
06:46— —
06:52— —
06:55 / 06:57— —
07:01 / 07:08— —
07:13— —
07:17— —
07:26— —

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 NovEcht 07:34No data—
Wed 4 NovEcht 07:33Partial coverage0 min—
Tue 3 NovEcht 07:48Partial coverage+4 min+4 min
Mon 2 NovEcht 07:33Partial coverage0 min—
Sat 31 OctEcht 07:33Partial coverage0 min—
Fri 30 OctEcht 07:35Partial coverage+3 min+3 min
Thu 29 OctEcht 07:33Partial coverage0 min—
Wed 28 OctEcht 07:36Partial coverage+2 min+2 min
Tue 27 OctEcht 07:33Partial coverage0 min—
Mon 26 OctEcht 07:32Partial coverage0 min—
Sat 24 OctEcht 07:33Partial coverage0 min—
Fri 23 OctEcht 07:33Partial coverage0 min—
Thu 22 OctEcht 07:33Partial coverage0 min—
Wed 21 OctEcht 07:32Partial coverage0 min—
Tue 20 OctEcht 07:33Partial coverage0 min—
Mon 19 OctEcht 07:32Partial coverage0 min—
Sat 17 OctEcht 07:33Partial coverage0 min—
Fri 16 OctEcht 07:34Partial coverage0 min—
Thu 15 OctEcht 07:33Partial coverage0 min—
Tue 13 OctEcht 07:35Partial coverage0 min—
Mon 12 OctEcht 07:34Partial coverage0 min—
Sat 10 OctEcht 07:32No data—
Fri 9 OctEcht 07:35Partial coverage+2 min+2 min
Thu 8 OctEcht 07:34Partial coverage+1 min+1 min
Wed 7 OctEcht 07:32Partial coverage0 min—
Tue 6 OctEcht 07:33Partial coverage0 min—
Mon 5 OctEcht 07:37No data—
Sat 3 OctEcht 07:32No data—
Fri 2 OctEcht 07:33No data—
Thu 1 OctEcht 07:33No data—