S21 6723 Konolfingen → Thun

View line S21

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

S21 6723 Konolfingen–Thun: final delay under 3 min on 22 of its 22 runs with data in the last 30 days (100%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 15:00 (GMT+1).

✓ Today’s run finished

Today it reached Thun at 14:33 +1 min

  1. Konolfingen14:11
  2. Stalden i.E.14:12
  3. Oberdiessbach14:16
  4. Heimberg14:23
  5. Lädeli14:25
  6. Steffisburg14:28
  7. Thun14:32

Next service: tomorrow 14:11 from Konolfingen · Mon 23 Nov

Next departure 14:11 tomorrow · Konolfingen
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 12 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Tue 20 Oct Max en route +5 min · last fix heading to Thun +5 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 95% · 36
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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
14:11+1 min +1 min
14:12≈ +1 min ≈ +1 min
14:16 / 14:17≈ +1 min ≈ +1 min
14:19≈ +1 min ≈ +1 min
14:23≈ +1 min ≈ +1 min
14:25≈ +1 min ≈ +1 min
14:28 / 14:29≈ +1 min ≈ +1 min
14:32+1 min +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
Sun 22 NovThun 14:34+1 min—
Sat 21 NovNeuchâtel Place Pury Littorail 15:270 min—
Fri 20 NovThun 14:33+1 min—
Thu 19 NovThun 14:33No data—
Wed 18 NovThun 14:33+1 min—
Tue 17 NovThun 14:34+1 min—
Mon 16 NovThun 14:33No data—
Sun 15 NovNeuchâtel Place Pury Littorail 15:270 min+1 min
Sat 14 NovNeuchâtel Place Pury Littorail 15:270 min+1 min
Fri 13 NovThun 14:34+2 min+2 min
Thu 12 NovThun 14:33No data—
Wed 11 NovThun 14:33+1 min—
Tue 10 NovThun 14:34+1 min—
Mon 9 NovThun 14:33No data—
Sun 8 NovNeuchâtel Place Pury Littorail 15:28+1 min—
Sat 7 NovNeuchâtel Place Pury Littorail 15:28+1 min+1 min
Fri 6 NovThun 14:34+1 min—
Thu 5 NovThun 14:33No data—
Wed 4 NovThun 14:34+1 min+1 min
Tue 3 NovThun 14:34+1 min—
Mon 2 NovThun 14:33No data—
Sun 1 NovNeuchâtel Place Pury Littorail 15:270 min—
Sat 31 OctNeuchâtel Place Pury Littorail 15:28+1 min—
Fri 30 OctThun 14:33+1 min—
Thu 29 OctThun 14:33No data—
Wed 28 OctThun 14:34+1 min—
Tue 27 OctThun 14:34+1 min—
Mon 26 OctThun 14:33No data—
Sun 25 OctNeuchâtel Place Pury Littorail 15:27+1 min—
Sat 24 OctNeuchâtel Place Pury Littorail 15:270 min+1 min