L2 23416 Coppet – Annecy

View line L2

Coppet 08:19 → Annecy 10:16 Daily 1 h 57 min · 22 stops SNCF

✓ Today’s run finished

Today it reached Annecy at 10:16 0 min

  1. Coppet08:19
  2. Versoix08:27
  3. Les Tuileries08:34
  4. Lancy-Pont-Rouge08:51
  5. Genève-Eaux-Vives09:01
  6. La Roche-sur-Foron09:38
  7. Annecy10:16

Next service: tomorrow 08:19 from Coppet · Sat 7 Nov

Next departure 08:19 tomorrow · Coppet
On-time · 30 days
87%
26/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
92%
45/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Annecy, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 4 Nov Max en route +40 min · last fix heading to Annecy +35 min
  • Thu 29 Oct Max en route +20 min · last fix heading to Annecy +20 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Annecy +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Annemasse +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 45
  • 3–10 min 4% · 2
  • 10–30 min 2% · 1
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 88% W n=8
  • 75% T n=8
  • 100% F n=8
  • 100% S n=4
  • 80% S n=5

Stops and timetable

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

Last 90 days, 49 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
08:19on time on time
08:21≈ on time ≈ on time
08:22 / 08:23≈ on time ≈ on time
08:25≈ on time ≈ on time
08:27≈ on time ≈ on time
08:29 / 08:30≈ on time ≈ on time
08:32≈ on time ≈ on time
08:34≈ on time ≈ on time
08:36 / 08:37≈ on time ≈ on time
08:40≈ on time ≈ on time
08:44 / 08:46≈ on time ≈ on time
08:51 / 08:52≈ on time ≈ on time
08:55≈ on time ≈ on time
08:58≈ on time ≈ on time
09:01 / 09:02≈ on time ≈ on time
09:05≈ on time ≈ on time
09:10 / 09:18≈ on time ≈ on time
09:29 / 09:31≈ on time ≈ on time
09:38 / 09:42≈ on time ≈ on time
10:00 / 10:02≈ on time ≈ on time
10:10 / 10:11≈ on time ≈ on time
10:16on time on time

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 6 NovAnnecy 10:170 min—
Thu 5 NovAnnecy 10:170 min—
Wed 4 NovAnnecy 10:52+35 min+40 min
Tue 3 NovAnnecy 10:180 min—
Mon 2 NovAnnecy 10:170 min—
Sun 1 NovAnnecy 10:180 min—
Sat 31 OctAnnecy 10:170 min—
Fri 30 OctAnnecy 10:170 min—
Thu 29 OctAnnecy 10:37+20 min+20 min
Wed 28 OctAnnecy 10:170 min—
Tue 27 OctAnnecy 10:170 min—
Mon 26 OctAnnecy 10:170 min—
Sun 25 OctAnnecy 10:170 min—
Sat 24 OctAnnecy 10:170 min—
Fri 23 OctAnnecy 10:170 min—
Thu 22 OctAnnecy 10:170 min—
Wed 21 OctAnnecy 10:170 min—
Tue 20 OctAnnecy 10:170 min—
Mon 19 OctAnnecy 10:170 min—
Sun 18 OctAnnecy 10:170 min—
Sat 17 OctAnnecy 10:170 min—
Fri 16 OctAnnecy 10:170 min—
Thu 15 OctAnnecy 10:170 min—
Wed 14 OctAnnecy 10:170 min—
Tue 13 OctAnnecy 10:170 min—
Mon 12 OctAnnecy 10:180 min—
Sun 11 OctAnnecy 10:22+5 min+5 min
Sat 10 OctAnnecy 10:170 min—
Fri 9 OctAnnemasse 09:110 min—
Thu 8 OctAnnemasse 09:16+5 min+5 min