S60 211 Lugano FLP – Ponte Tresa

View line S60

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 19:39 from Lugano FLP · Mon 16 Nov

Next departure 19:39 today · Lugano FLP
On-time · 30 days
93%
25/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
92%
45/49 runs under 3 min
RT coverage: 49 full · 0 partial · 2 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

  • Thu 12 Nov Max en route +7 min · last fix heading to Ponte Tresa +7 min
  • Tue 6 Oct Max en route +6 min · last fix heading to Ponte Tresa +5 min
  • Mon 2 Nov Max en route +4 min · last fix heading to Ponte Tresa +4 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Ponte Tresa +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 45
  • 3–10 min 8% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 86% T n=7
  • 100% W n=8
  • 86% T n=7
  • 100% F n=7
  • 86% S n=7
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 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
19:39on time +1 min
19:41≈ on time ≈ +1 min
19:42≈ on time ≈ +1 min
19:45≈ on time ≈ +1 min
19:49≈ on time ≈ +1 min
19:51≈ on time ≈ +1 min
19:52≈ on time ≈ +1 min
19:55≈ on time ≈ +1 min
19:58≈ on time ≈ +2 min
20:00≈ on time ≈ +2 min
20:01≈ on time ≈ +2 min
20: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
Sun 15 NovPonte Tresa 20:040 min—
Sat 14 NovPonte Tresa 20:040 min—
Fri 13 NovPonte Tresa 20:08+1 min+2 min
Thu 12 NovPonte Tresa 20:13+7 min+7 min
Wed 11 NovPonte Tresa 20:040 min+2 min
Tue 10 NovPonte Tresa 20:07+1 min+4 min
Mon 9 NovPonte Tresa 20:08+2 min+2 min
Sun 8 NovPonte Tresa 20:04No data—
Sat 7 NovPonte Tresa 20:04+1 min+1 min
Fri 6 NovPonte Tresa 20:040 min+3 min
Thu 5 NovPonte Tresa 20:040 min+3 min
Wed 4 NovPonte Tresa 20:04+1 min+3 min
Tue 3 NovPonte Tresa 20:04+2 min+3 min
Mon 2 NovPonte Tresa 20:09+4 min+4 min
Sun 1 NovPonte Tresa 20:07+1 min—
Sat 31 OctPonte Tresa 20:060 min—
Fri 30 OctPonte Tresa 20:060 min+3 min
Thu 29 OctPonte Tresa 20:060 min+1 min
Wed 28 OctPonte Tresa 20:060 min+2 min
Tue 27 OctPonte Tresa 20:060 min—
Mon 26 OctPonte Tresa 20:060 min+2 min
Sun 25 OctPonte Tresa 20:06No data—
Sat 24 OctPonte Tresa 20:060 min—
Fri 23 OctPonte Tresa 20:060 min+2 min
Thu 22 OctPonte Tresa 20:060 min—
Wed 21 OctPonte Tresa 20:060 min—
Tue 20 OctPonte Tresa 20:060 min+2 min
Mon 19 OctPonte Tresa 20:060 min+2 min
Sun 18 OctPonte Tresa 20:07+1 min—
Sat 17 OctPonte Tresa 20:060 min—