S6 21681 Malters – Luzern

View line S6

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 18:31 from Malters · Mon 16 Nov

Next departure 18:31 today · Malters
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
94%
48/51 runs under 3 min
RT coverage: 51 full · 0 partial · 1 no data
Typical delay
+1min
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

  • Thu 29 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Mon 2 Nov Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 48
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=7
  • 100% W n=8
  • 67% T n=6
  • 100% F n=8
  • 100% S n=9
  • 100% S n=7

Stops and timetable

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

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