IRLEX 2975 Engelberg – Luzern

View line IRLEX

Engelberg 14:02 → Luzern 14:49 Daily 0 h 47 min · 7 stops zb Zentralbahn

It has not run yet today

Last recorded run: Sunday 8 November +2 min

Next service: today 14:02 from Engelberg · Mon 9 Nov

Next departure 14:02 today · Engelberg
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 24 full · 0 partial · 5 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 33 full · 0 partial · 5 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: +3 min

Last 30 days

Arrival delay at Luzern, 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 23 Oct Max en route +7 min · last fix heading to Luzern +7 min
  • Sun 25 Oct Max en route +6 min · last fix heading to Luzern +6 min
  • Wed 21 Oct Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 6% · 2
  • On time 85% · 28
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 80% W n=5
  • 100% T n=1
  • 83% F n=6
  • 100% S n=5
  • 83% S n=6

Stops and timetable

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

Last 90 days, 33 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:02on time on time
14:17≈ on time ≈ +1 min
14:22≈ on time ≈ +1 min
14:24≈ on time ≈ +1 min
14:28 / 14:29≈ on time ≈ +2 min
14:34≈ on time ≈ +2 min
14:49on time +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
Sun 8 NovLuzern 14:52+2 min+2 min
Sat 7 NovLuzern 14:490 min—
Fri 6 NovLuzern 14:49+1 min—
Thu 5 NovLuzern 14:49No data—
Wed 4 NovLuzern 14:490 min—
Tue 3 NovLuzern 14:490 min—
Mon 2 NovLuzern 14:49No data—
Sun 1 NovLuzern 14:490 min—
Sat 31 OctLuzern 14:500 min—
Fri 30 OctLuzern 14:52+2 min+2 min
Thu 29 OctLuzern 14:50No data—
Wed 28 OctLuzern 14:500 min—
Tue 27 OctLuzern 14:52+1 min+1 min
Mon 26 OctLuzern 14:500 min—
Sun 25 OctLuzern 14:55+6 min+6 min
Sat 24 OctLuzern 14:51+1 min—
Fri 23 OctLuzern 14:56+7 min+7 min
Thu 22 OctLuzern 14:50No data—
Wed 21 OctLuzern 14:53+3 min+3 min
Tue 20 OctLuzern 14:51+1 min—
Mon 19 OctLuzern 14:52+2 min+2 min
Sun 18 OctLuzern 14:49−1 min—
Sat 17 OctLuzern 14:49−1 min—
Fri 16 OctLuzern 14:50−1 min—
Thu 15 OctLuzern 14:50No data—
Wed 14 OctLuzern 14:52+2 min+2 min
Tue 13 OctLuzern 14:500 min—
Mon 12 OctLuzern 14:500 min—
Sun 11 OctLuzern 14:49−1 min—
Sat 10 OctLuzern 14:49−1 min—