S1 15163 Fribourg/Freiburg – Thun

View line S1

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

✓ Today’s run finished

Today it reached Thun at 17:46 0 min

  1. Fribourg/Freiburg16:42
  2. Schmitten FR16:52
  3. Thörishaus Dorf17:01
  4. Bern17:14
  5. Gümligen17:25
  6. Wichtrach17:35
  7. Thun17:46

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

Next departure 16:42 tomorrow · Fribourg/Freiburg
On-time · 30 days
73%
22/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
77%
36/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Mon 12 Oct Max en route +5 min · last fix heading to Thun +5 min
  • Fri 16 Oct Max en route +5 min · last fix heading to Thun +5 min
  • Tue 10 Nov Max en route +5 min · last fix heading to Thun +5 min
  • Tue 3 Nov Max en route +5 min · last fix heading to Thun +5 min
  • Thu 29 Oct Max en route +4 min · last fix heading to Thun +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 77% · 36
  • 3–10 min 23% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 67% T n=6
  • 71% W n=7
  • 57% T n=7
  • 50% 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, 47 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
16:42on time on time
16:44≈ on time ≈ on time
16:47 / 16:48≈ on time ≈ on time
16:52≈ on time ≈ +1 min
16:55≈ on time ≈ +1 min
16:58 / 16:59≈ on time ≈ +1 min
17:01≈ on time ≈ +1 min
17:05≈ on time ≈ +2 min
17:07≈ on time ≈ +2 min
17:09≈ +1 min ≈ +2 min
17:14 / 17:16≈ +1 min ≈ +2 min
17:19≈ +1 min ≈ +3 min
17:21 / 17:22≈ +1 min ≈ +3 min
17:25≈ +1 min ≈ +3 min
17:29≈ +1 min ≈ +3 min
17:32≈ +1 min ≈ +3 min
17:35≈ +1 min ≈ +3 min
17:38≈ +1 min ≈ +4 min
17:40≈ +1 min ≈ +4 min
17:46+1 min +4 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 11 NovThun 17:470 min—
Tue 10 NovThun 17:52+5 min+5 min
Mon 9 NovThun 17:470 min—
Sun 8 NovThun 17:470 min—
Sat 7 NovThun 17:44−1 min—
Fri 6 NovThun 17:470 min—
Thu 5 NovThun 17:48+1 min—
Wed 4 NovThun 17:48+1 min+1 min
Tue 3 NovThun 17:52+5 min+5 min
Mon 2 NovThun 17:49+2 min+2 min
Sun 1 NovThun 17:470 min—
Sat 31 OctThun 17:470 min—
Fri 30 OctThun 17:51+4 min+4 min
Thu 29 OctThun 17:51+4 min+4 min
Wed 28 OctThun 17:50+3 min+3 min
Tue 27 OctThun 17:48+1 min+1 min
Mon 26 OctThun 17:49+1 min+1 min
Sun 25 OctThun 17:470 min—
Sat 24 OctThun 17:470 min—
Fri 23 OctThun 17:50+3 min+3 min
Thu 22 OctThun 17:50+3 min+3 min
Wed 21 OctThun 17:50+3 min+3 min
Tue 20 OctThun 17:50+3 min+3 min
Mon 19 OctThun 17:48+2 min+2 min
Sun 18 OctThun 17:470 min—
Sat 17 OctThun 17:47+1 min—
Fri 16 OctThun 17:53+5 min+5 min
Thu 15 OctThun 17:49+2 min+2 min
Wed 14 OctThun 17:49+2 min+2 min
Tue 13 OctThun 17:49+2 min+2 min