R55 225 Genolier – Nyon
Alerts for train 225
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line R55.
✓ Today’s run finished
Today, last fix heading to Nyon at 13:29 No data
- Genolier13:14
- Givrins13:16
- Trélex13:20
- L'Asse13:22
- La Vuarpillière13:23
- Les Plantaz13:24
- Nyon13:28
Next service: tomorrow 13:14 from Genolier · Fri 20 Nov
Last 30 days
Arrival delay at Nyon, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 15 Sept Max en route +11 min · last fix heading to Agno +10 min
- Sat 24 Oct Max en route +7 min · last fix heading to Ponte Tresa +7 min
- Tue 3 Nov Max en route +7 min · last fix heading to Ponte Tresa +7 min
- Fri 9 Oct Max en route +4 min · last fix heading to Ponte Tresa +4 min
- Sun 25 Oct Max en route +4 min · last fix heading to Ponte Tresa +4 min
Distribution · 90 days
58 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 2% · 1
- On time 90% · 52
- 3–10 min 7% · 4
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 80% T n=10
- 100% W n=9
- 100% T n=8
- 83% F n=6
- 89% S n=9
- 88% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 58 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 13:14 | on time | on time | |
| 13:16 | ≈ on time | ≈ on time | |
| 13:20 | ≈ on time | ≈ +1 min | |
| 13:21 | ≈ on time | ≈ +1 min | |
| 13:22 | ≈ on time | ≈ +1 min | |
| 13:23 | ≈ on time | ≈ +2 min | |
| 13:24 | ≈ on time | ≈ +2 min | |
| 13:28 | on time | +3 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 19 Nov | Nyon 13:29 | No data | — |
| Wed 18 Nov | Ponte Tresa 23:04 | 0 min | +3 min |
| Tue 17 Nov | Ponte Tresa 23:04 | 0 min | +1 min |
| Mon 16 Nov | Ponte Tresa 23:04 | 0 min | +2 min |
| Sun 15 Nov | Ponte Tresa 23:04 | 0 min | — |
| Sat 14 Nov | Ponte Tresa 23:07 | 0 min | +1 min |
| Fri 13 Nov | Ponte Tresa 23:07 | +1 min | +3 min |
| Thu 12 Nov | Ponte Tresa 23:07 | +1 min | +3 min |
| Wed 11 Nov | Ponte Tresa 23:04 | 0 min | +2 min |
| Tue 10 Nov | Ponte Tresa 23:07 | 0 min | +3 min |
| Mon 9 Nov | Ponte Tresa 23:04 | 0 min | — |
| Sun 8 Nov | Ponte Tresa 23:04 | 0 min | +3 min |
| Sat 7 Nov | Ponte Tresa 23:04 | 0 min | +3 min |
| Fri 6 Nov | Ponte Tresa 23:07 | +2 min | +2 min |
| Thu 5 Nov | Ponte Tresa 23:04 | 0 min | +2 min |
| Wed 4 Nov | Ponte Tresa 23:04 | +1 min | +1 min |
| Tue 3 Nov | Ponte Tresa 23:04 | +7 min | +7 min |
| Mon 2 Nov | Ponte Tresa 23:07 | +1 min | +1 min |
| Sun 1 Nov | Ponte Tresa 23:04 | +1 min | +3 min |
| Sat 31 Oct | Ponte Tresa 23:07 | +2 min | +3 min |
| Fri 30 Oct | Ponte Tresa 23:06 | 0 min | +3 min |
| Thu 29 Oct | Ponte Tresa 23:08 | +2 min | +3 min |
| Wed 28 Oct | Ponte Tresa 23:06 | 0 min | +1 min |
| Tue 27 Oct | Ponte Tresa 23:06 | 0 min | +3 min |
| Mon 26 Oct | Ponte Tresa 23:08 | +1 min | +2 min |
| Sun 25 Oct | Ponte Tresa 23:06 | +4 min | +4 min |
| Sat 24 Oct | Ponte Tresa 23:13 | +7 min | +7 min |
| Fri 23 Oct | Ponte Tresa 23:06 | 0 min | +3 min |
| Thu 22 Oct | Ponte Tresa 23:06 | 0 min | +5 min |
| Wed 21 Oct | Ponte Tresa 23:06 | 0 min | +4 min |