Train Arriva 32020 Maastricht Randwyck – Kerkrade Centrum

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

✓ Today’s run finished

Today, last fix heading to Chevremont at 09:39 0 min

  1. Maastricht Randwyck08:35
  2. Maastricht Noord08:44
  3. Valkenburg08:54
  4. Klimmen-Ransdaal09:02
  5. Heerlen Woonboulevard09:08
  6. Chevremont09:24
  7. Kerkrade Centrum09:27

Next service: tomorrow 08:35 from Maastricht Randwyck · Sat 14 Nov

Next departure 08:35 tomorrow · Maastricht Randwyck
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 0 full · 16 partial · 14 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 0 full · 22 partial · 66 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: 0 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

Worst days

  • Thu 12 Nov Max en route +4 min · last fix heading to Chevremont +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=4
  • 100% W n=4
  • 50% T n=2
  • 100% F n=2
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 22 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
08:35on time on time
08:38 / 08:41— —
08:44— —
08:47— —
08:51— —
08:54— —
08:58 / 08:59— —
09:02— —
09:05— —
09:08— —
09:11 / 09:15— —
09:19— —
09:22— —
09:24— —
09: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
Fri 13 NovChevremont 09:39Partial coverage0 min—
Thu 12 NovChevremont 09:43Partial coverage+3 min+4 min
Wed 11 NovChevremont 09:39Partial coverage+1 min—
Tue 10 NovChevremont 09:39Partial coverage0 min—
Mon 9 NovChevremont 09:39Partial coverage0 min—
Sun 8 NovChevremont 09:39Partial coverage0 min—
Sat 7 NovChevremont 09:39Partial coverage0 min—
Fri 6 NovChevremont 09:39No data—
Thu 5 NovChevremont 09:39No data—
Wed 4 NovChevremont 09:39Partial coverage0 min—
Tue 3 NovChevremont 09:39No data—
Mon 2 NovChevremont 09:44No data—
Sun 1 NovChevremont 09:40Partial coverage0 min—
Sat 31 OctChevremont 09:40Partial coverage0 min—
Fri 30 OctChevremont 09:42No data—
Thu 29 OctChevremont 09:40No data—
Wed 28 OctChevremont 09:39Partial coverage0 min—
Tue 27 OctChevremont 09:40Partial coverage0 min—
Mon 26 OctChevremont 09:40No data—
Sun 25 OctChevremont 09:40No data—
Sat 24 OctChevremont 09:52Partial coverage0 min—
Fri 23 OctChevremont 09:39No data—
Thu 22 OctChevremont 09:40No data—
Wed 21 OctChevremont 09:40No data—
Tue 20 OctChevremont 09:40Partial coverage0 min—
Mon 19 OctChevremont 09:41No data—
Sun 18 OctChevremont 09:39Partial coverage0 min—
Sat 17 OctChevremont 09:39Partial coverage0 min—
Fri 16 OctChevremont 09:41No data—
Thu 15 OctChevremont 09:40No data—