IR15 2523 Lausanne – Luzern

View line IR15

Lausanne 13:40 → Luzern 16:01 Daily 2 h 21 min · 8 stops SBB CFF FFS

Running now · updated 15:39

Position estimated from the timetable

Between Zofingen and Sursee 0 min

Estimated arrival at Luzern 16:01 · 106 km/h

  1. Lausanne13:40
  2. Palézieux13:57
  3. Romont FR14:13
  4. Bern14:56
  5. Zofingen15:28
  6. Sursee15:41
  7. Luzern16:01

Today it is running no worse than usual: typical arrival delay is 0 min; 93% of the last 29 runs arrived on time.

On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 28 full · 1 partial · 1 no data
On-time · 90 days
93%
42/45 runs under 3 min
RT coverage: 44 full · 1 partial · 1 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

  • Mon 2 Nov Max en route +16 min · last fix heading to Luzern +15 min
  • Fri 9 Oct Max en route +15 min · last fix heading to Luzern +15 min
  • Sat 24 Oct Max en route +12 min · last fix heading to Luzern +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 42
  • 3–10 min 0% · 0
  • 10–30 min 7% · 3
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 45 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 10Today
13:40on time on timePassed
13:57≈ on time ≈ on timePassed
14:13≈ on time ≈ on timePassed
14:32 / 14:33≈ on time ≈ on timePassed
14:56 / 15:00≈ on time ≈ +1 minPassed
15:28 / 15:29≈ on time ≈ +1 minPassed
15:41 / 15:42≈ on time ≈ +1 minNext
16:01on 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 NovSursee 15:34Partial coverage0 min—
Fri 13 NovLuzern 16:020 min—
Thu 12 NovLuzern 16:03No data—
Wed 11 NovLuzern 16:03+1 min—
Tue 10 NovLuzern 16:020 min—
Mon 9 NovLuzern 16:020 min—
Sun 8 NovLuzern 16:020 min—
Sat 7 NovLuzern 16:020 min—
Fri 6 NovLuzern 16:03+1 min—
Thu 5 NovLuzern 16:020 min—
Wed 4 NovLuzern 16:020 min—
Tue 3 NovLuzern 16:020 min—
Mon 2 NovLuzern 16:18+15 min+16 min
Sun 1 NovLuzern 16:02+1 min—
Sat 31 OctLuzern 16:020 min—
Fri 30 OctLuzern 16:020 min—
Thu 29 OctLuzern 16:020 min—
Wed 28 OctLuzern 16:020 min—
Tue 27 OctLuzern 16:030 min—
Mon 26 OctLuzern 16:020 min—
Sun 25 OctLuzern 16:19−1 min—
Sat 24 OctLuzern 16:30+12 min+12 min
Fri 23 OctLuzern 16:020 min+2 min
Thu 22 OctLuzern 16:04+1 min+1 min
Wed 21 OctLuzern 16:020 min—
Tue 20 OctLuzern 16:020 min—
Mon 19 OctLuzern 16:020 min—
Sun 18 OctLuzern 16:020 min—
Sat 17 OctLuzern 16:03+1 min—
Fri 16 OctLuzern 16:030 min—