Train Arriva 32082 Maastricht Randwyck – Heerlen

Maastricht Randwyck 00:05 → Heerlen 00:41 Daily 0 h 36 min · 11 stops Arriva

It has not run yet today

Last recorded run: Sunday 1 November 0 min

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

Next departure 00:05 tomorrow · Maastricht Randwyck
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 3 full · 2 partial · 5 no data
On-time · 90 days
80%
4/5 runs under 3 min
RT coverage: 3 full · 2 partial · 12 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 30 Oct Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 4
  • 3–10 min 20% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 5 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:05on time on time
00:08 / 00:11— —
00:14— —
00:17— —
00:21— —
00:24— —
00:28 / 00:29— —
00:32— —
00:35— —
00:38— —
00:41— —

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
Sun 1 NovHeerlen Woonboulevard 00:52Partial coverage0 min—
Sat 31 Oct— 00:43No data—
Fri 30 Oct— 00:51+8 min+8 min
Thu 29 Oct— 00:460 min—
Sun 25 OctHeerlen Woonboulevard 00:52No data—
Fri 23 Oct— 00:49No data—
Thu 22 Oct— 00:44No data—
Sun 18 OctHeerlen Woonboulevard 00:53Partial coverage0 min—
Sat 17 OctHeerlen Woonboulevard 00:52No data—
Sun 11 OctHeerlen Woonboulevard 00:520 min—
Sun 4 OctHeerlen Woonboulevard 00:52No data—
Sun 27 SeptHeerlen Woonboulevard 00:52No data—
Sun 20 SeptHeerlen Woonboulevard 00:54No data—
Sun 13 SeptHeerlen Woonboulevard 00:52No data—
Sun 6 SeptHeerlen Woonboulevard 00:52No data—
Sun 30 AugHeerlen Woonboulevard 00:53No data—
Sun 23 AugHeerlen Woonboulevard 00:52No data—