Train Arriva 32430 Maastricht Randwyck – Roermond

Maastricht Randwyck 09:35 → Roermond 10:26 Daily 0 h 51 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Echt at 10:34 +2 min

  1. Maastricht Randwyck09:35
  2. Maastricht09:38
  3. Beek-Elsloo09:52
  4. Geleen-Lutterade09:55
  5. Sittard10:01
  6. Echt10:17
  7. Roermond10:26

Next service: tomorrow 09:35 from Maastricht Randwyck · Sun 8 Nov

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

  • Wed 4 Nov Max en route +18 min · last fix heading to Echt +18 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 50% W n=2
  • 100% T n=2
  • 100% F n=1
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 14 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
09:35on time on time
09:38 / 09:41— —
09:46— —
09:52— —
09:55 / 09:57— —
10:01 / 10:08— —
10:13— —
10:17— —
10: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
Sat 7 NovEcht 10:34Partial coverage+2 min+2 min
Fri 6 NovEcht 10:32No data—
Thu 5 NovEcht 10:33No data—
Wed 4 NovEcht 10:49Partial coverage+18 min+18 min
Tue 3 NovEcht 10:34No data—
Mon 2 NovEcht 10:33No data—
Sun 1 NovEcht 10:32No data—
Sat 31 OctEcht 10:34Partial coverage+1 min+1 min
Fri 30 OctEcht 10:43No data—
Thu 29 OctEcht 10:32Partial coverage0 min—
Wed 28 OctEcht 10:33Partial coverage0 min—
Tue 27 OctEcht 10:33Partial coverage0 min—
Mon 26 OctEcht 10:32No data—
Sun 25 OctEcht 10:33No data—
Sat 24 OctEcht 10:32Partial coverage0 min—
Fri 23 OctEcht 10:32No data—
Thu 22 OctEcht 10:40No data—
Wed 21 OctEcht 10:32No data—
Tue 20 OctEcht 10:33Partial coverage0 min—
Mon 19 OctEcht 10:33Partial coverage0 min—
Sun 18 OctEcht 10:32No data—
Sat 17 OctEcht 10:33Partial coverage0 min—
Fri 16 OctMaastricht 16:53No data—
Thu 15 OctEcht 10:33No data—
Tue 13 OctEcht 10:32No data—
Mon 12 OctEcht 10:34No data—
Sun 11 OctEcht 10:32No data—
Sat 10 OctEcht 10:33Partial coverage0 min—
Fri 9 OctEcht 10:35Partial coverage+2 min+2 min
Thu 8 OctEcht 10:34Partial coverage+1 min+1 min