Train Arriva 32025 Kerkrade Centrum – Maastricht Randwyck

Kerkrade Centrum 10:01 → Maastricht Randwyck 11:00 Daily 0 h 59 min · 15 stops Arriva

✓ Today’s run finished

Today, last fix heading to Maastricht at 11:09 0 min

  1. Kerkrade Centrum10:01
  2. Eygelshoven10:06
  3. Heerlen Woonboulevard10:27
  4. Klimmen-Ransdaal10:34
  5. Valkenburg10:40
  6. Maastricht10:53
  7. Maastricht Randwyck11:00

Next service: tomorrow 10:01 from Kerkrade Centrum · Sat 14 Nov

Next departure 10:01 tomorrow · Kerkrade Centrum
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 0 full · 15 partial · 15 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 1 full · 20 partial · 67 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 Maastricht Randwyck, in minutes. One bar per run.

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

Worst days

  • Wed 11 Nov Max en route +5 min · last fix heading to Maastricht +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 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=3
  • 75% W n=4
  • 100% T n=3
  • 100% F n=2
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 21 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:01on time on time
10:03— —
10:06— —
10:09— —
10:13 / 10:24— —
10:27— —
10:30— —
10:34— —
10:37— —
10:40 / 10:41— —
10:44— —
10:47— —
10:50— —
10:53 / 10:57— —
11:00— —

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