R20 167 Lausanne-Flon – Bercher

View line R20

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

It has not run yet today

Last recorded run: Thursday 5 November +1 min

Next service: today 20:55 from Lausanne-Flon · Fri 6 Nov

Next departure 20:55 today · Lausanne-Flon
On-time · 30 days
76%
22/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
84%
41/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Tue 20 Oct Max en route +11 min · last fix heading to Bercher +11 min
  • Mon 7 Sept Max en route +8 min · last fix heading to Magliaso Paese +7 min
  • Wed 28 Oct Max en route +5 min · last fix heading to Bercher +5 min
  • Wed 21 Oct Max en route +5 min · last fix heading to Bercher +5 min
  • Wed 14 Oct Max en route +4 min · last fix heading to Bercher +4 min

Distribution · 90 days

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

  • Early 10% · 5
  • On time 73% · 36
  • 3–10 min 14% · 7
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 80% T n=5
  • 57% W n=7
  • 86% T n=7
  • 83% F n=6
  • 100% S n=9
  • 83% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (19 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
20:55on time +1 min
20:56≈ on time ≈ +1 min
20:59 / 21:00≈ on time ≈ +1 min
21:01≈ on time ≈ +1 min
21:02≈ on time ≈ +1 min
21:04≈ on time ≈ +1 min
21:06 / 21:07≈ on time ≈ +1 min
21:08≈ on time ≈ +2 min
21:10≈ on time ≈ +2 min
21:12≈ on time ≈ +2 min
21:14≈ on time ≈ +2 min
21:16≈ on time ≈ +2 min
21:18≈ on time ≈ +2 min
21:22 / 21:24≈ on time ≈ +3 min
21:25≈ on time ≈ +3 min
21:26≈ on time ≈ +3 min
21:29 / 21:30≈ on time ≈ +3 min
21:32 / 21:33≈ on time ≈ +3 min
21:37on time +4 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 5 NovBercher 21:38+1 min+1 min
Wed 4 NovBercher 21:37−1 min+3 min
Tue 3 NovBercher 21:37−1 min+2 min
Mon 2 NovBercher 21:37−1 min+2 min
Sun 1 NovBercher 21:38+1 min+1 min
Sat 31 OctBercher 21:380 min+2 min
Fri 30 OctBercher 21:380 min+7 min
Thu 29 OctBercher 21:37−1 min+1 min
Wed 28 OctBercher 21:38+5 min+5 min
Tue 27 OctBercher 21:380 min+8 min
Mon 26 OctBercher 21:37−1 min+4 min
Sun 25 OctBercher 21:36−1 min+3 min
Sat 24 OctBercher 21:39+1 min+9 min
Fri 23 OctBercher 21:380 min+5 min
Thu 22 OctBercher 21:38+2 min+2 min
Wed 21 OctBercher 21:38+5 min+5 min
Tue 20 OctBercher 21:38+11 min+11 min
Mon 19 OctBercher 21:37−1 min+4 min
Sun 18 OctBercher 21:39+4 min+4 min
Sat 17 OctBercher 21:38+2 min+2 min
Fri 16 OctBercher 21:38+3 min+7 min
Thu 15 OctBercher 21:38+1 min+2 min
Wed 14 OctBercher 21:39+4 min+4 min
Tue 13 OctBercher 21:40+2 min+5 min
Mon 12 OctBercher 21:39+1 min+2 min
Sun 11 OctBercher 21:380 min—
Sat 10 OctBercher 21:38+2 min+2 min
Fri 9 OctBercher 21:39+2 min+2 min
Thu 8 OctBercher 21:38+3 min+3 min
Wed 7 OctBercher 21:380 min—