LIX 2938 Luzern – Meiringen

View line LIX

Luzern 19:06 → Meiringen 20:16 Daily 1 h 10 min · 8 stops zb Zentralbahn

It has not run yet today

Last recorded run: Wednesday 18 November +3 min

Next service: today 19:06 from Luzern · Thu 19 Nov

Next departure 19:06 today · Luzern
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
47/47 runs under 3 min
RT coverage: 47 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 Meiringen, 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

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

  • Early 13% · 6
  • On time 87% · 41
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 47 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
19:06on time on time
19:24≈ on time ≈ on time
19:27 / 19:28≈ on time ≈ on time
19:35 / 19:37≈ on time ≈ on time
19:43 / 19:44≈ on time ≈ on time
19:50 / 19:51≈ on time ≈ +1 min
20:03≈ on time ≈ +1 min
20:16on 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
Wed 18 NovMeiringen 20:19+3 min+3 min
Tue 17 NovMeiringen 20:17−1 min—
Mon 16 NovMeiringen 20:14−1 min—
Sun 15 NovMeiringen 20:14−1 min—
Sat 14 NovMeiringen 20:16−1 min—
Fri 13 NovMeiringen 20:170 min—
Thu 12 NovMeiringen 20:15−1 min—
Wed 11 NovMeiringen 20:14−2 min—
Tue 10 NovMeiringen 20:170 min—
Mon 9 NovMeiringen 20:14−1 min—
Sun 8 NovMeiringen 20:170 min—
Sat 7 NovMeiringen 20:170 min—
Fri 6 NovMeiringen 20:18+1 min+1 min
Thu 5 NovMeiringen 20:180 min—
Wed 4 NovMeiringen 20:170 min—
Tue 3 NovMeiringen 20:170 min—
Mon 2 NovMeiringen 20:170 min—
Sun 1 NovMeiringen 20:19+1 min+1 min
Sat 31 OctMeiringen 20:18+1 min—
Fri 30 OctMeiringen 20:170 min—
Thu 29 OctMeiringen 20:18+1 min+1 min
Wed 28 OctMeiringen 20:17−1 min—
Tue 27 OctMeiringen 20:180 min—
Mon 26 OctMeiringen 20:18+1 min—
Sun 25 OctMeiringen 20:18+1 min—
Sat 24 OctMeiringen 20:19+2 min+2 min
Fri 23 OctMeiringen 20:18+1 min—
Thu 22 OctMeiringen 20:19+1 min+1 min
Wed 21 OctMeiringen 20:17+1 min—
Tue 20 OctMeiringen 20:18+1 min—