S3 21365 Luzern – Brunnen

View line S3

Luzern 17:06 → Brunnen 17:52 Daily 0 h 46 min · 11 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Brunnen at 17:54 +2 min

  1. Luzern17:06
  2. Meggen Zentrum17:17
  3. Meggen17:19
  4. Küssnacht am Rigi17:25
  5. Arth-Goldau17:38
  6. Steinen17:43
  7. Brunnen17:52

Next service: tomorrow 17:06 from Luzern · Fri 13 Nov

Next departure 17:06 tomorrow · Luzern
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 3 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 Brunnen, 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

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

  • Early 0% · 0
  • On time 100% · 38
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=6
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 38 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:06on time on time
17:13≈ on time ≈ on time
17:17≈ on time ≈ on time
17:19≈ on time ≈ on time
17:22≈ on time ≈ +1 min
17:25 / 17:26≈ on time ≈ +1 min
17:29 / 17:30≈ on time ≈ +1 min
17:38 / 17:39≈ on time ≈ +1 min
17:43≈ on time ≈ +1 min
17:48≈ on time ≈ +1 min
17:52on 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
Thu 12 NovBrunnen 17:54+2 min+2 min
Wed 11 NovBrunnen 17:530 min—
Tue 10 NovBrunnen 17:530 min+1 min
Mon 9 NovBrunnen 17:52−1 min—
Sun 8 NovBrunnen 17:530 min—
Sat 7 NovBrunnen 17:54+2 min+2 min
Fri 6 NovBrunnen 17:530 min—
Thu 5 NovBrunnen 17:54+2 min+2 min
Wed 4 NovBrunnen 17:530 min—
Tue 3 NovBrunnen 17:530 min+2 min
Mon 2 NovBrunnen 17:530 min—
Sun 1 NovBrunnen 17:520 min—
Sat 31 OctBrunnen 17:55+2 min+2 min
Fri 30 OctBrunnen 17:52−1 min—
Thu 29 OctBrunnen 17:530 min—
Wed 28 OctBrunnen 17:530 min—
Tue 27 OctBrunnen 17:530 min—
Mon 26 OctBrunnen 17:530 min—
Sun 25 OctBrunnen 17:520 min—
Sat 24 OctBrunnen 17:53No data—
Fri 23 OctBrunnen 17:530 min—
Thu 22 OctBrunnen 17:53No data—
Wed 21 OctBrunnen 17:520 min—
Tue 20 OctBrunnen 17:53−1 min—
Mon 19 OctBrunnen 17:52−1 min—
Sun 18 OctBrunnen 17:530 min—
Sat 17 OctBrunnen 17:520 min—
Fri 16 OctBrunnen 17:53−1 min—
Thu 15 OctBrunnen 17:530 min—
Wed 14 OctBrunnen 17:52−1 min+1 min