IRLEX 2967 Engelberg – Luzern

View line IRLEX

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

✓ Today’s run finished

Today it reached Luzern at 17:49 0 min

  1. Engelberg17:02
  2. Grafenort17:17
  3. Wolfenschiessen17:22
  4. Niederrickenbach Station17:24
  5. Dallenwil17:28
  6. Stans17:34
  7. Luzern17:49

Next service: tomorrow 17:02 from Engelberg · Fri 13 Nov

Next departure 17:02 tomorrow · Engelberg
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
95%
40/42 runs under 3 min
RT coverage: 42 full · 0 partial · 1 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 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

  • Tue 20 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Mon 19 Oct Max en route +5 min · last fix heading to Luzern +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 40
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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