Train Arriva 32434 Maastricht Randwyck – Roermond

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 10:35 from Maastricht Randwyck · Thu 5 Nov

Next departure 10:35 today · Maastricht Randwyck
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 19 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 77 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 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

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

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

On-time by weekday

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

Stops and timetable

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

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

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
Wed 4 NovEcht 11:34Partial coverage+1 min+1 min
Tue 3 NovEcht 11:32No data—
Mon 2 NovEcht 11:32No data—
Sun 1 NovEcht 11:34Partial coverage0 min—
Sat 31 OctEcht 11:32No data—
Fri 30 OctEcht 11:33No data—
Thu 29 OctEcht 11:33No data—
Wed 28 OctEcht 11:36Partial coverage0 min—
Tue 27 OctEcht 11:32Partial coverage0 min—
Mon 26 OctEcht 11:32No data—
Sun 25 OctEcht 11:33No data—
Sat 24 OctEcht 11:32No data—
Fri 23 OctEcht 11:35No data—
Thu 22 OctEcht 11:38No data—
Wed 21 OctEcht 11:33No data—
Tue 20 OctEcht 11:33Partial coverage0 min—
Mon 19 OctEcht 11:36No data—
Sun 18 OctEcht 11:33Partial coverage0 min—
Sat 17 OctEcht 11:33No data—
Fri 16 OctEcht 11:32No data—
Thu 15 OctEcht 11:32No data—
Tue 13 OctEcht 11:33No data—
Mon 12 OctEcht 11:33No data—
Sun 11 OctEcht 11:33Partial coverage0 min—
Sat 10 OctEcht 11:32No data—
Fri 9 OctEcht 11:33Partial coverage0 min+1 min
Thu 8 OctEcht 11:33Partial coverage0 min—
Wed 7 OctEcht 12:02No data—
Tue 6 OctEcht 11:32Partial coverage0 min—
Mon 5 OctEcht 11:36No data—