R55 302 Nyon – St-Cergue

View line R55

Nyon 05:47 → St-Cergue 06:23 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 15 stops NStCM

✓ Today’s run finished

Today it reached St-Cergue at 06:24 +1 min

  1. Nyon05:47
  2. La Vuarpillière05:49
  3. Trélex05:55
  4. Genolier06:01
  5. Genolier clinique/campus06:05
  6. Arzier06:13
  7. St-Cergue06:23

Next service: Monday 05:47 from Nyon · Mon 16 Nov

Next departure 05:47 Monday · Nyon
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
49/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at St-Cergue, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 2% · 1
  • On time 98% · 48
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=8
  • 100% F n=9
  • 100% S n=5
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (15 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
05:47on time +2 min
05:48≈ on time ≈ +2 min
05:49≈ on time ≈ +2 min
05:50≈ on time ≈ +2 min
05:53≈ on time ≈ +2 min
05:55≈ on time ≈ +2 min
05:58≈ on time ≈ +2 min
06:01≈ on time ≈ +2 min
06:02≈ on time ≈ +2 min
06:05≈ on time ≈ +2 min
06:08≈ +1 min ≈ +2 min
06:09≈ +1 min ≈ +2 min
06:13 / 06:15≈ +1 min ≈ +2 min
06:19≈ +1 min ≈ +2 min
06:23+1 min +2 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
Fri 13 NovSt-Cergue 06:24+1 min+6 min
Thu 12 NovSt-Cergue 06:24+1 min—
Wed 11 NovSt-Cergue 06:24+1 min+5 min
Tue 10 NovSt-Cergue 06:24+2 min+2 min
Mon 9 NovSt-Cergue 06:24+1 min+5 min
Sun 8 NovCamedo 06:180 min—
Sat 7 NovCamedo 06:180 min—
Fri 6 NovSt-Cergue 06:24+1 min+3 min
Thu 5 NovSt-Cergue 06:24+1 min+3 min
Wed 4 NovSt-Cergue 06:24+2 min+4 min
Tue 3 NovSt-Cergue 06:24+1 min+5 min
Mon 2 NovSt-Cergue 06:23−1 min+3 min
Sun 1 NovCamedo 06:19+1 min+1 min
Sat 31 OctCamedo 06:19+1 min+2 min
Fri 30 OctSt-Cergue 06:25+1 min+8 min
Thu 29 OctSt-Cergue 06:25+1 min+4 min
Wed 28 OctSt-Cergue 06:25+1 min+3 min
Tue 27 OctSt-Cergue 06:25+1 min+3 min
Mon 26 OctSt-Cergue 06:25+2 min+5 min
Sun 25 OctCamedo 06:19+1 min+2 min
Sat 24 OctCamedo 06:20+2 min+3 min
Fri 23 OctCamedo 06:20+2 min+5 min
Thu 22 OctCamedo 06:180 min+5 min
Wed 21 OctCamedo 06:190 min+5 min
Tue 20 OctCamedo 06:20+2 min+2 min
Mon 19 OctCamedo 06:19+1 min+2 min
Sun 18 OctCamedo 06:19+1 min—
Sat 17 OctCamedo 06:19+1 min+2 min
Fri 16 OctCamedo 06:17−1 min—
Thu 15 OctCamedo 06:180 min+2 min