R20 252 Echallens – Lausanne-Flon

View line R20

Echallens 17:52 → Lausanne-Flon 18:20 Mon, Tue, Wed, Thu, Fri, Sat 0 h 28 min · 14 stops Lausanne-Echallens-Bercher

It has not run yet today

Last recorded run: Thursday 12 November +1 min

Next service: today 17:52 from Echallens · Fri 13 Nov

Next departure 17:52 today · Echallens
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
54/54 runs under 3 min
RT coverage: 54 full · 0 partial · 2 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 Lausanne-Flon, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 11% · 6
  • On time 89% · 48
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=9
  • 100% W n=8
  • 100% T n=7
  • 100% F n=8
  • 100% S n=8
  • 100% S n=6

Stops and timetable

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

Last 90 days, 54 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
17:521 min early +1 min
17:55 / 17:56≈ 1 min early ≈ on time
17:57≈ 1 min early ≈ on time
18:00≈ 1 min early ≈ on time
18:01 / 18:02≈ 1 min early ≈ on time
18:03≈ 1 min early ≈ on time
18:05≈ 1 min early ≈ on time
18:06 / 18:07≈ 1 min early ≈ on time
18:09≈ on time ≈ on time
18:10≈ on time ≈ on time
18:12≈ on time ≈ on time
18:14≈ on time ≈ on time
18:17≈ on time ≈ on time
18:20on 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
Thu 12 NovLausanne-Flon 18:22+1 min+2 min
Wed 11 NovLausanne-Flon 18:190 min+1 min
Tue 10 NovLausanne-Flon 18:23+2 min+3 min
Mon 9 NovLausanne-Flon 18:180 min+1 min
Sun 8 NovInterlaken Ost 14:24−1 min—
Sat 7 NovLausanne-Flon 18:190 min—
Fri 6 NovLausanne-Flon 18:190 min—
Thu 5 NovLausanne-Flon 18:190 min—
Wed 4 NovLausanne-Flon 18:190 min+1 min
Tue 3 NovLausanne-Flon 18:190 min—
Mon 2 NovLausanne-Flon 18:190 min—
Sun 1 NovInterlaken Ost 14:24−1 min—
Sat 31 OctLausanne-Flon 18:190 min—
Fri 30 OctLausanne-Flon 18:22+1 min+1 min
Thu 29 OctLausanne-Flon 18:210 min—
Wed 28 OctLausanne-Flon 18:210 min+2 min
Tue 27 OctLausanne-Flon 18:22+1 min+11 min
Mon 26 OctLausanne-Flon 18:210 min—
Sun 25 OctInterlaken Ost 14:240 min—
Sat 24 OctLausanne-Flon 18:210 min—
Fri 23 OctLausanne-Flon 18:210 min—
Thu 22 OctLausanne-Flon 18:210 min+1 min
Wed 21 OctLausanne-Flon 18:210 min+2 min
Tue 20 OctLausanne-Flon 18:210 min—
Mon 19 OctLausanne-Flon 18:210 min+1 min
Sun 18 OctInterlaken Ost 14:24−1 min—
Sat 17 OctLausanne-Flon 18:210 min—
Fri 16 OctLausanne-Flon 18:220 min+1 min
Thu 15 OctLausanne-Flon 18:210 min—
Wed 14 OctLausanne-Flon 18:21+1 min+2 min