Train Arriva 32437 Roermond – Maastricht Randwyck

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 11:04 from Roermond · Sun 8 Nov

Next departure 11:04 today · Roermond
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 15 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 0 full · 17 partial · 70 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: 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

Worst days

  • Fri 9 Oct Max en route +9 min · last fix heading to Maastricht +9 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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