Train Arriva 32446 Maastricht Randwyck – Roermond

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

✓ Today’s run finished

Today, last fix heading to Echt at 14:32 0 min

  1. Maastricht Randwyck13:35
  2. Maastricht13:38
  3. Beek-Elsloo13:52
  4. Geleen-Lutterade13:55
  5. Sittard14:01
  6. Echt14:17
  7. Roermond14:26

Next service: tomorrow 13:35 from Maastricht Randwyck · Sun 8 Nov

Next departure 13:35 tomorrow · Maastricht Randwyck
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 18 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 74 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=4
  • 100% S n=2

Stops and timetable

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

Last 90 days, 14 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
13:35on time on time
13:38 / 13:41— —
13:46— —
13:52— —
13:55 / 13:57— —
14:01 / 14:08— —
14:13— —
14:17— —
14: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
Sat 7 NovEcht 14:32Partial coverage0 min—
Fri 6 NovEcht 14:32No data—
Thu 5 NovEcht 14:33No data—
Wed 4 NovEcht 14:33Partial coverage0 min—
Tue 3 NovEcht 14:33No data—
Mon 2 NovEcht 14:32No data—
Sun 1 NovEcht 14:33Partial coverage0 min—
Sat 31 OctEcht 14:33Partial coverage0 min—
Fri 30 OctEcht 14:32No data—
Thu 29 OctEcht 14:32No data—
Wed 28 OctEcht 14:33Partial coverage0 min—
Tue 27 OctEcht 14:33Partial coverage0 min—
Mon 26 OctEcht 14:33No data—
Sun 25 OctEcht 14:36No data—
Sat 24 OctEcht 14:34Partial coverage+1 min+2 min
Fri 23 OctEcht 14:32No data—
Thu 22 OctEcht 14:34No data—
Wed 21 OctEcht 14:37No data—
Tue 20 OctEcht 14:34Partial coverage0 min—
Mon 19 OctEcht 14:33No data—
Sun 18 OctEcht 14:33Partial coverage0 min—
Sat 17 OctEcht 14:37No data—
Fri 16 OctEcht 14:32No data—
Thu 15 OctEcht 14:32No data—
Tue 13 OctEcht 14:32No data—
Mon 12 OctEcht 14:33No data—
Sun 11 OctEcht 14:32No data—
Sat 10 OctEcht 14:32Partial coverage0 min—
Fri 9 OctEcht 14:33Partial coverage0 min—
Thu 8 OctEcht 14:32Partial coverage0 min—