Train Arriva 18974 Heerlen – Liège-Guillemins

Heerlen 22:49 → Liège-Guillemins 23:50 Daily 1 h 01 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Valkenburg at 23:14 0 min

  1. Heerlen22:49
  2. Valkenburg23:00
  3. Meerssen23:05
  4. Maastricht23:11
  5. Maastricht Randwyck23:18
  6. Eijsden23:26
  7. Liège-Guillemins23:50

Next service: tomorrow 22:49 from Heerlen · Sun 15 Nov

Next departure 22:49 tomorrow · Heerlen
On-time · 30 days
60%
3/5 runs under 3 min
RT coverage: 4 full · 1 partial · 3 no data
On-time · 90 days
67%
4/6 runs under 3 min
RT coverage: 5 full · 1 partial · 15 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: +6 min

Last 30 days

Arrival delay at Liège-Guillemins, in minutes. One bar per run.

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

Worst days

  • Sun 8 Nov Max en route +10 min · last fix heading to Eijsden +7 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Meerssen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 4
  • 3–10 min 33% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=2
  • 50% S n=4

Stops and timetable

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

Last 90 days, 6 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
22:49on time on time
23:00≈ on time ≈ +1 min
23:05≈ on time ≈ +2 min
23:11 / 23:16≈ on time ≈ +2 min
23:18 / 23:20≈ on time ≈ +3 min
23:26 / 23:27≈ on time ≈ +4 min
23:32 / 23:33≈ on time ≈ +4 min
23:42 / 23:43≈ on time ≈ +5 min
23:50on time +6 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 14 NovValkenburg 23:14Partial coverage0 min—
Sun 8 NovEijsden 23:49+7 min+10 min
Sat 7 NovMaastricht Randwyck 23:340 min—
Sun 1 NovEijsden 23:390 min—
Sat 31 OctMaastricht Randwyck 23:34No data—
Sun 25 OctEijsden 23:42No data—
Sun 18 OctMeerssen 23:21+4 min+4 min
Sat 17 OctMeerssen 23:22No data—
Sun 11 OctMeerssen 23:200 min—
Sun 4 OctMeerssen 23:20No data—
Sat 3 OctMeerssen 23:15No data—
Sun 27 SeptMeerssen 23:22No data—
Sat 26 SeptMeerssen 23:19No data—
Sun 20 SeptEijsden 23:41No data—
Sat 19 SeptValkenburg 23:08No data—
Sun 13 SeptEijsden 23:41No data—
Sat 12 SeptEijsden 23:41No data—
Sun 6 SeptEijsden 23:47No data—
Sun 30 AugEijsden 23:41No data—
Sun 23 AugEijsden 23:42No data—
Sat 22 AugEijsden 23:41No data—