S60 147 Lugano FLP – Ponte Tresa

View line S60

Lugano FLP 11:39 → Ponte Tresa 12:05 Daily 0 h 26 min · 12 stops Lugano-Ponte Tresa

✓ Today’s run finished

Today it reached Ponte Tresa at 12:05 0 min

  1. Lugano FLP11:39
  2. Sorengo Laghetto11:42
  3. Bioggio Molinazzo11:49
  4. Serocca11:52
  5. Agno11:55
  6. Magliaso12:00
  7. Ponte Tresa12:05

Next service: tomorrow 11:39 from Lugano FLP · Fri 13 Nov

Next departure 11:39 tomorrow · Lugano FLP
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
94%
79/84 runs under 3 min
RT coverage: 84 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Ponte Tresa, in minutes. One bar per run.

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

Worst days

  • Sat 12 Sept Max en route +7 min · last fix heading to Lauterbrunnen +7 min
  • Thu 17 Sept Max en route +7 min · last fix heading to La Chèvrerie-Monterêt +6 min
  • Sun 6 Sept Max en route +5 min · last fix heading to La Chèvrerie-Monterêt +5 min
  • Fri 30 Oct Max en route +5 min · last fix heading to Nyon +5 min
  • Fri 6 Nov Max en route +6 min · last fix heading to Nyon +4 min

Distribution · 90 days

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

  • Early 20% · 17
  • On time 74% · 62
  • 3–10 min 6% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=10
  • 100% W n=12
  • 92% T n=12
  • 83% F n=12
  • 92% S n=13
  • 92% S n=13

Stops and timetable

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

Last 90 days, 84 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:39on time +1 min
11:41≈ on time ≈ +1 min
11:42≈ on time ≈ +1 min
11:45≈ on time ≈ +1 min
11:49≈ on time ≈ +1 min
11:51≈ on time ≈ +1 min
11:52≈ on time ≈ +1 min
11:55≈ on time ≈ +2 min
11:58≈ on time ≈ +2 min
12:00≈ on time ≈ +2 min
12:01≈ on time ≈ +2 min
12:05on time +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
Thu 12 NovPonte Tresa 12:040 min—
Wed 11 NovNyon 22:420 min+3 min
Tue 10 NovNyon 22:45+2 min+2 min
Mon 9 NovNyon 22:40−1 min+2 min
Sun 8 NovNyon 22:42−1 min+2 min
Sat 7 NovNyon 22:420 min+2 min
Fri 6 NovNyon 22:44+4 min+6 min
Thu 5 NovNyon 22:42−1 min+3 min
Wed 4 NovNyon 22:39+1 min+4 min
Tue 3 NovNyon 22:42−1 min+3 min
Mon 2 NovNyon 22:390 min+3 min
Sun 1 NovNyon 22:44+2 min+3 min
Sat 31 OctNyon 22:42−1 min+2 min
Fri 30 OctNyon 22:48+5 min+5 min
Thu 29 OctNyon 22:44+1 min+2 min
Wed 28 OctNyon 22:430 min+4 min
Tue 27 OctNyon 22:42−2 min+12 min
Mon 26 OctNyon 22:44+1 min+5 min
Sun 25 OctBercher 16:380 min—
Sat 24 OctBercher 16:380 min—
Fri 23 OctMorges 17:07+3 min+5 min
Thu 22 OctMorges 17:05+1 min+1 min
Wed 21 OctMorges 17:05+1 min+2 min
Tue 20 OctMorges 17:04−2 min+3 min
Mon 19 OctMorges 17:04+1 min+2 min
Sun 18 OctBercher 16:380 min+1 min
Sat 17 OctBercher 16:380 min+4 min
Fri 16 OctMorges 17:05+2 min+3 min
Thu 15 OctMorges 17:03−2 min+2 min
Wed 14 OctMorges 17:03−2 min+2 min