Train Arriva 18943 Maastricht – Aachen Hbf

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

✓ Today’s run finished

Today, last fix heading to Eygelshoven Markt at 15:12 0 min

  1. Maastricht14:23
  2. Meerssen14:28
  3. Heerlen14:45
  4. Landgraaf14:52
  5. Eygelshoven Markt14:55
  6. Herzogenrath14:59
  7. Aachen Hbf15:12

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

Next departure 14:23 tomorrow · Maastricht
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 5 full · 10 partial · 14 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 5 full · 14 partial · 69 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: +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

Worst days

  • Sat 24 Oct Max en route +4 min · last fix heading to Eygelshoven Markt +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
14:23on time on time
14:28≈ on time ≈ on time
14:33≈ on time ≈ +1 min
14:45 / 14:48≈ on time ≈ +1 min
14:52≈ on time ≈ +2 min
14:55≈ on time ≈ +2 min
14:59 / 15:00≈ on time ≈ +2 min
15:07 / 15:08≈ on time ≈ +3 min
15:12on time +3 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 15:12Partial coverage0 min—
Fri 6 NovEygelshoven Markt 15:12No data—
Thu 5 NovEygelshoven Markt 15:12No data—
Wed 4 NovEygelshoven Markt 15:12Partial coverage0 min—
Tue 3 NovEygelshoven Markt 15:12No data—
Mon 2 NovEygelshoven Markt 15:12No data—
Sun 1 NovEygelshoven Markt 15:13Partial coverage0 min—
Sat 31 OctEygelshoven Markt 15:13Partial coverage0 min—
Fri 30 OctEygelshoven Markt 15:20No data—
Thu 29 OctEygelshoven Markt 15:14Partial coverage0 min—
Wed 28 OctEygelshoven Markt 15:12Partial coverage0 min—
Tue 27 OctEygelshoven Markt 15:12No data—
Mon 26 OctEygelshoven Markt 15:12No data—
Sun 25 OctEygelshoven Markt 15:12No data—
Sat 24 OctEygelshoven Markt 15:16+4 min+4 min
Fri 23 OctEygelshoven Markt 15:18No data—
Thu 22 OctEygelshoven Markt 15:29No data—
Wed 21 OctEygelshoven Markt 15:12No data—
Tue 20 OctEygelshoven Markt 15:12Partial coverage0 min—
Mon 19 OctEygelshoven Markt 15:16Partial coverage0 min—
Sun 18 OctEygelshoven Markt 15:12+1 min—
Sat 17 OctValkenburg 14:470 min—
Fri 16 OctEygelshoven Markt 15:12No data—
Thu 15 OctEygelshoven Markt 15:13No data—
Tue 13 OctEygelshoven Markt 15:12Partial coverage0 min—
Mon 12 OctEygelshoven Markt 15:12No data—
Sun 11 OctEygelshoven Markt 15:120 min—
Sat 10 OctEygelshoven Markt 15:120 min—
Fri 9 OctEygelshoven Markt 15:15Partial coverage+2 min+3 min
Thu 8 OctEygelshoven Markt 15:14Partial coverage+2 min+2 min