Train Arriva 32452 Maastricht Randwyck – Roermond

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

Running now · updated 15:23

Heading to Roermond No data

Estimated arrival at Roermond 15:56 · 50 km/h

  1. Maastricht Randwyck15:05
  2. Maastricht15:08
  3. Beek-Elsloo15:22
  4. Geleen-Lutterade15:25
  5. Sittard15:31
  6. Echt15:47
  7. Roermond15:56
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 17 no data
On-time · 90 days
100%
14/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
+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

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

On-time by weekday

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

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 10Today
15:05on time on time
15:08 / 15:11— —
15:16— —
15:22— —
15:25 / 15:27— —
15:31 / 15:38— —
15:43— —
15:47— —
15: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
Thu 5 NovBeek-Elsloo 15:19No data—
Wed 4 NovEcht 16:03Partial coverage0 min—
Tue 3 NovEcht 16:03No data—
Mon 2 NovEcht 16:03No data—
Sun 1 NovEcht 16:05Partial coverage+1 min+1 min
Sat 31 OctEcht 16:02No data—
Fri 30 OctEcht 16:03No data—
Thu 29 OctEcht 16:02No data—
Wed 28 OctEcht 16:03Partial coverage0 min—
Tue 27 OctEcht 16:03Partial coverage0 min—
Mon 26 OctEcht 16:02No data—
Sun 25 OctEcht 16:03No data—
Sat 24 OctEcht 16:03Partial coverage0 min—
Fri 23 OctEcht 16:03No data—
Thu 22 OctEcht 16:13No data—
Wed 21 OctEcht 16:02No data—
Tue 20 OctEcht 16:03Partial coverage0 min—
Mon 19 OctEcht 16:04No data—
Sun 18 OctEcht 16:03Partial coverage0 min—
Sat 17 OctEcht 16:25No data—
Fri 16 OctEcht 16:03No data—
Thu 15 OctEcht 16:03No data—
Tue 13 OctEcht 16:03No data—
Mon 12 OctEcht 16:02Partial coverage0 min—
Sun 11 OctEcht 16:04Partial coverage+2 min+2 min
Sat 10 OctEcht 16:03Partial coverage0 min—
Fri 9 OctEcht 16:03Partial coverage0 min—
Thu 8 OctEcht 16:03No data—
Wed 7 OctEcht 16:02Partial coverage0 min—
Tue 6 OctEcht 16:03Partial coverage0 min—