L4 23239 Annemasse → Coppet

View line L4

Annemasse 11:20 → Coppet 12:11 Daily 0 h 51 min · 17 stops SNCF

TER 23239 Annemasse–Coppet: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 23:52 (GMT+1).

✓ Today’s run finished

Today it reached Coppet at 12:11 0 min

  1. Annemasse11:20
  2. Genève-Champel11:30
  3. Lancy-Pont-Rouge11:36
  4. Chambésy11:50
  5. Creux-de-Genthod11:58
  6. Pont-Céard12:04
  7. Coppet12:11

Next service: tomorrow 11:20 from Annemasse · Sun 22 Nov

Next departure 11:20 tomorrow · Annemasse
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
64/66 runs under 3 min
RT coverage: 65 full · 1 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: 0 min

Last 30 days

Arrival delay at Coppet, 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 8 Oct Max en route +25 min · last fix heading to Coppet +25 min
  • Mon 16 Nov Max en route +5 min · last fix heading to Coppet +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 64
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=13
  • 100% T n=11
  • 100% W n=8
  • 92% T n=13
  • 100% F n=7
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 66 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:20on time on time
11:24≈ on time ≈ on time
11:27 / 11:28≈ on time ≈ on time
11:30≈ on time ≈ on time
11:34≈ on time ≈ on time
11:36 / 11:37≈ on time ≈ on time
11:43 / 11:45≈ on time ≈ on time
11:48≈ on time ≈ on time
11:50 / 11:51≈ on time ≈ on time
11:54≈ on time ≈ on time
11:56≈ on time ≈ on time
11:58 / 11:59≈ on time ≈ on time
12:02≈ on time ≈ on time
12:04≈ on time ≈ on time
12:06 / 12:07≈ on time ≈ on time
12:09≈ on time ≈ on time
12:11on 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
Sat 21 NovCoppet 12:120 min—
Fri 20 NovCoppet 12:130 min—
Thu 19 NovCoppet 12:120 min—
Wed 18 NovCoppet 12:120 min—
Tue 17 NovCoppet 12:120 min—
Mon 16 NovCoppet 12:18+5 min+5 min
Sun 15 NovCoppet 12:130 min—
Sat 14 NovCoppet 12:120 min—
Fri 13 NovCoppet 12:120 min—
Thu 12 NovCoppet 12:120 min—
Wed 11 NovCoppet 12:120 min—
Tue 10 NovCoppet 12:120 min—
Mon 9 NovCoppet 12:130 min—
Sun 8 NovCoppet 12:120 min—
Sat 7 NovCoppet 12:120 min—
Fri 6 NovCoppet 12:120 min—
Thu 5 NovCoppet 12:120 min—
Wed 4 NovCoppet 12:120 min—
Tue 3 NovCoppet 12:120 min—
Mon 2 NovCoppet 12:120 min—
Sun 1 NovCoppet 12:120 min—
Sat 31 OctCoppet 12:130 min—
Fri 30 OctCoppet 12:120 min—
Thu 29 OctCoppet 12:120 min—
Wed 28 OctCoppet 12:120 min—
Tue 27 OctCoppet 12:120 min—
Mon 26 OctCoppet 12:120 min—
Sun 25 OctCoppet 12:120 min—
Sat 24 OctCoppet 12:120 min—
Fri 23 OctCoppet 12:120 min—