R20 178 Bercher – Echallens

View line R20

Bercher 23:41 → Echallens 23:52 Daily 0 h 11 min · 6 stops Lausanne-Echallens-Bercher

✓ Today’s run finished

Today it reached Echallens at 23:53 +1 min

  1. Bercher23:41
  2. Fey23:43
  3. Sugnens23:47
  4. Grésaley23:49
  5. Sur Roche23:50
  6. Echallens23:52

Next service: tomorrow 23:41 from Bercher · Sat 7 Nov

Next departure 23:41 tomorrow · Bercher
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
68/70 runs under 3 min
RT coverage: 70 full · 0 partial · 3 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: +1 min

Last 30 days

Arrival delay at Echallens, 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 8 Sept Max en route +7 min · last fix heading to Cappella-Agnuzzo +7 min
  • Tue 18 Aug Max en route +5 min · last fix heading to Ste-Croix +3 min

Distribution · 90 days

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

  • Early 4% · 3
  • On time 93% · 65
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 82% T n=11
  • 100% W n=10
  • 100% T n=11
  • 100% F n=11
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 70 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:41on time +1 min
23:43 / 23:44≈ on time ≈ on time
23:47≈ on time ≈ on time
23:49≈ on time ≈ +1 min
23:50≈ on time ≈ +1 min
23:52on 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
Fri 6 NovEchallens 23:54+1 min+2 min
Thu 5 NovEchallens 23:53+1 min+1 min
Wed 4 NovYverdon-les-Bains 23:520 min+4 min
Tue 3 NovEchallens 23:54+1 min+29 min
Mon 2 NovEchallens 23:52−1 min+1 min
Sun 1 NovYverdon-les-Bains 00:090 min+1 min
Sat 31 OctYverdon-les-Bains 00:130 min+2 min
Fri 30 OctYverdon-les-Bains 23:540 min—
Thu 29 OctYverdon-les-Bains 23:540 min—
Wed 28 OctYverdon-les-Bains 23:540 min+1 min
Tue 27 OctYverdon-les-Bains 23:56+1 min+3 min
Mon 26 OctYverdon-les-Bains 23:520 min+4 min
Sun 25 OctYverdon-les-Bains 00:110 min+3 min
Sat 24 OctYverdon-les-Bains 00:130 min+1 min
Fri 23 OctEchallens 23:54+1 min+1 min
Thu 22 OctYverdon-les-Bains 23:540 min—
Wed 21 OctEchallens 23:530 min+2 min
Tue 20 OctEchallens 23:530 min+2 min
Mon 19 OctYverdon-les-Bains 23:540 min+2 min
Sun 18 OctYverdon-les-Bains 00:130 min—
Sat 17 OctYverdon-les-Bains 00:180 min+2 min
Fri 16 OctYverdon-les-Bains 23:540 min+5 min
Thu 15 OctEchallens 23:530 min+1 min
Wed 14 OctYverdon-les-Bains 23:540 min—
Tue 13 OctEchallens 23:55+1 min+2 min
Mon 12 OctEchallens 23:54+1 min+2 min
Sun 11 OctYverdon-les-Bains 00:130 min—
Sat 10 OctYverdon-les-Bains 00:130 min+1 min
Fri 9 OctEchallens 23:540 min+2 min
Thu 8 OctEchallens 23:530 min+1 min