IR15 2513 Lausanne → Luzern

View line IR15

Lausanne 08:40 → Luzern 11:01 Daily 2 h 21 min · 7 stops SBB CFF FFS

IR15 2513 Lausanne–Luzern: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. Running now, on time. Expected at Luzern: 11:01. TrainsRadar data as of 22 Nov 2026, 10:44 (GMT+1).

Running now · updated 10:44

Position estimated from the timetable

Between Sursee and Luzern 0 min

Estimated arrival at Luzern 11:01 · 101 km/h

  1. Lausanne08:40
  2. Palézieux08:56
  3. Fribourg/Freiburg09:32
  4. Bern09:56
  5. Zofingen10:28
  6. Sursee10:41
  7. Luzern11:01

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

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
93%
53/57 runs under 3 min
RT coverage: 56 full · 1 partial · 0 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 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 18 Oct Max en route +21 min · last fix heading to Luzern +20 min
  • Sun 15 Nov Max en route +16 min · last fix heading to Nancy +15 min
  • Tue 13 Oct Max en route +13 min · last fix heading to Luzern +13 min
  • Thu 22 Oct Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 89% · 51
  • 3–10 min 2% · 1
  • 10–30 min 5% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 89% T n=9
  • 100% W n=8
  • 88% T n=8
  • 100% F n=7
  • 100% S n=7
  • 80% S n=10

Stops and timetable

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

Last 90 days, 57 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
08:40on time on timePassed
08:56 / 09:01≈ on time ≈ on timePassed
09:32 / 09:33≈ on time ≈ +1 minPassed
09:56 / 10:00≈ on time ≈ +1 minPassed
10:28 / 10:29≈ on time ≈ +2 minPassed
10:41 / 10:42≈ on time ≈ +2 minPassed
11:01on time +2 minNext

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
Sun 22 NovSursee 10:39Partial coverage0 min—
Sat 21 NovLuzern 11:020 min—
Fri 20 NovNancy 17:440 min—
Thu 19 NovNancy 17:440 min—
Wed 18 NovNancy 17:44+2 min+2 min
Tue 17 NovNancy 17:440 min+1 min
Mon 16 NovNancy 17:44−1 min—
Sun 15 NovNancy 17:44+15 min+16 min
Sat 14 NovLuzern 11:020 min—
Fri 13 NovNancy 17:440 min—
Thu 12 NovNancy 17:440 min—
Wed 11 NovNancy 17:440 min—
Tue 10 NovNancy 17:44+1 min—
Mon 9 NovNancy 17:44−1 min—
Sun 8 NovNancy 17:440 min—
Sat 7 NovLuzern 11:03+1 min—
Fri 6 NovNancy 17:44+1 min—
Thu 5 NovNancy 17:440 min—
Wed 4 NovNancy 17:44+1 min—
Tue 3 NovNancy 17:44+1 min+1 min
Mon 2 NovNancy 17:44−1 min—
Sun 1 NovLuzern 11:04+2 min+2 min
Sat 31 OctLuzern 11:03+1 min—
Fri 30 OctLuzern 11:01−1 min—
Thu 29 OctLuzern 11:020 min—
Wed 28 OctLuzern 11:04+2 min+2 min
Tue 27 OctLuzern 11:03+1 min—
Mon 26 OctLuzern 11:030 min+1 min
Sun 25 OctLuzern 11:20+2 min+2 min
Sat 24 OctLuzern 11:180 min—