Train Arriva 32474 Maastricht Randwyck → Roermond

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

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

Running now · updated 20:30

Position estimated from the timetable

Heading to Roermond 0 min

Estimated arrival at Roermond 21:26

  1. Maastricht Randwyck20:35
  2. Maastricht20:38
  3. Beek-Elsloo20:52
  4. Geleen-Lutterade20:55
  5. Sittard21:01
  6. Echt21:17
  7. Roermond21:26

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

On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 7 full · 5 partial · 3 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 7 full · 8 partial · 16 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: 0 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

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

  • Early 0% · 0
  • On time 100% · 15
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
20:35on time on time
20:38 / 20:41≈ on time ≈ on time
20:46≈ on time ≈ on time
20:52≈ on time ≈ on time
20:55 / 20:57≈ on time ≈ on time
21:01 / 21:08≈ on time ≈ on time
21:13≈ on time ≈ on time
21:17≈ on time ≈ on time
21:26on time on time

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 Randwyck 20:29Partial coverage0 min—
Sat 21 NovEcht 21:29Partial coverage0 min—
Sun 15 NovGeleen-Lutterade 21:090 min—
Sat 14 NovGeleen-Lutterade 21:120 min—
Thu 12 Nov— 21:280 min—
Tue 10 Nov— 21:290 min—
Sun 8 NovEcht 21:34Partial coverage+1 min+1 min
Sat 7 NovEcht 21:32Partial coverage0 min—
Fri 6 Nov— 21:290 min—
Wed 4 Nov— 21:290 min—
Mon 2 Nov— 21:290 min—
Sun 1 NovEcht 21:33Partial coverage0 min—
Sat 31 OctEcht 21:33No data—
Sun 25 OctEcht 21:32No data—
Sat 24 OctEcht 21:32No data—
Sun 18 OctEcht 21:34Partial coverage+2 min+2 min
Sat 17 OctEcht 21:32No data—
Sun 11 OctEcht 21:32Partial coverage0 min—
Sat 10 OctEcht 21:31Partial coverage0 min—
Sun 4 OctEcht 21:33No data—
Sat 3 OctEcht 21:32No data—
Sun 27 SeptEcht 21:34No data—
Sat 26 SeptEcht 21:33No data—
Sun 20 SeptEcht 21:33No data—
Sat 19 SeptEcht 21:33No data—
Sun 13 SeptEcht 21:33No data—
Sat 12 SeptEcht 21:32No data—
Sun 6 SeptGeleen-Lutterade 21:11No data—
Sat 5 SeptGeleen-Lutterade 21:11No data—
Sun 30 AugEcht 21:32No data—