R20 171 Lausanne-Flon – Bercher

View line R20

Lausanne-Flon 21:55 → Bercher 22:37 Daily 0 h 42 min · 19 stops Lausanne-Echallens-Bercher

It has not run yet today

Last recorded run: Saturday 7 November −1 min

Next service: today 21:55 from Lausanne-Flon · Sun 8 Nov

Next departure 21:55 today · Lausanne-Flon
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
91%
71/78 runs under 3 min
RT coverage: 78 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Bercher, in minutes. One bar per run.

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

Worst days

  • Sun 30 Aug Max en route +11 min · last fix heading to Zweilütschinen +11 min
  • Tue 11 Aug Max en route +11 min · last fix heading to Zweilütschinen +11 min
  • Sat 12 Sept Max en route +11 min · last fix heading to Agno +11 min
  • Tue 15 Sept Max en route +9 min · last fix heading to Magliaso Paese +7 min
  • Fri 23 Oct Max en route +6 min · last fix heading to Bercher +6 min

Distribution · 90 days

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

  • Early 12% · 9
  • On time 79% · 62
  • 3–10 min 5% · 4
  • 10–30 min 4% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 60% T n=10
  • 100% W n=11
  • 100% T n=10
  • 92% F n=12
  • 92% S n=12
  • 92% S n=12

Stops and timetable

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

Last 90 days, 78 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
21:55on time +1 min
21:56≈ on time ≈ +1 min
21:59 / 22:00≈ on time ≈ +1 min
22:01≈ on time ≈ +1 min
22:02≈ on time ≈ +1 min
22:04≈ on time ≈ +1 min
22:06 / 22:07≈ on time ≈ +1 min
22:08≈ on time ≈ +1 min
22:10≈ on time ≈ +1 min
22:12≈ on time ≈ +1 min
22:14≈ on time ≈ +1 min
22:16≈ on time ≈ +1 min
22:18≈ on time ≈ +1 min
22:22 / 22:24≈ on time ≈ +2 min
22:25≈ on time ≈ +2 min
22:26≈ on time ≈ +2 min
22:29 / 22:30≈ on time ≈ +2 min
22:32 / 22:33≈ on time ≈ +2 min
22:37on 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

DateLast stopFinalMax
Sat 7 NovBercher 22:37−1 min+1 min
Fri 6 NovBercher 22:37−1 min+2 min
Thu 5 NovBercher 22:38−1 min+2 min
Wed 4 NovBercher 22:370 min+4 min
Tue 3 NovBercher 22:380 min+1 min
Mon 2 NovBercher 22:390 min+2 min
Sun 1 NovBercher 22:380 min—
Sat 31 OctBercher 22:380 min+2 min
Fri 30 OctBercher 22:370 min+4 min
Thu 29 OctBercher 22:36−2 min+3 min
Wed 28 OctBercher 22:37−1 min+5 min
Tue 27 OctBercher 22:37−1 min+6 min
Mon 26 OctBercher 22:37−1 min+4 min
Sun 25 OctBercher 22:38+3 min+3 min
Sat 24 OctBercher 22:38+3 min+3 min
Fri 23 OctBercher 22:38+6 min+6 min
Thu 22 OctBercher 22:380 min+4 min
Wed 21 OctBercher 22:37−1 min+4 min
Tue 20 OctBercher 22:380 min+5 min
Mon 19 OctBercher 22:380 min+3 min
Sun 18 OctBercher 22:40+2 min+3 min
Sat 17 OctBercher 22:380 min+2 min
Fri 16 OctBercher 22:370 min+5 min
Thu 15 OctBercher 22:37−1 min+6 min
Wed 14 OctBercher 22:38−1 min+5 min
Tue 13 OctBercher 22:38+4 min+4 min
Mon 12 OctBercher 22:38+3 min+3 min
Sun 11 OctBercher 22:39+1 min+2 min
Sat 10 OctBercher 22:390 min+1 min
Fri 9 OctBercher 22:37−1 min+2 min