IRLEX 2972 Luzern – Engelberg

View line IRLEX

Luzern 13:10 → Engelberg 13:53 Daily 0 h 43 min · 7 stops zb Zentralbahn

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 13:10 from Luzern · Thu 12 Nov

Next departure 13:10 today · Luzern
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
98%
43/44 runs under 3 min
RT coverage: 44 full · 0 partial · 8 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Engelberg, 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 30 Oct Max en route +5 min · last fix heading to Wolfenschiessen +5 min

Distribution · 90 days

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

  • Early 7% · 3
  • On time 91% · 40
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=8
  • 100% W n=8
  • 100% T n=4
  • 83% F n=6
  • 100% S n=7
  • 100% S n=8

Stops and timetable

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

Last 90 days, 44 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
13:10on time on time
13:24≈ on time ≈ +1 min
13:29≈ on time ≈ +1 min
13:30≈ on time ≈ +1 min
13:34≈ on time ≈ +1 min
13:38≈ on time ≈ +1 min
13:53+1 min +2 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
Wed 11 NovEngelberg 13:540 min—
Tue 10 NovEngelberg 13:53−2 min—
Mon 9 NovEngelberg 13:54No data—
Sun 8 NovEngelberg 13:57+2 min+2 min
Sat 7 NovEngelberg 13:49−2 min—
Fri 6 NovEngelberg 13:54+2 min+2 min
Thu 5 NovEngelberg 13:53−1 min—
Wed 4 NovEngelberg 13:53−1 min—
Tue 3 NovEngelberg 13:54+1 min—
Mon 2 NovEngelberg 13:54No data—
Sun 1 NovWolfenschiessen 13:350 min—
Sat 31 OctWolfenschiessen 13:35+1 min—
Fri 30 OctWolfenschiessen 13:40+5 min+5 min
Thu 29 OctWolfenschiessen 13:35No data—
Wed 28 OctWolfenschiessen 13:36+1 min+1 min
Tue 27 OctWolfenschiessen 13:36+1 min+2 min
Mon 26 OctWolfenschiessen 13:35No data—
Sun 25 OctWolfenschiessen 13:36+2 min+2 min
Sat 24 OctWolfenschiessen 13:36+1 min+1 min
Fri 23 OctWolfenschiessen 13:36+1 min+1 min
Thu 22 OctWolfenschiessen 13:35No data—
Wed 21 OctWolfenschiessen 13:38+3 min+3 min
Tue 20 OctWolfenschiessen 13:36+1 min—
Mon 19 OctWolfenschiessen 13:35No data—
Sun 18 OctStansstad 13:230 min—
Sat 17 OctStansstad 13:220 min—
Fri 16 OctStansstad 13:24+1 min+1 min
Thu 15 OctStansstad 13:22No data—
Wed 14 OctStansstad 13:23+1 min—
Tue 13 OctStansstad 13:230 min—