S1 15121 Fribourg/Freiburg – Thun

View line S1

Fribourg/Freiburg 06:12 → Thun 07:18 Daily 1 h 06 min · 20 stops BLS

Running now · updated 07:12

Position estimated from the timetable

Between Uttigen and Thun 0 min

Estimated arrival at Thun 07:18 · 52 km/h

  1. Fribourg/Freiburg06:12
  2. Schmitten FR06:22
  3. Thörishaus Dorf06:31
  4. Bern06:44
  5. Gümligen06:56
  6. Uttigen07:11
  7. Thun07:18

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

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
95%
52/55 runs under 3 min
RT coverage: 54 full · 1 partial · 0 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

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

Distribution · 90 days

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

  • Early 5% · 3
  • On time 89% · 49
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 75% T n=8
  • 100% W n=8
  • 100% T n=8
  • 100% F n=8
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 55 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
06:12on time on timePassed
06:14≈ on time ≈ on timePassed
06:17 / 06:18≈ on time ≈ on timePassed
06:22≈ on time ≈ +1 minPassed
06:25≈ on time ≈ +1 minPassed
06:28 / 06:29≈ on time ≈ +1 minPassed
06:31≈ on time ≈ +1 minPassed
06:35≈ on time ≈ +1 minPassed
06:37≈ on time ≈ +1 minPassed
06:39≈ on time ≈ +1 minPassed
06:44 / 06:47≈ on time ≈ +1 minPassed
06:50≈ on time ≈ +1 minPassed
06:53≈ on time ≈ +1 minPassed
06:56≈ on time ≈ +1 minPassed
07:00≈ on time ≈ +2 minPassed
07:03 / 07:04≈ on time ≈ +2 minPassed
07:06 / 07:07≈ on time ≈ +2 minPassed
07:09≈ on time ≈ +2 minPassed
07:11≈ on time ≈ +2 minPassed
07:18on time +2 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
Tue 17 NovUttigen 07:09Partial coverage0 min—
Mon 16 NovThun 07:19+2 min+2 min
Sun 15 NovThun 07:190 min—
Sat 14 NovThun 07:19−1 min—
Fri 13 NovThun 07:190 min—
Thu 12 NovThun 07:190 min—
Wed 11 NovThun 07:190 min—
Tue 10 NovThun 07:23+4 min+4 min
Mon 9 NovThun 07:22+2 min+2 min
Sun 8 NovThun 07:190 min—
Sat 7 NovThun 07:190 min—
Fri 6 NovThun 07:180 min—
Thu 5 NovThun 07:190 min—
Wed 4 NovThun 07:190 min—
Tue 3 NovThun 07:190 min—
Mon 2 NovThun 07:19+1 min—
Sun 1 NovThun 07:18−1 min—
Sat 31 OctThun 07:18−1 min—
Fri 30 OctThun 07:190 min—
Thu 29 OctThun 07:190 min—
Wed 28 OctThun 07:190 min—
Tue 27 OctThun 07:200 min—
Mon 26 OctThun 07:21+1 min—
Sun 25 OctThun 07:180 min—
Sat 24 OctThun 07:18−1 min—
Fri 23 OctThun 07:190 min—
Thu 22 OctThun 07:190 min—
Wed 21 OctThun 07:20+1 min—
Tue 20 OctThun 07:22+2 min+2 min
Mon 19 OctThun 07:20+1 min—