Train Arriva 18956 Aachen Hbf – Maastricht

Aachen Hbf 17:47 → Maastricht 18:41 Daily 0 h 54 min · 9 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 17:47 from Aachen Hbf · Sat 7 Nov

Next departure 17:47 today · Aachen Hbf
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 5 full · 10 partial · 12 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 5 full · 12 partial · 62 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: +2 min

Last 30 days

Arrival delay at Maastricht, in minutes. One bar per run.

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

Worst days

  • Sat 31 Oct Max en route +4 min · last fix heading to Meerssen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=2
  • — T n=0
  • 100% F n=3
  • 67% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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
17:47on time on time
17:50 / 17:51≈ on time ≈ on time
17:59 / 18:01≈ on time ≈ on time
18:05≈ on time ≈ on time
18:08 / 18:13≈ on time ≈ on time
18:17 / 18:19≈ on time ≈ +1 min
18:30≈ on time ≈ +1 min
18:35≈ on time ≈ +1 min
18:41on 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
Fri 6 NovMeerssen 18:44Partial coverage0 min+1 min
Thu 5 NovLandgraaf 18:27No data—
Wed 4 NovLandgraaf 18:27No data—
Tue 3 NovEygelshoven Markt 18:19No data—
Mon 2 NovEygelshoven Markt 18:19No data—
Sun 1 NovMeerssen 18:49Partial coverage+1 min+1 min
Sat 31 OctMeerssen 18:54Partial coverage+3 min+4 min
Fri 30 OctMeerssen 18:49No data—
Wed 28 OctLandgraaf 18:27Partial coverage0 min—
Tue 27 OctEygelshoven Markt 18:19Partial coverage0 min—
Mon 26 OctEygelshoven Markt 18:19No data—
Sun 25 OctMeerssen 19:01No data—
Sat 24 OctLandgraaf 18:280 min—
Fri 23 OctMeerssen 18:49Partial coverage+2 min+3 min
Thu 22 OctMeerssen 18:49No data—
Wed 21 OctMeerssen 18:49No data—
Tue 20 OctMeerssen 18:49Partial coverage0 min—
Mon 19 OctMeerssen 18:49Partial coverage0 min—
Sun 18 OctMeerssen 18:510 min—
Sat 17 OctMeerssen 18:52No data—
Fri 16 OctMeerssen 18:49No data—
Thu 15 OctValkenburg 18:44No data—
Tue 13 OctMeerssen 18:49Partial coverage0 min—
Mon 12 OctMeerssen 18:490 min—
Sun 11 OctMeerssen 18:52+2 min+2 min
Sat 10 OctMeerssen 18:510 min—
Fri 9 OctMeerssen 18:49Partial coverage0 min—
Wed 7 OctEygelshoven Markt 18:19Partial coverage0 min—
Mon 5 OctEygelshoven Markt 18:19Partial coverage0 min—
Sun 4 OctMeerssen 18:52No data—