IRLEX 2993 Engelberg – Luzern

View line IRLEX

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 18:02 from Engelberg · Mon 16 Nov

Next departure 18:02 today · Engelberg
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
45/46 runs under 3 min
RT coverage: 46 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Mon 9 Nov Max en route +4 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=7
  • 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, 46 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
18:02on time on time
18:17≈ on time ≈ on time
18:22≈ on time ≈ on time
18:24≈ on time ≈ +1 min
18:28 / 18:29≈ on time ≈ +1 min
18:34≈ on time ≈ +1 min
18:49on time +1 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 15 NovLuzern 23:490 min—
Sat 14 NovLuzern 23:52+1 min+1 min
Fri 13 NovLuzern 23:490 min—
Thu 12 NovLuzern 23:50+1 min+1 min
Wed 11 NovLuzern 23:490 min—
Tue 10 NovLuzern 23:490 min—
Mon 9 NovLuzern 23:55+4 min+4 min
Sun 8 NovLuzern 23:490 min—
Sat 7 NovLuzern 23:49−1 min—
Fri 6 NovLuzern 23:490 min—
Thu 5 NovLuzern 23:49−1 min—
Wed 4 NovLuzern 23:49−1 min—
Tue 3 NovLuzern 23:490 min—
Mon 2 NovLuzern 23:52+2 min+2 min
Sun 1 NovLuzern 23:49−1 min—
Sat 31 OctLuzern 23:49−1 min—
Fri 30 OctLuzern 23:48−2 min—
Thu 29 OctLuzern 23:500 min—
Wed 28 OctLuzern 23:500 min—
Tue 27 OctLuzern 23:510 min—
Mon 26 OctLuzern 23:50−1 min—
Sun 25 OctLuzern 23:500 min—
Sat 24 OctLuzern 23:500 min—
Fri 23 OctLuzern 23:52+2 min+2 min
Thu 22 OctLuzern 23:49−1 min—
Wed 21 OctLuzern 23:490 min—
Tue 20 OctLuzern 23:50−1 min—
Mon 19 OctLuzern 23:51+1 min—
Sun 18 OctLuzern 23:500 min—
Sat 17 OctLuzern 23:500 min—