S1 15179 Fribourg/Freiburg – Thun

View line S1

Fribourg/Freiburg 20:42 → Thun 21:46 Daily 1 h 04 min · 20 stops BLS

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 20:42 from Fribourg/Freiburg · Wed 18 Nov

Next departure 20:42 today · Fribourg/Freiburg
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
90%
45/50 runs under 3 min
RT coverage: 50 full · 0 partial · 0 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: +1 min

Last 30 days

Arrival delay at Thun, 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 +9 min · last fix heading to Thun +9 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Thun +5 min
  • Sat 7 Nov Max en route +5 min · last fix heading to Thun +5 min
  • Sun 25 Oct Max en route +4 min · last fix heading to Thun +4 min
  • Mon 12 Oct Max en route +4 min · last fix heading to Thun +4 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 84% · 42
  • 3–10 min 10% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 83% W n=6
  • 100% T n=7
  • 88% F n=8
  • 88% S n=8
  • 86% S n=7

Stops and timetable

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

Last 90 days, 50 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
20:42on time on time
20:44≈ on time ≈ on time
20:47 / 20:48≈ on time ≈ on time
20:52≈ on time ≈ on time
20:55≈ on time ≈ on time
20:58 / 20:59≈ on time ≈ +1 min
21:01≈ on time ≈ +1 min
21:05≈ on time ≈ +1 min
21:07≈ on time ≈ +1 min
21:09≈ on time ≈ +1 min
21:14 / 21:16≈ on time ≈ +1 min
21:19≈ on time ≈ +1 min
21:21 / 21:22≈ on time ≈ +1 min
21:25≈ on time ≈ +2 min
21:29≈ on time ≈ +2 min
21:32≈ +1 min ≈ +2 min
21:35≈ +1 min ≈ +2 min
21:38≈ +1 min ≈ +2 min
21:40≈ +1 min ≈ +2 min
21:46+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
Tue 17 NovThun 21:48+1 min—
Mon 16 NovThun 21:47+1 min—
Sun 15 NovThun 21:48+1 min+1 min
Sat 14 NovThun 21:470 min—
Fri 13 NovThun 21:470 min—
Thu 12 NovThun 21:48+1 min—
Wed 11 NovThun 21:48+1 min—
Tue 10 NovThun 21:48+1 min+1 min
Mon 9 NovThun 21:480 min—
Sun 8 NovThun 21:48+1 min—
Sat 7 NovThun 21:49+5 min+5 min
Fri 6 NovThun 21:45−1 min—
Thu 5 NovThun 21:44−1 min—
Wed 4 NovThun 21:48+1 min—
Tue 3 NovThun 21:48+1 min+1 min
Mon 2 NovThun 21:48+1 min+1 min
Sun 1 NovThun 21:49+1 min+1 min
Sat 31 OctThun 21:48+1 min+1 min
Fri 30 OctThun 21:470 min—
Thu 29 OctThun 21:48+1 min+1 min
Wed 28 OctThun 21:48+1 min+1 min
Tue 27 OctThun 21:47−1 min—
Mon 26 OctThun 21:480 min—
Sun 25 OctThun 21:51+4 min+4 min
Sat 24 OctThun 21:460 min—
Fri 23 OctThun 21:49+2 min+2 min
Thu 22 OctThun 21:470 min—
Wed 21 OctThun 21:48+1 min+1 min
Tue 20 OctThun 21:49+1 min+1 min
Mon 19 OctThun 21:48+1 min+1 min