Train Arriva 18951 Maastricht – Aachen Hbf

Maastricht 16:23 → Aachen Hbf 17:12 Daily 0 h 49 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Eygelshoven Markt at 17:13 0 min

  1. Maastricht16:23
  2. Meerssen16:28
  3. Heerlen16:45
  4. Landgraaf16:52
  5. Eygelshoven Markt16:55
  6. Herzogenrath16:59
  7. Aachen Hbf17:12

Next service: tomorrow 16:23 from Maastricht · Sun 8 Nov

Next departure 16:23 tomorrow · Maastricht
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 5 full · 11 partial · 13 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 5 full · 15 partial · 68 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 Aachen Hbf, 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=3
  • 100% T n=4
  • 100% W n=3
  • 100% T n=1
  • 100% F n=2
  • 100% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
16:23on time on time
16:28≈ on time ≈ on time
16:33≈ on time ≈ on time
16:45 / 16:48≈ on time ≈ +1 min
16:52≈ on time ≈ +1 min
16:55≈ on time ≈ +1 min
16:59 / 17:00≈ on time ≈ +1 min
17:07 / 17:08≈ on time ≈ +1 min
17:12on 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
Sat 7 NovEygelshoven Markt 17:13Partial coverage0 min—
Fri 6 NovEygelshoven Markt 17:13Partial coverage0 min—
Thu 5 NovEygelshoven Markt 17:09No data—
Wed 4 NovEygelshoven Markt 17:09Partial coverage0 min—
Tue 3 NovEygelshoven Markt 17:09No data—
Mon 2 NovEygelshoven Markt 17:09No data—
Sun 1 NovEygelshoven Markt 17:12Partial coverage0 min—
Sat 31 OctEygelshoven Markt 17:14Partial coverage+1 min+1 min
Fri 30 OctEygelshoven Markt 17:15No data—
Thu 29 OctEygelshoven Markt 17:09No data—
Wed 28 OctEygelshoven Markt 17:10Partial coverage0 min—
Tue 27 OctEygelshoven Markt 17:09Partial coverage0 min—
Mon 26 OctEygelshoven Markt 17:09No data—
Sun 25 OctEygelshoven Markt 17:15No data—
Sat 24 OctEygelshoven Markt 17:14+2 min+2 min
Fri 23 OctEygelshoven Markt 17:21No data—
Thu 22 OctEygelshoven Markt 17:09No data—
Wed 21 OctEygelshoven Markt 17:14No data—
Tue 20 OctEygelshoven Markt 17:12Partial coverage0 min—
Mon 19 OctEygelshoven Markt 17:12Partial coverage0 min—
Sun 18 OctEygelshoven Markt 17:110 min—
Sat 17 OctEygelshoven Markt 17:12No data—
Fri 16 OctEygelshoven Markt 17:12No data—
Thu 15 OctEygelshoven Markt 17:12No data—
Tue 13 OctEygelshoven Markt 17:09Partial coverage0 min—
Mon 12 OctEygelshoven Markt 17:120 min—
Sun 11 OctEygelshoven Markt 17:130 min—
Sat 10 OctEygelshoven Markt 17:130 min—
Fri 9 OctEygelshoven Markt 17:13Partial coverage0 min—
Thu 8 OctEygelshoven Markt 17:09Partial coverage+1 min—