Train Arriva 32464 Maastricht Randwyck – Roermond

Maastricht Randwyck 18:05 → Roermond 18:56 Daily 0 h 51 min · 9 stops Arriva

Running now · updated 18:28

Position estimated from the timetable

Heading to Roermond 0 min

Estimated arrival at Roermond 18:56 · 7 km/h

  1. Maastricht Randwyck18:05
  2. Maastricht18:08
  3. Beek-Elsloo18:22
  4. Geleen-Lutterade18:25
  5. Sittard18:31
  6. Echt18:47
  7. Roermond18:56

Today it is running no worse than usual: typical arrival delay is 0 min; 88% of the last 17 runs arrived on time.

On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 0 full · 17 partial · 12 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 0 full · 23 partial · 57 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: +3 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

  • Fri 23 Oct Max en route +8 min · last fix heading to Echt +8 min
  • Mon 2 Nov Max en route +5 min · last fix heading to Maastricht Randwyck +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 100% W n=4
  • 100% T n=1
  • 75% F n=4
  • 100% S n=3
  • 100% S n=4

Stops and timetable

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

Last 90 days, 23 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 10Today
18:05on time on time
18:08 / 18:11— —
18:16— —
18:22— —
18:25 / 18:27— —
18:31 / 18:38— —
18:43— —
18:47— —
18: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
Fri 13 NovGeleen-Lutterade 18:24Partial coverage0 min—
Thu 12 NovBeek-Elsloo 18:34Partial coverage0 min—
Wed 11 NovMaastricht 18:24Partial coverage0 min—
Tue 10 NovBunde 18:59Partial coverage0 min—
Mon 9 NovMaastricht 18:59Partial coverage0 min—
Sun 8 NovEcht 19:04Partial coverage+1 min+1 min
Sat 7 NovEcht 19:03Partial coverage0 min—
Fri 6 NovEcht 18:59Partial coverage0 min—
Thu 5 NovMaastricht 18:24No data—
Wed 4 NovMaastricht 18:24Partial coverage0 min—
Tue 3 NovMaastricht 18:24No data—
Mon 2 NovMaastricht Randwyck 19:04Partial coverage+5 min+5 min
Sun 1 NovEcht 19:02Partial coverage0 min—
Sat 31 OctEcht 19:03Partial coverage+1 min+1 min
Fri 30 OctEcht 19:01No data—
Wed 28 OctMaastricht 18:25Partial coverage0 min—
Tue 27 OctMaastricht Randwyck 18:19Partial coverage0 min—
Mon 26 OctMaastricht Randwyck 18:19No data—
Sun 25 OctEcht 19:03No data—
Sat 24 OctEcht 19:05No data—
Fri 23 OctEcht 19:02Partial coverage+8 min+8 min
Thu 22 OctSusteren 18:57No data—
Wed 21 OctSittard 18:52No data—
Tue 20 OctSusteren 18:50Partial coverage0 min—
Mon 19 OctSusteren 18:57No data—
Sun 18 OctEcht 19:05Partial coverage+2 min+2 min
Sat 17 OctEcht 19:02No data—
Fri 16 OctEcht 19:01No data—
Thu 15 OctGeleen-Lutterade 18:41No data—
Tue 13 OctSittard 18:50No data—