Train Arriva 32028 Maastricht Randwyck – Kerkrade Centrum

Maastricht Randwyck 10:35 → Kerkrade Centrum 11:27 Daily 0 h 52 min · 15 stops Arriva

✓ Today’s run finished

Today, last fix heading to Chevremont at 11:39 No data

  1. Maastricht Randwyck10:35
  2. Maastricht Noord10:44
  3. Valkenburg10:54
  4. Klimmen-Ransdaal11:02
  5. Heerlen Woonboulevard11:08
  6. Chevremont11:24
  7. Kerkrade Centrum11:27

Next service: tomorrow 10:35 from Maastricht Randwyck · Fri 6 Nov

Next departure 10:35 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%
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: +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

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=3
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (15 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
10:35on time on time
10:38 / 10:41— —
10:44— —
10:47— —
10:51— —
10:54— —
10:58 / 10:59— —
11:02— —
11:05— —
11:08— —
11:11 / 11:15— —
11:19— —
11:22— —
11:24— —
11:27— —

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