Train Arriva 32454 Maastricht Randwyck – Sittard

Maastricht Randwyck 15:35 → Sittard 16:02 Daily 0 h 27 min · 6 stops Arriva

✓ Today’s run finished

Today, last fix heading to Geleen-Lutterade at 16:09 0 min

  1. Maastricht Randwyck15:35
  2. Maastricht15:38
  3. Bunde15:46
  4. Beek-Elsloo15:52
  5. Geleen-Lutterade15:55
  6. Sittard16:02

Next service: tomorrow 15:35 from Maastricht Randwyck · Mon 16 Nov

Next departure 15:35 tomorrow · Maastricht Randwyck
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 14 full · 2 partial · 14 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 22 full · 2 partial · 64 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 Sittard, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
15:35on time on time
15:38 / 15:41≈ on time ≈ on time
15:46≈ on time ≈ on time
15:52≈ on time ≈ +1 min
15:55 / 15:57≈ on time ≈ +1 min
16:02on time +1 min

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 15 NovGeleen-Lutterade 16:09Partial coverage0 min—
Sat 14 NovGeleen-Lutterade 16:12Partial coverage0 min—
Fri 13 NovGeleen-Lutterade 16:130 min—
Thu 12 NovEcht 16:34+1 min+1 min
Wed 11 NovEcht 16:34+2 min+2 min
Tue 10 NovEcht 16:330 min—
Mon 9 NovEcht 16:330 min—
Sun 8 NovEcht 16:330 min—
Sat 7 NovEcht 16:32No data—
Fri 6 NovEcht 16:34No data—
Thu 5 NovEcht 16:33No data—
Wed 4 NovEcht 16:330 min—
Tue 3 NovEcht 16:34No data—
Mon 2 NovEcht 16:34No data—
Sun 1 NovEcht 16:36+3 min+7 min
Sat 31 OctEcht 16:330 min—
Fri 30 OctEcht 16:35No data—
Thu 29 OctEcht 16:330 min—
Wed 28 OctEcht 16:330 min—
Tue 27 OctEcht 16:33No data—
Mon 26 OctEcht 16:33No data—
Sun 25 OctEcht 16:33No data—
Sat 24 OctEcht 16:330 min—
Fri 23 OctEcht 16:32No data—
Thu 22 OctEcht 16:32No data—
Wed 21 OctEcht 16:35No data—
Tue 20 OctEcht 16:330 min—
Mon 19 OctEcht 16:34No data—
Sun 18 OctEcht 16:330 min—
Sat 17 OctEcht 16:33No data—