S1 15165 Fribourg/Freiburg → Thun

View line S1

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

S1 15165 Fribourg/Freiburg–Thun: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 18:25 (GMT+1).

✓ Today’s run finished

Today it reached Thun at 18:19 +1 min

  1. Fribourg/Freiburg17:12
  2. Schmitten FR17:22
  3. Thörishaus Dorf17:31
  4. Bern17:44
  5. Gümligen17:56
  6. Wichtrach18:06
  7. Thun18:18

Next service: tomorrow 17:12 from Fribourg/Freiburg · Mon 23 Nov

Next departure 17:12 tomorrow · Fribourg/Freiburg
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
54/56 runs under 3 min
RT coverage: 56 full · 0 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

  • Thu 12 Nov Max en route +5 min · last fix heading to Thun +5 min
  • Thu 24 Sept Max en route +4 min · last fix heading to Thun +4 min

Distribution · 90 days

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

  • Early 5% · 3
  • On time 91% · 51
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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