S4 15430 Langnau i.E. – Thun

View line S4

Langnau i.E. 08:40 → Thun 10:21 Daily 1 h 41 min · 24 stops BLS

✓ Today’s run finished

Today it reached Thun at 10:21 0 min

  1. Langnau i.E.08:40
  2. Lützelflüh-Goldbach08:55
  3. Burgdorf09:11
  4. Zollikofen09:31
  5. Belp09:54
  6. Burgistein10:07
  7. Thun10:21

Next service: tomorrow 08:40 from Langnau i.E. · Sat 7 Nov

Next departure 08:40 tomorrow · Langnau i.E.
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
37/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
+2min
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

Distribution · 90 days

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

  • Early 5% · 2
  • On time 95% · 35
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (24 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
08:40on time on time
08:44≈ on time ≈ on time
08:46≈ on time ≈ on time
08:51 / 08:52≈ on time ≈ on time
08:55≈ on time ≈ on time
08:59 / 09:01≈ on time ≈ on time
09:04≈ on time ≈ on time
09:06≈ on time ≈ on time
09:11 / 09:17≈ on time ≈ on time
09:20≈ on time ≈ +1 min
09:23≈ on time ≈ +1 min
09:27≈ on time ≈ +1 min
09:31≈ on time ≈ +1 min
09:35≈ on time ≈ +1 min
09:41 / 09:42≈ on time ≈ +1 min
09:54≈ on time ≈ +1 min
09:57≈ on time ≈ +1 min
10:00≈ on time ≈ +1 min
10:03≈ on time ≈ +1 min
10:07≈ on time ≈ +1 min
10:09≈ on time ≈ +1 min
10:13≈ on time ≈ +1 min
10:16≈ on time ≈ +1 min
10:21on 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
Fri 6 NovThun 10:230 min—
Thu 5 NovThun 10:19−1 min—
Wed 4 NovThun 10:19−1 min—
Tue 3 NovThun 10:24+2 min+2 min
Mon 2 NovThun 10:220 min—
Sun 1 NovThun 10:23+1 min—
Sat 31 OctThun 10:21−1 min—
Fri 30 OctThun 10:220 min—
Thu 29 OctThun 10:220 min—
Wed 28 OctThun 10:220 min—
Tue 27 OctThun 10:220 min—
Mon 26 OctLangnau i.E. 11:01−1 min—
Sun 25 OctThun 10:21−1 min—
Sat 24 OctThun 10:23+1 min—
Fri 23 OctThun 10:23+1 min+1 min
Thu 22 OctThun 10:23+1 min—
Wed 21 OctThun 10:21−1 min—
Tue 20 OctThun 10:25+2 min+2 min
Mon 19 OctThun 10:21−1 min—
Sun 18 OctThun 10:22−1 min—
Sat 17 OctThun 10:220 min—
Fri 16 OctThun 10:220 min—
Thu 15 OctThun 10:23+1 min+1 min
Wed 14 OctThun 10:220 min—
Tue 13 OctThun 10:24+1 min+1 min
Mon 12 OctThun 10:22+1 min—
Sun 11 OctThun 10:23+1 min—
Sat 10 OctThun 10:220 min—
Fri 9 OctThun 10:21−1 min—
Thu 8 OctThun 10:24+1 min+1 min