Train Arriva 18911 Heerlen – Aachen Hbf

Heerlen 06:48 → Aachen Hbf 07:12 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 6 stops Arriva

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 06:48 from Heerlen · Tue 17 Nov

Next departure 06:48 today · Heerlen
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 0 full · 17 partial · 3 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 0 full · 24 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +8 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

  • Fri 13 Nov Max en route +9 min · last fix heading to Eygelshoven Markt +9 min
  • Tue 10 Nov Max en route +9 min · last fix heading to Eygelshoven Markt +9 min
  • Thu 12 Nov Max en route +8 min · last fix heading to Eygelshoven Markt +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 21
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 100% W n=5
  • 80% T n=5
  • 80% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

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