S6 21617 Malters – Luzern

View line S6

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

✓ Today’s run finished

Today it reached Luzern at 06:45 +2 min

  1. Malters06:31
  2. Luzern Littau06:35
  3. Luzern06:43

Next service: tomorrow 06:31 from Malters · Sun 15 Nov

Next departure 06:31 tomorrow · Malters
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 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 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 13 Oct Max en route +7 min · last fix heading to Luzern +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 47
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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