Train Arriva 32436 Maastricht Randwyck – Sittard

Maastricht Randwyck 11:05 → Sittard 11:32 Daily 0 h 27 min · 6 stops Arriva

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 11:05 from Maastricht Randwyck · Sun 15 Nov

Next departure 11:05 today · Maastricht Randwyck
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 partial · 13 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 19 full · 1 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

Stops and timetable

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

Last 90 days, 20 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
11:05on time on time
11:08 / 11:11≈ on time ≈ on time
11:16≈ on time ≈ +1 min
11:22≈ on time ≈ +1 min
11:25 / 11:27≈ on time ≈ +1 min
11:32on time +2 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
Sat 14 NovGeleen-Lutterade 11:39Partial coverage0 min—
Fri 13 NovGeleen-Lutterade 11:390 min—
Thu 12 NovEcht 12:020 min—
Wed 11 NovEcht 12:04+2 min+2 min
Tue 10 NovEcht 12:030 min—
Mon 9 NovEcht 12:030 min—
Sun 8 NovEcht 12:04+1 min+1 min
Sat 7 NovEcht 12:020 min—
Fri 6 NovEcht 12:03No data—
Thu 5 NovEcht 12:03No data—
Wed 4 NovEcht 12:030 min—
Tue 3 NovEcht 12:02No data—
Mon 2 NovEcht 12:02No data—
Sun 1 NovEcht 12:040 min—
Sat 31 OctEcht 12:020 min—
Fri 30 OctEcht 12:02No data—
Thu 29 OctEcht 12:02No data—
Wed 28 OctEcht 12:030 min—
Tue 27 OctEcht 12:030 min—
Mon 26 OctEcht 12:02No data—
Sun 25 OctEcht 12:02No data—
Sat 24 OctEcht 12:030 min—
Fri 23 OctEcht 12:02No data—
Thu 22 OctEcht 12:05No data—
Wed 21 OctEcht 12:02No data—
Tue 20 OctEcht 12:020 min—
Mon 19 OctEcht 12:03No data—
Sun 18 OctEcht 12:020 min—
Sat 17 OctEcht 12:02No data—
Fri 16 OctEcht 12:02No data—