S60 161 Lugano FLP – Ponte Tresa

View line S60

Lugano FLP 13:24 → Ponte Tresa 13:50 Mon, Tue, Wed, Thu, Fri 0 h 26 min · 12 stops Lugano-Ponte Tresa

✓ Today’s run finished

Today it reached Ponte Tresa at 13:52 +2 min

  1. Lugano FLP13:24
  2. Sorengo Laghetto13:27
  3. Bioggio Molinazzo13:34
  4. Serocca13:37
  5. Agno13:40
  6. Magliaso13:45
  7. Ponte Tresa13:50

Next service: Monday 13:24 from Lugano FLP · Mon 9 Nov

Next departure 13:24 Monday · Lugano FLP
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
44/45 runs under 3 min
RT coverage: 45 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: 0 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

  • Tue 6 Oct Max en route +8 min · last fix heading to Morges +4 min

Distribution · 90 days

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

  • Early 40% · 18
  • On time 58% · 26
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 45 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
13:24on time +1 min
13:26≈ on time ≈ on time
13:27≈ on time ≈ on time
13:30≈ on time ≈ +1 min
13:34≈ on time ≈ +1 min
13:36≈ on time ≈ +1 min
13:37≈ on time ≈ +1 min
13:40≈ on time ≈ +1 min
13:43≈ on time ≈ +1 min
13:45≈ on time ≈ +1 min
13:46≈ on time ≈ +2 min
13:501 min early +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 6 NovPonte Tresa 13:53+2 min+2 min
Thu 5 NovMorges 20:33−1 min+3 min
Wed 4 NovMorges 20:34−1 min+3 min
Tue 3 NovMorges 20:340 min+3 min
Mon 2 NovMorges 20:34−1 min+3 min
Sun 1 NovMorges 20:34−1 min+2 min
Sat 31 OctMorges 20:34−1 min+3 min
Fri 30 OctMorges 20:350 min+2 min
Thu 29 OctMorges 20:33−2 min+2 min
Wed 28 OctMorges 20:33−2 min+2 min
Tue 27 OctMorges 20:33−1 min+11 min
Mon 26 OctMorges 20:34−2 min+3 min
Sun 25 OctBercher 20:06−1 min+1 min
Sat 24 OctBercher 20:080 min—
Fri 23 OctMorges 20:34−1 min+3 min
Thu 22 OctMorges 20:33−3 min+5 min
Wed 21 OctMorges 20:33−2 min+9 min
Tue 20 OctMorges 20:33−2 min+4 min
Mon 19 OctMorges 20:33−2 min+21 min
Sun 18 OctMorges 20:33−2 min+3 min
Sat 17 OctMorges 20:350 min+2 min
Fri 16 OctMorges 20:350 min+4 min
Thu 15 OctMorges 20:32−2 min+3 min
Wed 14 OctMorges 20:350 min+6 min
Tue 13 OctMorges 20:36+1 min+2 min
Mon 12 OctMorges 20:32−3 min+2 min
Sun 11 OctMorges 20:37+2 min+7 min
Sat 10 OctMorges 20:34−1 min+4 min
Fri 9 OctMorges 20:34−2 min+2 min
Thu 8 OctMorges 20:34−1 min+2 min