IR15 2509 Genève-Aéroport – Luzern

View line IR15

Genève-Aéroport 05:45 → Luzern 09:01 Daily 3 h 16 min · 11 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Luzern at 09:01 0 min

  1. Genève-Aéroport05:45
  2. Nyon06:07
  3. Morges06:24
  4. Palézieux06:56
  5. Bern07:56
  6. Zofingen08:28
  7. Luzern09:01

Next service: tomorrow 05:45 from Genève-Aéroport · Thu 12 Nov

Next departure 05:45 tomorrow · Genève-Aéroport
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 41 full · 0 partial · 3 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 12 Oct Max en route +8 min · last fix heading to Luzern +8 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 95% · 39
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 41 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:45on time on time
05:52 / 05:54≈ on time ≈ on time
06:07 / 06:09≈ on time ≈ on time
06:24 / 06:26≈ on time ≈ on time
06:37 / 06:40≈ on time ≈ on time
06:56 / 07:01≈ on time ≈ +1 min
07:32 / 07:33≈ on time ≈ +1 min
07:56 / 08:00≈ on time ≈ +1 min
08:28 / 08:29≈ on time ≈ +1 min
08:41 / 08:42≈ on time ≈ +1 min
09: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
Wed 11 NovLuzern 09:020 min—
Tue 10 NovNancy 15:44+1 min+1 min
Mon 9 NovNancy 15:440 min—
Sun 8 NovLuzern 09:020 min+6 min
Sat 7 NovZweisimmen 06:54No data—
Fri 6 NovNancy 15:440 min—
Thu 5 NovNancy 15:440 min—
Wed 4 NovNancy 15:44+1 min+1 min
Tue 3 NovNancy 15:440 min—
Mon 2 NovNancy 15:440 min—
Sun 1 NovLuzern 09:020 min—
Sat 31 OctZweisimmen 06:55No data—
Fri 30 OctLuzern 09:020 min—
Thu 29 OctLuzern 09:020 min—
Wed 28 OctLuzern 09:04+1 min+1 min
Tue 27 OctLuzern 09:03+1 min+2 min
Mon 26 OctLuzern 09:030 min—
Sun 25 OctLuzern 09:180 min—
Sat 24 OctZweisimmen 06:56+1 min+1 min
Fri 23 OctLuzern 09:03+1 min—
Thu 22 OctLuzern 09:020 min—
Wed 21 OctLuzern 09:03+1 min+1 min
Tue 20 OctLuzern 09:04+1 min+1 min
Mon 19 OctLuzern 09:04+2 min+2 min
Sun 18 OctLuzern 09:020 min—
Sat 17 OctZweisimmen 06:55No data—
Fri 16 OctZweisimmen 06:54+1 min+12 min
Thu 15 OctLuzern 09:03+1 min—
Wed 14 OctLuzern 09:03+1 min+1 min
Tue 13 OctLuzern 09:04+2 min+2 min