R20 177 Lausanne-Flon – Bercher

View line R20

Lausanne-Flon 23:25 → Bercher 00:07 Daily 0 h 42 min · 19 stops Lausanne-Echallens-Bercher

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 23:25 from Lausanne-Flon · Wed 11 Nov

Next departure 23:25 today · Lausanne-Flon
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
95%
62/65 runs under 3 min
RT coverage: 65 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Sat 5 Sept Max en route +5 min · last fix heading to Bercher +5 min
  • Fri 21 Aug Max en route +3 min · last fix heading to Ste-Croix +3 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Bercher +3 min

Distribution · 90 days

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

  • Early 28% · 18
  • On time 68% · 44
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 90% T n=10
  • 100% W n=9
  • 100% T n=7
  • 90% F n=10
  • 91% S n=11
  • 100% S n=9

Stops and timetable

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

Last 90 days, 65 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
23:25on time +1 min
23:26≈ on time ≈ +1 min
23:29 / 23:30≈ on time ≈ +1 min
23:31≈ on time ≈ +1 min
23:32≈ on time ≈ +1 min
23:34≈ on time ≈ +1 min
23:36 / 23:37≈ on time ≈ +1 min
23:38≈ on time ≈ +1 min
23:40≈ on time ≈ +1 min
23:42≈ on time ≈ +1 min
23:44≈ on time ≈ +1 min
23:46≈ on time ≈ +1 min
23:48≈ on time ≈ +1 min
23:52 / 23:54≈ on time ≈ +1 min
23:55≈ on time ≈ +1 min
23:56≈ on time ≈ +1 min
23:59 / 00:00≈ on time ≈ +1 min
00:02 / 00:03≈ on time ≈ +1 min
00:07on time +1 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
Tue 10 NovBercher 00:080 min+9 min
Mon 9 NovBercher 00:050 min+2 min
Sun 8 NovBercher 00:080 min+2 min
Sat 7 NovBercher 00:040 min+2 min
Fri 6 NovBercher 00:080 min+2 min
Thu 5 NovBercher 00:040 min+4 min
Wed 4 NovBercher 00:07−1 min+4 min
Tue 3 NovBercher 00:08−1 min+2 min
Mon 2 NovBercher 00:09+1 min+3 min
Sun 1 NovBercher 00:080 min+2 min
Sat 31 OctBercher 00:080 min+2 min
Fri 30 OctBercher 00:06−1 min+1 min
Thu 29 OctBercher 00:06−1 min+2 min
Wed 28 OctBercher 00:06−1 min+3 min
Tue 27 OctBercher 00:07−1 min+4 min
Mon 26 OctBercher 00:07−1 min+5 min
Sun 25 OctBercher 00:070 min+4 min
Sat 24 OctBercher 00:080 min+12 min
Fri 23 OctBercher 00:07−1 min+6 min
Thu 22 OctBercher 00:080 min+2 min
Wed 21 OctBercher 00:06−1 min+2 min
Tue 20 OctBercher 00:08+3 min+5 min
Mon 19 OctBercher 00:06−1 min+3 min
Sun 18 OctBercher 00:080 min+2 min
Sat 17 OctBercher 00:090 min+2 min
Fri 16 OctBercher 00:080 min+6 min
Thu 15 OctBercher 00:080 min+2 min
Wed 14 OctBercher 00:07−1 min+3 min
Tue 13 OctBercher 00:06−2 min+5 min
Mon 12 OctBercher 00:06−1 min+3 min