Train Arriva 32034 Maastricht Randwyck – Kerkrade Centrum

Maastricht Randwyck 12:05 → Kerkrade Centrum 12:57 Daily 0 h 52 min · 15 stops Arriva

✓ Today’s run finished

Today, last fix heading to Chevremont at 13:09 No data

  1. Maastricht Randwyck12:05
  2. Maastricht Noord12:14
  3. Valkenburg12:24
  4. Klimmen-Ransdaal12:32
  5. Heerlen Woonboulevard12:38
  6. Chevremont12:54
  7. Kerkrade Centrum12:57

Next service: tomorrow 12:05 from Maastricht Randwyck · Fri 6 Nov

Next departure 12:05 tomorrow · Maastricht Randwyck
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 16 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 73 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Kerkrade Centrum, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
12:05on time on time
12:08 / 12:11— —
12:14— —
12:17— —
12:21— —
12:24— —
12:28 / 12:29— —
12:32— —
12:35— —
12:38— —
12:41 / 12:45— —
12:49— —
12:52— —
12:54— —
12:57— —

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