R20 247 Lausanne-Flon → Echallens

View line R20

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

R20 247 Lausanne-Flon–Echallens: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 17:50 (GMT+1).

✓ Today’s run finished

Today it reached Echallens at 16:37 0 min

  1. Lausanne-Flon16:10
  2. Union-Prilly16:14
  3. Cery-Fleur-de-Lys16:17
  4. Vernand-Camarès16:23
  5. Cheseaux16:27
  6. Etagnières16:31
  7. Echallens16:37

Next service: Monday 16:10 from Lausanne-Flon · Mon 23 Nov

Next departure 16:10 Monday · Lausanne-Flon
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
47/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Sun 4 Oct Max en route +7 min · last fix heading to Grindelwald +7 min
  • Sat 17 Oct Max en route +4 min · last fix heading to Echallens +4 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 92% · 45
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 86% S n=7
  • 86% S n=7

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
16:102 min early 2 min early
16:11≈ 1 min early ≈ 1 min early
16:14 / 16:15≈ 1 min early ≈ 1 min early
16:16≈ 1 min early ≈ 1 min early
16:17≈ 1 min early ≈ 1 min early
16:19≈ 1 min early ≈ on time
16:21 / 16:22≈ 1 min early ≈ on time
16:23≈ 1 min early ≈ on time
16:25≈ on time ≈ on time
16:27≈ on time ≈ +1 min
16:29≈ on time ≈ +1 min
16:31≈ on time ≈ +1 min
16:33≈ on time ≈ +1 min
16: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
Sat 21 NovEchallens 16:380 min—
Fri 20 NovEchallens 16:39+2 min+2 min
Thu 19 NovEchallens 16:39+1 min+1 min
Wed 18 NovEchallens 16:37−1 min—
Tue 17 NovEchallens 16:39+2 min+3 min
Mon 16 NovEchallens 16:39+2 min+2 min
Sun 15 NovGrindelwald 09:38−1 min—
Sat 14 NovEchallens 16:37−1 min+2 min
Fri 13 NovEchallens 16:38−1 min—
Thu 12 NovEchallens 16:38+1 min—
Wed 11 NovEchallens 16:380 min—
Tue 10 NovEchallens 16:38+1 min—
Mon 9 NovEchallens 16:370 min—
Sun 8 NovGrindelwald 09:39−2 min+1 min
Sat 7 NovEchallens 16:380 min—
Fri 6 NovEchallens 16:39+1 min—
Thu 5 NovEchallens 16:380 min+1 min
Wed 4 NovEchallens 16:39+1 min—
Tue 3 NovEchallens 16:380 min—
Mon 2 NovEchallens 16:39+1 min+1 min
Sun 1 NovGrindelwald 09:380 min—
Sat 31 OctEchallens 16:37−1 min—
Fri 30 OctEchallens 16:380 min+1 min
Thu 29 OctEchallens 16:38−1 min—
Wed 28 OctEchallens 16:39+1 min+1 min
Tue 27 OctEchallens 16:380 min+1 min
Mon 26 OctEchallens 16:390 min—
Sun 25 OctGrindelwald 09:40−1 min—
Sat 24 OctEchallens 16:380 min—
Fri 23 OctEchallens 16:38+1 min+1 min