S1 21188 Sursee – Zug

View line S1

Sursee 00:18 → Zug 01:22 Daily 1 h 04 min · 20 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Zug at 01:23 +1 min

  1. Sursee00:18
  2. Sempach-Neuenkirch00:26
  3. Emmenbrücke Gersag00:36
  4. Buchrain01:00
  5. Rotkreuz01:08
  6. Cham Alpenblick01:16
  7. Zug01:22

Next service: tomorrow 00:18 from Sursee · Sun 8 Nov

Next departure 00:18 tomorrow · Sursee
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
68/71 runs under 3 min
RT coverage: 71 full · 0 partial · 0 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: +1 min

Last 30 days

Arrival delay at Zug, 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 +31 min · last fix heading to Zug +31 min
  • Sat 26 Sept Max en route +6 min · last fix heading to Cham Alpenblick +6 min
  • Tue 1 Sept Max en route +10 min · last fix heading to Luzern +5 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 93% · 66
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 1% · 1

On-time by weekday

  • 100% M n=10
  • 83% T n=12
  • 100% W n=12
  • 100% T n=9
  • 100% F n=9
  • 89% S n=9
  • 100% S n=10

Stops and timetable

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

Last 90 days, 71 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
00:18on time +1 min
00:20≈ on time ≈ +1 min
00:22≈ on time ≈ +1 min
00:26 / 00:27≈ on time ≈ +1 min
00:31≈ on time ≈ +1 min
00:33≈ on time ≈ +1 min
00:36≈ on time ≈ +1 min
00:38≈ on time ≈ +1 min
00:45 / 00:51≈ on time ≈ +1 min
00:58≈ on time ≈ +1 min
01:00≈ on time ≈ +1 min
01:02≈ on time ≈ +1 min
01:05≈ +1 min ≈ +1 min
01:08 / 01:10≈ +1 min ≈ +1 min
01:13≈ on time ≈ +2 min
01:15≈ on time ≈ +2 min
01:16≈ on time ≈ +2 min
01:18≈ on time ≈ +2 min
01:20≈ on time ≈ +2 min
01:22on 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
Sat 7 NovZug 01:24+1 min+1 min
Fri 6 NovZug 01:24+1 min+1 min
Thu 5 NovZug 01:24+1 min+1 min
Wed 4 NovLuzern 00:44−1 min—
Tue 3 NovLuzern 00:44−1 min—
Mon 2 NovZug 01:24+1 min+2 min
Sun 1 NovZug 01:230 min—
Sat 31 OctZug 01:230 min—
Fri 30 OctLuzern 00:45−1 min—
Thu 29 OctLuzern 00:460 min—
Wed 28 OctLuzern 00:48+1 min+1 min
Tue 27 OctLuzern 00:470 min—
Mon 26 OctLuzern 00:450 min—
Sun 25 OctZug 01:23+1 min—
Sat 24 OctZug 01:22−1 min—
Fri 23 OctZug 01:230 min+1 min
Thu 22 OctZug 01:230 min+1 min
Wed 21 OctZug 01:24+1 min+1 min
Tue 20 OctZug 01:230 min+1 min
Mon 19 OctZug 01:24+1 min+2 min
Sun 18 OctZug 01:24+1 min—
Sat 17 OctZug 01:230 min—
Fri 16 OctZug 01:23+1 min+1 min
Thu 15 OctZug 01:240 min+1 min
Wed 14 OctZug 01:22−1 min+1 min
Tue 13 OctZug 01:23+31 min+31 min
Mon 12 OctZug 01:25+2 min+2 min
Sun 11 OctZug 01:230 min—
Sat 10 OctZug 01:230 min—
Fri 9 OctZug 01:230 min+1 min