Train Arriva 32084 Maastricht Randwyck – Heerlen

Maastricht Randwyck 00:35 → Heerlen 01:11 Daily 0 h 36 min · 11 stops Arriva

It has not run yet today

Last recorded run: Monday 2 November +3 min

Next service: tomorrow 00:35 from Maastricht Randwyck · Sat 7 Nov

Next departure 00:35 tomorrow · Maastricht Randwyck
On-time · 30 days
71%
5/7 runs under 3 min
RT coverage: 5 full · 2 partial · 4 no data
On-time · 90 days
71%
5/7 runs under 3 min
RT coverage: 5 full · 2 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Heerlen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 24 Oct Max en route +4 min · last fix heading to — +4 min
  • Mon 2 Nov Max en route +3 min · last fix heading to Heerlen Woonboulevard +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 5
  • 3–10 min 29% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 7 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
00:35on time on time
00:38 / 00:41≈ on time ≈ on time
00:44≈ on time ≈ +1 min
00:47≈ on time ≈ +1 min
00:51≈ on time ≈ +1 min
00:54≈ on time ≈ +1 min
00:58 / 00:59≈ on time ≈ +2 min
01:02≈ on time ≈ +2 min
01:06≈ on time ≈ +2 min
01:08≈ on time ≈ +2 min
01:11on time +3 min

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
Mon 2 NovHeerlen Woonboulevard 01:22Partial coverage+3 min+3 min
Thu 29 Oct— 01:150 min—
Tue 27 Oct— 01:140 min—
Mon 26 OctHeerlen Woonboulevard 01:25No data—
Sat 24 Oct— 01:18+4 min+4 min
Fri 23 Oct— 01:19No data—
Thu 22 Oct— 01:17No data—
Wed 21 Oct— 01:130 min—
Mon 19 OctHeerlen Woonboulevard 01:22Partial coverage0 min—
Sun 18 OctHeerlen Woonboulevard 01:22No data—
Mon 12 OctHeerlen Woonboulevard 01:220 min—
Mon 5 OctHeerlen Woonboulevard 01:23No data—
Mon 28 SeptHeerlen Woonboulevard 01:23No data—
Mon 21 SeptHeerlen Woonboulevard 01:23No data—
Mon 14 SeptHeerlen Woonboulevard 01:22No data—
Mon 7 SeptHeerlen Woonboulevard 01:23No data—
Mon 31 AugHeerlen Woonboulevard 01:23No data—
Mon 24 AugHeerlen Woonboulevard 01:23No data—