R20 217 Lausanne-Flon – Echallens

View line R20

Lausanne-Flon 09:10 → Echallens 09:37 Mon, Tue, Wed, Thu, Fri, Sat 0 h 27 min · 14 stops Lausanne-Echallens-Bercher

✓ Today’s run finished

Today it reached Echallens at 09:38 +1 min

  1. Lausanne-Flon09:10
  2. Union-Prilly09:14
  3. Cery-Fleur-de-Lys09:17
  4. Vernand-Camarès09:23
  5. Cheseaux09:27
  6. Etagnières09:31
  7. Echallens09:37

Next service: tomorrow 09:10 from Lausanne-Flon · Fri 6 Nov

Next departure 09:10 tomorrow · Lausanne-Flon
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
94%
46/49 runs under 3 min
RT coverage: 49 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 29 Oct Max en route +6 min · last fix heading to Ponte Tresa +5 min
  • Fri 16 Oct Max en route +5 min · last fix heading to Ponte Tresa +5 min
  • Tue 15 Sept Max en route +4 min · last fix heading to Muriaux +4 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 88% · 43
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 90% T n=10
  • 100% W n=7
  • 83% T n=6
  • 86% F n=7
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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