R20 255 Lausanne-Flon → Echallens

View line R20

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

R20 255 Lausanne-Flon–Echallens: final delay under 3 min on 28 of its 29 runs with data in the last 30 days (97%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 22:01 (GMT+1).

✓ Today’s run finished

Today it reached Echallens at 18:37 0 min

  1. Lausanne-Flon18:10
  2. Union-Prilly18:14
  3. Cery-Fleur-de-Lys18:17
  4. Vernand-Camarès18:23
  5. Cheseaux18:27
  6. Etagnières18:31
  7. Echallens18:37

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

Next departure 18:10 Monday · Lausanne-Flon
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 47 full · 0 partial · 2 no data
Typical delay
+1min
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

  • Fri 9 Oct Max en route +5 min · last fix heading to Echallens +5 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Echallens +3 min

Distribution · 90 days

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

  • Early 13% · 6
  • On time 83% · 39
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=7
  • 83% T n=6
  • 86% F n=7
  • 100% S n=7
  • 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
18:102 min early on time
18:11≈ 1 min early ≈ on time
18:14 / 18:15≈ 1 min early ≈ on time
18:16≈ 1 min early ≈ on time
18:17≈ 1 min early ≈ on time
18:19≈ 1 min early ≈ on time
18:21 / 18:22≈ 1 min early ≈ +1 min
18:23≈ on time ≈ +1 min
18:25≈ on time ≈ +1 min
18:27≈ on time ≈ +1 min
18:29≈ on time ≈ +1 min
18:31≈ on time ≈ +1 min
18:33≈ on time ≈ +1 min
18:37+1 min +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 18:370 min—
Fri 20 NovEchallens 18:39+1 min+2 min
Thu 19 NovEchallens 18:39+1 min—
Wed 18 NovEchallens 18:380 min—
Tue 17 NovEchallens 18:38−2 min—
Mon 16 NovEchallens 18:39+2 min+2 min
Sun 15 NovGrindelwald 11:39−2 min—
Sat 14 NovEchallens 18:38+1 min—
Fri 13 NovEchallens 18:39+1 min+2 min
Thu 12 NovEchallens 18:39+3 min+3 min
Wed 11 NovEchallens 18:39+1 min+1 min
Tue 10 NovEchallens 18:38+1 min+1 min
Mon 9 NovEchallens 18:39+2 min+2 min
Sun 8 NovGrindelwald 11:380 min—
Sat 7 NovEchallens 18:380 min+3 min
Fri 6 NovEchallens 18:380 min—
Thu 5 NovEchallens 18:380 min—
Wed 4 NovEchallens 18:39+1 min—
Tue 3 NovEchallens 18:38−1 min—
Mon 2 NovEchallens 18:39+2 min+2 min
Sun 1 NovGrindelwald 11:38−3 min—
Sat 31 OctEchallens 18:37+1 min+3 min
Fri 30 OctEchallens 18:39+1 min+2 min
Thu 29 OctEchallens 18:39+1 min—
Wed 28 OctEchallens 18:39+1 min—
Tue 27 OctEchallens 18:39+1 min+1 min
Mon 26 OctEchallens 18:38No data—
Sun 25 OctGrindelwald 11:43+2 min+2 min
Sat 24 OctEchallens 18:39+1 min+4 min
Fri 23 OctEchallens 18:40+2 min+2 min