IRLEX 2970 Luzern – Engelberg

View line IRLEX

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

Running now · updated 12:46

Position estimated from the timetable

Between Grafenort and Engelberg No data

Estimated arrival at Engelberg 12:53 · 30 km/h

  1. Luzern12:10
  2. Stans12:24
  3. Dallenwil12:29
  4. Niederrickenbach Station12:30
  5. Wolfenschiessen12:34
  6. Grafenort12:38
  7. Engelberg12:53
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
97%
34/35 runs under 3 min
RT coverage: 35 full · 0 partial · 12 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

  • Sun 25 Oct Max en route +4 min · last fix heading to Wolfenschiessen +4 min

Distribution · 90 days

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

  • Early 17% · 6
  • On time 80% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 100% T n=1
  • 100% F n=6
  • 100% S n=6
  • 86% S n=7

Stops and timetable

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

Last 90 days, 35 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 10Today
12:10on time on timePassed
12:24≈ on time ≈ +1 minPassed
12:29≈ on time ≈ +1 minPassed
12:30≈ on time ≈ +1 minPassed
12:34≈ on time ≈ +1 minPassed
12:38≈ on time ≈ +1 minPassed
12:53+1 min +2 minNext

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
Thu 19 NovEngelberg 12:44No data—
Wed 18 NovEngelberg 12:53−1 min—
Tue 17 NovEngelberg 12:55+1 min—
Mon 16 NovEngelberg 12:54No data—
Sun 15 NovEngelberg 12:53−1 min—
Sat 14 NovEngelberg 12:54+1 min+1 min
Fri 13 NovEngelberg 12:49−3 min—
Thu 12 NovEngelberg 12:54No data—
Wed 11 NovEngelberg 12:54+1 min+1 min
Tue 10 NovEngelberg 12:540 min—
Mon 9 NovEngelberg 12:54No data—
Sun 8 NovEngelberg 12:53−1 min—
Sat 7 NovEngelberg 12:52−2 min—
Fri 6 NovEngelberg 12:52−2 min—
Thu 5 NovEngelberg 12:54No data—
Wed 4 NovEngelberg 12:52−3 min—
Tue 3 NovEngelberg 12:540 min—
Mon 2 NovEngelberg 12:54No data—
Sun 1 NovWolfenschiessen 12:37+2 min+3 min
Sat 31 OctWolfenschiessen 12:37+2 min+2 min
Fri 30 OctWolfenschiessen 12:36+1 min—
Thu 29 OctWolfenschiessen 12:35No data—
Wed 28 OctWolfenschiessen 12:38+3 min+3 min
Tue 27 OctWolfenschiessen 12:36+1 min—
Mon 26 OctWolfenschiessen 12:35No data—
Sun 25 OctWolfenschiessen 12:39+4 min+4 min
Sat 24 OctWolfenschiessen 12:37+2 min+2 min
Fri 23 OctWolfenschiessen 12:350 min—
Thu 22 OctWolfenschiessen 12:35No data—
Wed 21 OctWolfenschiessen 12:37+2 min+2 min