S1 15147 Fribourg/Freiburg – Thun

View line S1

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

✓ Today’s run finished

Today it reached Thun at 13:57 +11 min

  1. Fribourg/Freiburg12:42
  2. Schmitten FR12:52
  3. Thörishaus Dorf13:01
  4. Bern13:14
  5. Gümligen13:25
  6. Wichtrach13:35
  7. Thun13:46

Next service: tomorrow 12:42 from Fribourg/Freiburg · Thu 19 Nov

Next departure 12:42 tomorrow · Fribourg/Freiburg
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
92%
36/39 runs under 3 min
RT coverage: 39 full · 0 partial · 11 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 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

  • Wed 18 Nov Max en route +11 min · last fix heading to Thun +11 min
  • Sun 13 Sept Max en route +5 min · last fix heading to Thun +5 min
  • Wed 23 Sept Max en route +3 min · last fix heading to Thun +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 90% · 35
  • 3–10 min 5% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=7
  • 75% W n=8
  • 100% T n=2
  • 100% F n=6
  • 100% S n=6
  • 88% S n=8

Stops and timetable

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

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