N1 742 Fribourg/Freiburg – Lausanne

View line N1

Fribourg/Freiburg 02:26 → Lausanne 03:16 Sat, Sun 0 h 50 min · 4 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Lausanne at 03:17 +1 min

  1. Fribourg/Freiburg02:26
  2. Romont FR02:43
  3. Palézieux02:58
  4. Lausanne03:16

Next service: tomorrow 02:26 from Fribourg/Freiburg · Sun 8 Nov

Next departure 02:26 tomorrow · Fribourg/Freiburg
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 12 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 17 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Lausanne, 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

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

  • Early 40% · 4
  • On time 60% · 6
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 10 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
02:26on time on time
02:43 / 02:44≈ on time ≈ on time
02:58 / 02:59≈ 1 min early ≈ +1 min
03:161 min early +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
Sat 7 NovLausanne 03:19+1 min+1 min
Sun 1 NovLausanne 03:16−1 min—
Sat 31 OctLausanne 03:16−1 min—
Sun 25 OctGrütschalp 11:10No data—
Sat 24 OctGrütschalp 11:10−2 min—
Fri 23 OctGrütschalp 11:10No data—
Thu 22 OctGrütschalp 11:10No data—
Wed 21 OctGrütschalp 11:10No data—
Tue 20 OctGrütschalp 11:11No data—
Mon 19 OctGrütschalp 11:10No data—
Sun 18 OctGrütschalp 11:11+1 min—
Sat 17 OctGrütschalp 11:10+1 min—
Fri 16 OctGrütschalp 11:11No data—
Thu 15 OctGrütschalp 11:10No data—
Wed 14 OctGrütschalp 11:10No data—
Tue 13 OctGrütschalp 11:11No data—
Mon 12 OctGrütschalp 11:10No data—
Sun 11 OctGrütschalp 11:10−2 min—
Sat 10 OctGrütschalp 11:11−1 min—
Fri 9 OctGrütschalp 11:10No data—
Thu 8 OctGrütschalp 11:10No data—
Wed 7 OctGrütschalp 11:10No data—
Tue 6 OctGrütschalp 11:10No data—
Mon 5 OctGrütschalp 11:11No data—
Sun 4 OctGrütschalp 11:10−1 min—
Sun 20 SeptLausanne 03:15−1 min—
Thu 17 SeptLausanne 03:15No data—