S1 15187 Fribourg/Freiburg – Thun

View line S1

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

Running now · updated 23:28

Position estimated from the timetable

Between Gümligen and Rubigen No data

Estimated arrival at Thun 23:46 · 82 km/h

  1. Fribourg/Freiburg22:42
  2. Schmitten FR22:52
  3. Thörishaus Dorf23:01
  4. Bern23:14
  5. Gümligen23:25
  6. Rubigen23:29
  7. Thun23:46
On-time · 30 days
90%
27/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
95%
73/77 runs under 3 min
RT coverage: 76 full · 1 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Tue 6 Oct Max en route +19 min · last fix heading to Münsingen +19 min
  • Sun 8 Nov Max en route +6 min · last fix heading to Thun +6 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Thun +4 min
  • Thu 5 Nov Max en route +3 min · last fix heading to Thun +3 min

Distribution · 90 days

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

  • Early 8% · 6
  • On time 87% · 67
  • 3–10 min 4% · 3
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 92% T n=13
  • 100% W n=10
  • 91% T n=11
  • 100% F n=11
  • 90% S n=10
  • 92% S n=12

Stops and timetable

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

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