R20 239 Lausanne-Flon – Echallens

View line R20

Lausanne-Flon 14:10 → Echallens 14: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 14:37 −3 min

  1. Lausanne-Flon14:10
  2. Union-Prilly14:14
  3. Cery-Fleur-de-Lys14:17
  4. Vernand-Camarès14:23
  5. Cheseaux14:27
  6. Etagnières14:31
  7. Echallens14:37

Next service: tomorrow 14:10 from Lausanne-Flon · Fri 20 Nov

Next departure 14:10 tomorrow · Lausanne-Flon
On-time · 30 days
73%
22/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
77%
36/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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 27 Oct Max en route +6 min · last fix heading to Nyon +6 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Nyon +5 min
  • Tue 10 Nov Max en route +7 min · last fix heading to Nyon +4 min
  • Mon 2 Nov Max en route +4 min · last fix heading to Nyon +4 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Nyon +4 min

Distribution · 90 days

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

  • Early 17% · 8
  • On time 60% · 28
  • 3–10 min 23% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 57% M n=7
  • 71% T n=7
  • 57% W n=7
  • 86% T n=7
  • 67% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 47 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
14:102 min early 2 min early
14:11≈ 1 min early ≈ 1 min early
14:14 / 14:15≈ 1 min early ≈ 1 min early
14:16≈ 1 min early ≈ on time
14:17≈ 1 min early ≈ on time
14:19≈ on time ≈ on time
14:21 / 14:22≈ on time ≈ +1 min
14:23≈ on time ≈ +1 min
14:25≈ +1 min ≈ +1 min
14:27≈ +1 min ≈ +2 min
14:29≈ +1 min ≈ +2 min
14:31≈ +1 min ≈ +3 min
14:33≈ +2 min ≈ +3 min
14:37+2 min +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 19 NovEchallens 14:38−3 min—
Wed 18 NovNyon 17:590 min+3 min
Tue 17 NovNyon 18:02+3 min+3 min
Mon 16 NovNyon 18:02+3 min+3 min
Sun 15 NovGrindelwald 07:37−1 min—
Sat 14 NovEchallens 14:37−1 min—
Fri 13 NovNyon 18:02+2 min+3 min
Thu 12 NovNyon 18:03+5 min+5 min
Wed 11 NovNyon 18:03+4 min+4 min
Tue 10 NovNyon 18:03+4 min+7 min
Mon 9 NovNyon 17:59+2 min+2 min
Sun 8 NovGrindelwald 07:38−3 min—
Sat 7 NovEchallens 14:37−1 min—
Fri 6 NovNyon 18:02+3 min+3 min
Thu 5 NovNyon 17:59+3 min+3 min
Wed 4 NovNyon 18:02+2 min+3 min
Tue 3 NovNyon 17:59+2 min+2 min
Mon 2 NovNyon 18:03+4 min+4 min
Sun 1 NovGrindelwald 07:380 min—
Sat 31 OctEchallens 14:37−1 min—
Fri 30 OctNyon 18:01+2 min+3 min
Thu 29 OctNyon 18:01+2 min+3 min
Wed 28 OctNyon 18:01+2 min+3 min
Tue 27 OctNyon 18:05+6 min+6 min
Mon 26 OctNyon 18:02+3 min+6 min
Sun 25 OctGrindelwald 07:39+1 min+1 min
Sat 24 OctEchallens 14:37−1 min+3 min
Fri 23 OctEchallens 14:37−1 min+3 min
Thu 22 OctEchallens 14:38+2 min+2 min
Wed 21 OctEchallens 14:37−1 min+3 min