S6 21649 Malters – Luzern

View line S6

Malters 14:31 → Luzern 14:43 Daily 0 h 12 min · 3 stops BLS

✓ Today’s run finished

Today it reached Luzern at 14:44 +1 min

  1. Malters14:31
  2. Luzern Littau14:35
  3. Luzern14:43

Next service: tomorrow 14:31 from Malters · Mon 16 Nov

Next departure 14:31 tomorrow · Malters
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
95%
39/41 runs under 3 min
RT coverage: 41 full · 0 partial · 11 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: +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

  • Sat 24 Oct Max en route +4 min · last fix heading to Luzern +4 min
  • Sun 25 Oct Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 90% · 37
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 100% W n=7
  • 100% T n=2
  • 100% F n=8
  • 86% S n=7
  • 90% S n=10

Stops and timetable

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

Last 90 days, 41 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:31+1 min +1 min
14:35≈ on time ≈ +1 min
14:43on 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 15 NovLuzern 14:44+1 min—
Sat 14 NovLuzern 14:440 min—
Fri 13 NovLuzern 14:440 min—
Thu 12 NovLuzern 14:44No data—
Wed 11 NovLuzern 14:440 min—
Tue 10 NovLuzern 14:440 min—
Mon 9 NovLuzern 14:44No data—
Sun 8 NovLuzern 14:440 min—
Sat 7 NovLuzern 14:43−1 min—
Fri 6 NovLuzern 14:44+1 min—
Thu 5 NovLuzern 14:44No data—
Wed 4 NovLuzern 14:43−1 min—
Tue 3 NovLuzern 14:440 min—
Mon 2 NovLuzern 14:44No data—
Sun 1 NovLuzern 14:46+2 min+2 min
Sat 31 OctLuzern 14:440 min—
Fri 30 OctLuzern 14:440 min—
Thu 29 OctLuzern 14:44No data—
Wed 28 OctLuzern 14:45+1 min—
Tue 27 OctLuzern 14:440 min—
Mon 26 OctLuzern 14:44No data—
Sun 25 OctLuzern 14:47+3 min+3 min
Sat 24 OctLuzern 14:48+4 min+4 min
Fri 23 OctLuzern 14:45+2 min+2 min
Thu 22 OctLuzern 14:44No data—
Wed 21 OctLuzern 14:440 min—
Tue 20 OctLuzern 14:440 min—
Mon 19 OctLuzern 14:44No data—
Sun 18 OctLuzern 14:46+2 min+2 min
Sat 17 OctLuzern 14:44+1 min—