Train Arriva 32441 Roermond – Maastricht Randwyck

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 12:04 from Roermond · Sat 7 Nov

Next departure 12:04 today · Roermond
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 6 full · 6 partial · 16 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 6 full · 10 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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 100% · 16
  • 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
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=3

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 10
12:04on time on time
12:12≈ on time ≈ on time
12:16≈ on time ≈ on time
12:22 / 12:31≈ on time ≈ on time
12:35≈ on time ≈ on time
12:39≈ on time ≈ on time
12:44 / 12:45≈ on time ≈ on time
12:50 / 12:52≈ on time ≈ on time
12:55on 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
Fri 6 NovMaastricht 13:04No data—
Thu 5 NovMaastricht 13:04No data—
Wed 4 NovMaastricht 13:04Partial coverage0 min—
Tue 3 NovMaastricht 13:04No data—
Mon 2 NovMaastricht 13:04No data—
Sun 1 NovMaastricht 13:070 min—
Sat 31 OctMaastricht 13:060 min—
Fri 30 OctMaastricht 13:06No data—
Thu 29 OctMaastricht 13:06No data—
Wed 28 OctMaastricht 13:06Partial coverage0 min—
Tue 27 OctMaastricht 13:07Partial coverage0 min—
Mon 26 OctMaastricht 13:06No data—
Sun 25 OctMaastricht 13:06No data—
Sat 24 OctMaastricht 13:060 min—
Fri 23 OctMaastricht 13:06No data—
Thu 22 OctMaastricht 13:09No data—
Wed 21 OctMaastricht 13:06No data—
Tue 20 OctMaastricht 13:06Partial coverage0 min—
Mon 19 OctMaastricht 13:06Partial coverage0 min—
Sun 18 OctMaastricht 13:060 min—
Sat 17 OctMaastricht 13:06No data—
Fri 16 OctMaastricht 13:06No data—
Thu 15 OctMaastricht 13:16No data—
Tue 13 OctMaastricht 13:06No data—
Mon 12 OctMaastricht 13:07No data—
Sun 11 OctMaastricht 13:060 min—
Sat 10 OctMaastricht 13:060 min—
Fri 9 OctMaastricht 13:06Partial coverage0 min—
Thu 8 OctMaastricht 13:07Partial coverage+1 min+1 min
Wed 7 OctMaastricht 13:06Partial coverage0 min—