S1 15093 Gümligen – Thun

View line S1

Gümligen 00:06 → Thun 00:28 Mon, Tue, Wed, Thu, Sun 0 h 22 min · 7 stops BLS

It has not run yet today

Last recorded run: Friday 13 November −1 min

Next service: tomorrow 00:06 from Gümligen · Mon 16 Nov

Next departure 00:06 tomorrow · Gümligen
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 0 no data
On-time · 90 days
97%
36/37 runs under 3 min
RT coverage: 37 full · 0 partial · 0 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

  • Fri 16 Oct Max en route +8 min · last fix heading to Thun +8 min

Distribution · 90 days

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

  • Early 14% · 5
  • On time 84% · 31
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 100% W n=8
  • 100% T n=9
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 37 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
00:06on time on time
00:10≈ on time ≈ on time
00:14≈ on time ≈ +1 min
00:17≈ on time ≈ +1 min
00:19≈ on time ≈ +1 min
00:21≈ on time ≈ +1 min
00:28on time +1 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 NovThun 00:29−1 min—
Thu 12 NovThun 00:29+1 min—
Wed 11 NovThun 00:290 min—
Tue 10 NovThun 00:290 min—
Fri 6 NovThun 00:29+1 min—
Thu 5 NovThun 00:280 min—
Wed 4 NovThun 00:290 min—
Tue 3 NovThun 00:28−1 min—
Mon 2 NovThun 00:290 min+1 min
Fri 30 OctThun 00:290 min—
Thu 29 OctThun 00:30+1 min+1 min
Wed 28 OctThun 00:300 min—
Tue 27 OctThun 00:30+1 min—
Mon 26 OctThun 00:29+1 min—
Fri 23 OctThun 00:28−1 min—
Thu 22 OctThun 00:28−1 min—
Wed 21 OctThun 00:290 min—
Tue 20 OctThun 00:280 min—
Fri 16 OctThun 00:37+8 min+8 min
Thu 15 OctThun 00:30+1 min—
Wed 14 OctThun 00:30+1 min+1 min
Tue 13 OctThun 00:31+3 min+3 min
Mon 12 OctThun 00:280 min—
Fri 9 OctThun 00:300 min—
Thu 8 OctThun 00:30+1 min—
Wed 7 OctThun 00:30+1 min—
Tue 6 OctThun 00:28−1 min—
Mon 5 OctThun 00:290 min—
Thu 1 OctThun 00:280 min+10 min
Tue 29 SeptThun 00:27−1 min—