S3 21316 Arth-Goldau – Luzern

View line S3

Arth-Goldau 05:20 → Luzern 05:53 Daily 0 h 33 min · 8 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Luzern at 05:54 No data

  1. Arth-Goldau05:20
  2. Immensee05:28
  3. Küssnacht am Rigi05:32
  4. Meggen05:39
  5. Meggen Zentrum05:40
  6. Luzern Verkehrshaus05:45
  7. Luzern05:53

Next service: tomorrow 05:20 from Arth-Goldau · Sat 21 Nov

Next departure 05:20 tomorrow · Arth-Goldau
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 3 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 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

  • Sun 15 Nov Max en route +4 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

  • Early 38% · 18
  • On time 60% · 29
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
05:20on time on time
05:28≈ on time ≈ on time
05:32≈ on time ≈ on time
05:35≈ on time ≈ on time
05:39≈ on time ≈ on time
05:40≈ on time ≈ on time
05:45≈ on time ≈ on time
05:531 min early +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
Fri 20 NovLuzern 05:54No data—
Thu 19 NovLuzern 05:54+1 min—
Wed 18 NovLuzern 05:54+1 min—
Tue 17 NovLuzern 05:540 min—
Mon 16 NovLuzern 05:52−1 min—
Sun 15 NovLuzern 05:58+4 min+4 min
Sat 14 NovLuzern 05:540 min—
Fri 13 NovLuzern 05:53−2 min—
Thu 12 NovLuzern 05:53−1 min—
Wed 11 NovLuzern 05:540 min—
Tue 10 NovLuzern 05:540 min—
Mon 9 NovLuzern 05:53−1 min—
Sun 8 NovLuzern 05:53−1 min—
Sat 7 NovLuzern 05:53−1 min—
Fri 6 NovLuzern 05:53−1 min—
Thu 5 NovLuzern 05:52−2 min—
Wed 4 NovLuzern 05:52−2 min—
Tue 3 NovLuzern 05:54−1 min—
Mon 2 NovLuzern 05:540 min—
Sun 1 NovLuzern 05:53−1 min—
Sat 31 OctLuzern 05:53−1 min—
Fri 30 OctLuzern 05:52−2 min—
Thu 29 OctLuzern 05:55+1 min—
Wed 28 OctLuzern 05:53−1 min—
Tue 27 OctLuzern 05:55+1 min—
Mon 26 OctLuzern 05:55+1 min+1 min
Sun 25 OctLuzern 05:530 min—
Sat 24 OctLuzern 05:53−1 min—
Fri 23 OctLuzern 05:53−1 min—
Thu 22 OctLuzern 05:53−1 min—