Train Arriva 18927 Maastricht – Aachen Hbf

Maastricht 10:23 → Aachen Hbf 11:12 Mon, Tue, Wed, Thu, Fri, Sat 0 h 49 min · 9 stops Arriva

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 10:23 from Maastricht · Mon 9 Nov

Next departure 10:23 tomorrow · Maastricht
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 3 full · 8 partial · 13 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 3 full · 12 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Aachen Hbf, 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 24 Oct Max en route +3 min · last fix heading to Eygelshoven Markt +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 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=3
  • 100% T n=1
  • 100% F n=1
  • 80% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 15 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:23on time on time
10:28— —
10:33— —
10:45 / 10:48— —
10:52— —
10:55— —
10:59 / 11:00— —
11:07 / 11:08— —
11:12— —

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 7 NovEygelshoven Markt 11:12Partial coverage0 min—
Fri 6 NovEygelshoven Markt 11:24No data—
Thu 5 NovEygelshoven Markt 11:12No data—
Wed 4 NovEygelshoven Markt 11:12Partial coverage0 min—
Tue 3 NovEygelshoven Markt 11:09No data—
Mon 2 NovEygelshoven Markt 11:12No data—
Sat 31 OctEygelshoven Markt 11:12Partial coverage0 min—
Fri 30 OctEygelshoven Markt 11:12No data—
Thu 29 OctEygelshoven Markt 11:12No data—
Wed 28 OctEygelshoven Markt 11:13Partial coverage0 min—
Tue 27 OctEygelshoven Markt 11:12Partial coverage0 min—
Mon 26 OctEygelshoven Markt 11:12No data—
Sat 24 OctEygelshoven Markt 11:15+3 min+3 min
Fri 23 OctEygelshoven Markt 11:12No data—
Thu 22 OctEygelshoven Markt 11:14No data—
Wed 21 OctEygelshoven Markt 11:12No data—
Tue 20 OctEygelshoven Markt 11:12Partial coverage0 min—
Mon 19 OctEygelshoven Markt 11:24Partial coverage0 min—
Sat 17 OctEygelshoven Markt 11:110 min—
Fri 16 OctEygelshoven Markt 11:12No data—
Thu 15 OctEygelshoven Markt 11:12No data—
Tue 13 OctEygelshoven Markt 11:14Partial coverage0 min—
Mon 12 OctEygelshoven Markt 11:13No data—
Sat 10 OctEygelshoven Markt 11:120 min—
Fri 9 OctEygelshoven Markt 11:12Partial coverage0 min—
Thu 8 OctEygelshoven Markt 11:12Partial coverage0 min—
Wed 7 OctEygelshoven Markt 12:02Partial coverage0 min—
Tue 6 OctEygelshoven Markt 11:12Partial coverage0 min—
Mon 5 OctEygelshoven Markt 11:12No data—
Sat 3 OctEygelshoven Markt 11:15No data—