IRLEX 2973 Engelberg – Luzern

View line IRLEX

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

✓ Today’s run finished

Today, last fix heading to Luzern at 13:49 No data

  1. Engelberg13:02
  2. Grafenort13:17
  3. Wolfenschiessen13:22
  4. Niederrickenbach Station13:24
  5. Dallenwil13:28
  6. Stans13:34
  7. Luzern13:49

Next service: tomorrow 13:02 from Engelberg · Tue 10 Nov

Next departure 13:02 tomorrow · Engelberg
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
100%
32/32 runs under 3 min
RT coverage: 32 full · 0 partial · 9 no data
Typical delay
0min
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 Luzern, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 3% · 1
  • On time 97% · 31
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 100% W n=5
  • 100% T n=2
  • 100% F n=5
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

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