Train Arriva 32489 Roermond – Maastricht Randwyck

Roermond 00:04 → Maastricht Randwyck 00:55 Daily 0 h 51 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to — at 00:57 0 min

  1. Roermond00:04
  2. Echt00:12
  3. Sittard00:22
  4. Geleen-Lutterade00:35
  5. Beek-Elsloo00:39
  6. Maastricht00:50
  7. Maastricht Randwyck00:55

Next service: tomorrow 00:04 from Roermond · Sun 15 Nov

Next departure 00:04 tomorrow · Roermond
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 1 full · 3 partial · 2 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 3 full · 4 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Maastricht Randwyck, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 18 Oct Max en route +4 min · last fix heading to Maastricht +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 6
  • 3–10 min 14% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 7 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
00:04on time on time
00:12— —
00:16— —
00:22 / 00:31— —
00:35— —
00:39— —
00:44 / 00:45— —
00:50 / 00:52— —
00:55— —

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 14 Nov— 00:570 min+2 min
Sun 8 NovMaastricht 01:04Partial coverage0 min—
Sun 1 NovMaastricht 01:07Partial coverage+1 min+5 min
Sun 25 OctMaastricht 01:06No data—
Sun 18 OctMaastricht 01:10Partial coverage+4 min+4 min
Sat 17 OctMaastricht 01:05No data—
Tue 13 Oct— 00:58No data—
Sun 11 OctMaastricht 01:06Partial coverage0 min—
Sat 10 Oct— 00:550 min+1 min
Thu 8 Oct— 01:01+3 min+3 min
Sun 4 OctMaastricht 01:06No data—
Sat 3 OctGeleen-Lutterade 00:49No data—
Sun 27 SeptMaastricht 01:06No data—
Sun 20 SeptMaastricht 01:06No data—
Sun 13 SeptMaastricht 01:06No data—
Mon 7 SeptMaastricht 01:06No data—
Sun 30 AugMaastricht 01:19No data—
Sun 23 AugMaastricht 01:06No data—