S1 15151 Fribourg/Freiburg – Thun

View line S1

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

Running now · updated 14:47

Position estimated from the timetable

Between Uttigen and Thun +1 min

Estimated arrival at Thun 14:47 · 11 km/h

  1. Fribourg/Freiburg13:42
  2. Schmitten FR13:52
  3. Thörishaus Dorf14:01
  4. Bern14:14
  5. Gümligen14:25
  6. Uttigen14:40
  7. Thun14:46

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 22 runs arrived on time.

On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 11 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 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 7 Oct Max en route +4 min · last fix heading to Thun +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 38
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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 10Today
13:42on time on timePassed
13:44≈ on time ≈ on timePassed
13:47 / 13:48≈ on time ≈ on timePassed
13:52≈ on time ≈ on timePassed
13:55≈ on time ≈ on timePassed
13:58 / 13:59≈ on time ≈ on timePassed
14:01≈ on time ≈ on timePassed
14:05≈ on time ≈ on timePassed
14:07≈ on time ≈ +1 minPassed
14:09≈ on time ≈ +1 minPassed
14:14 / 14:16≈ on time ≈ +1 minPassed
14:19≈ on time ≈ +1 minPassed
14:21 / 14:22≈ on time ≈ +1 minPassed
14:25≈ on time ≈ +1 minPassed
14:29≈ on time ≈ +1 minPassed
14:32≈ on time ≈ +1 minPassed
14:35≈ on time ≈ +1 minPassed
14:38≈ on time ≈ +1 minPassed
14:40≈ on time ≈ +1 minPassed
14:46on time +1 minNext

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 14:440 min—
Tue 17 NovThun 14:49+1 min+1 min
Mon 16 NovThun 14:47No data—
Sun 15 NovThun 14:48+1 min+1 min
Sat 14 NovThun 14:49+2 min+2 min
Fri 13 NovThun 14:470 min—
Thu 12 NovThun 14:48No data—
Wed 11 NovThun 14:470 min—
Tue 10 NovThun 14:48+1 min+2 min
Mon 9 NovThun 14:47No data—
Sun 8 NovThun 14:470 min—
Sat 7 NovThun 14:47+1 min—
Fri 6 NovThun 14:470 min—
Thu 5 NovThun 14:47No data—
Wed 4 NovThun 14:470 min—
Tue 3 NovThun 14:470 min—
Mon 2 NovThun 14:47No data—
Sun 1 NovThun 14:47+1 min—
Sat 31 OctThun 14:46−1 min—
Fri 30 OctThun 14:470 min+1 min
Thu 29 OctThun 14:47No data—
Wed 28 OctThun 14:48+1 min—
Tue 27 OctThun 14:480 min—
Mon 26 OctThun 14:47No data—
Sun 25 OctThun 14:47+1 min—
Sat 24 OctThun 14:470 min—
Fri 23 OctThun 14:470 min—
Thu 22 OctThun 14:47No data—
Wed 21 OctThun 14:470 min—
Tue 20 OctThun 14:480 min—