Train Arriva 32471 Roermond → Maastricht Randwyck

Roermond 19:34 → Maastricht Randwyck 20:25 Daily 0 h 51 min · 9 stops Arriva

Arriva 32471 Roermond–Maastricht Randwyck: final delay under 3 min on 12 of its 13 runs with data in the last 30 days (92%). Median final delay: 0 min. Running now, on time. Expected at Maastricht Randwyck: 20:25. TrainsRadar data as of 22 Nov 2026, 20:30 (GMT+1).

Running now · updated 20:29

Position estimated from the timetable

Heading to Maastricht Randwyck 0 min

Estimated arrival at Maastricht Randwyck 20:25

  1. Roermond19:34
  2. Echt19:42
  3. Sittard19:52
  4. Geleen-Lutterade20:05
  5. Beek-Elsloo20:09
  6. Maastricht20:20
  7. Maastricht Randwyck20:25

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

On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 7 full · 6 partial · 3 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 7 full · 9 partial · 18 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 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
19:34on time on time
19:42≈ on time ≈ on time
19:46≈ on time ≈ +1 min
19:52 / 20:01≈ on time ≈ +1 min
20:05≈ on time ≈ +1 min
20:09≈ on time ≈ +2 min
20:14 / 20:15≈ on time ≈ +2 min
20:20 / 20:22≈ on time ≈ +2 min
20:25+1 min +2 min

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
Sun 22 NovMaastricht 20:29Partial coverage0 min—
Sat 21 NovMaastricht 20:34Partial coverage0 min—
Sun 15 NovMaastricht 20:37+1 min+2 min
Sat 14 NovMaastricht 20:340 min—
Thu 12 Nov— 20:280 min—
Wed 11 Nov— 20:28+1 min+1 min
Tue 10 Nov— 20:270 min—
Sun 8 NovMaastricht 20:34Partial coverage0 min—
Sat 7 NovMaastricht 20:37Partial coverage0 min—
Fri 6 Nov— 20:29+1 min—
Wed 4 Nov— 20:29+4 min+4 min
Mon 2 Nov— 20:27No data—
Sun 1 NovMaastricht 20:38Partial coverage+2 min+2 min
Sat 31 OctMaastricht 20:36Partial coverage0 min—
Sun 25 OctMaastricht 20:39No data—
Sat 24 OctMaastricht 20:37No data—
Sun 18 OctMaastricht 20:36Partial coverage0 min—
Sat 17 OctMaastricht 20:36No data—
Fri 16 OctSusteren 20:00No data—
Tue 13 Oct— 20:58No data—
Sun 11 OctMaastricht 20:37Partial coverage+1 min+2 min
Sat 10 OctMaastricht 20:36Partial coverage0 min—
Sun 4 OctMaastricht 20:36No data—
Sat 3 OctMaastricht 20:39No data—
Sun 27 SeptMaastricht 20:38No data—
Sat 26 SeptMaastricht 20:36No data—
Sun 20 SeptMaastricht 20:36No data—
Sat 19 SeptMaastricht 20:36No data—
Sun 13 SeptMaastricht 20:36No data—
Sat 12 SeptMaastricht 20:36No data—