S21 6731 Konolfingen – Thun

View line S21

Konolfingen 18:11 → Thun 18:32 Daily 0 h 21 min · 8 stops BLS

✓ Today’s run finished

Today it reached Thun at 18:33 +1 min

  1. Konolfingen18:11
  2. Stalden i.E.18:12
  3. Oberdiessbach18:16
  4. Heimberg18:23
  5. Lädeli18:25
  6. Steffisburg18:28
  7. Thun18:32

Next service: tomorrow 18:11 from Konolfingen · Sat 7 Nov

Next departure 18:11 tomorrow · Konolfingen
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 33 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
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

  • Fri 23 Oct Max en route +4 min · last fix heading to Thun +4 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Thun +3 min
  • Thu 15 Oct Max en route +3 min · last fix heading to Thun +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 30
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 100% W n=5
  • 80% T n=5
  • 80% F n=5
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 33 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
18:11+1 min +1 min
18:12≈ +1 min ≈ +1 min
18:16 / 18:17≈ +1 min ≈ +1 min
18:19≈ +1 min ≈ +1 min
18:23≈ +1 min ≈ +2 min
18:25≈ +1 min ≈ +2 min
18:28 / 18:29≈ +1 min ≈ +2 min
18:32+1 min +3 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 6 NovThun 18:34+1 min+1 min
Thu 5 NovThun 18:34+1 min—
Wed 4 NovThun 18:34+1 min+1 min
Tue 3 NovThun 18:34+1 min—
Mon 2 NovThun 18:34+1 min—
Sun 1 NovThun 18:34+1 min—
Sat 31 OctThun 18:36+3 min+3 min
Fri 30 OctThun 18:34+1 min+1 min
Thu 29 OctThun 18:34+1 min+1 min
Wed 28 OctThun 18:34+1 min—
Tue 27 OctThun 18:36+2 min+2 min
Mon 26 OctThun 18:340 min—
Sun 25 OctThun 18:34+1 min+1 min
Sat 24 OctThun 18:34+1 min+1 min
Fri 23 OctThun 18:37+4 min+4 min
Thu 22 OctThun 18:35+2 min+2 min
Wed 21 OctThun 18:33+1 min—
Tue 20 OctThun 18:32+1 min—
Mon 19 OctThun 18:34+1 min+1 min
Sun 18 OctThun 18:34+1 min—
Sat 17 OctThun 18:33+1 min+1 min
Fri 16 OctThun 18:33−1 min—
Thu 15 OctThun 18:35+3 min+3 min
Wed 14 OctThun 18:34+1 min+1 min
Tue 13 OctThun 18:34+1 min—
Sun 11 OctThun 18:34+1 min+1 min
Sat 10 OctThun 18:34+1 min—
Fri 9 OctThun 18:36+2 min+2 min
Thu 8 OctThun 18:35+2 min+2 min
Wed 7 OctThun 18:35+1 min+1 min