L2 23436 Annemasse – Annecy

View line L2

Annemasse 11:19 → Annecy 12:16 Daily 0 h 57 min · 6 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: tomorrow 11:19 from Annemasse · Fri 6 Nov

Next departure 11:19 tomorrow · Annemasse
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 33 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: +1 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

  • Thu 29 Oct Max en route +10 min · last fix heading to Annecy +10 min
  • Mon 12 Oct Max en route +5 min · last fix heading to Annecy +5 min
  • Thu 22 Oct Max en route +4 min · last fix heading to Annecy +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 30
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=5
  • 50% T n=4
  • 100% F n=4
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 33 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
11:19on time on time
11:29 / 11:31≈ on time ≈ on time
11:38 / 11:42≈ on time ≈ on time
12:00 / 12:02≈ on time ≈ on time
12:10 / 12:11≈ on time ≈ on time
12: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
Wed 4 NovAnnecy 20:170 min—
Tue 3 NovAnnecy 20:170 min—
Mon 2 NovAnnecy 20:170 min—
Sun 1 NovAnnecy 20:170 min+5 min
Sat 31 OctAnnecy 20:170 min—
Fri 30 OctAnnecy 20:170 min—
Thu 29 OctAnnecy 20:27+10 min+10 min
Wed 28 OctAnnecy 20:170 min—
Tue 27 OctAnnecy 20:170 min—
Mon 26 OctAnnecy 20:170 min—
Sun 25 OctAnnecy 20:170 min—
Sat 24 OctAnnecy 20:170 min—
Fri 23 OctAnnecy 20:170 min—
Thu 22 OctAnnecy 20:21+4 min+4 min
Wed 21 OctAnnecy 20:170 min—
Tue 20 OctAnnecy 20:170 min—
Mon 19 OctAnnecy 20:170 min—
Sun 18 OctAnnecy 20:170 min—
Sat 17 OctAnnecy 20:170 min—
Fri 16 OctAnnecy 20:170 min—
Thu 15 OctAnnecy 20:170 min—
Wed 14 OctAnnecy 20:170 min—
Tue 13 OctAnnecy 20:170 min+5 min
Mon 12 OctAnnecy 20:22+5 min+5 min
Sun 11 OctAnnecy 20:170 min—
Sat 10 OctAnnecy 20:170 min—
Fri 9 OctAnnecy 20:180 min—
Thu 8 OctAnnecy 20:170 min—
Wed 7 OctAnnecy 20:180 min—
Tue 6 OctAnnecy 20:170 min—