S4 15450 Langnau i.E. – Thun

View line S4

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

Running now · updated 14:23

Position estimated from the timetable

Between Hindelbank and Schönbühl SBB 0 min

Estimated arrival at Thun 15:21 · 72 km/h

  1. Langnau i.E.13:40
  2. Lützelflüh-Goldbach13:55
  3. Burgdorf14:11
  4. Hindelbank14:23
  5. Schönbühl SBB14:27
  6. Zollikofen14:31
  7. Thun15:21

Today it is running no worse than usual: typical arrival delay is 0 min; 93% of the last 29 runs arrived on time.

On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 28 full · 1 partial · 1 no data
On-time · 90 days
96%
50/52 runs under 3 min
RT coverage: 51 full · 1 partial · 1 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

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

Distribution · 90 days

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

  • Early 6% · 3
  • On time 90% · 47
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 52 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 10Today
13:40on time on timePassed
13:44≈ on time ≈ on timePassed
13:46≈ on time ≈ on timePassed
13:51 / 13:52≈ on time ≈ on timePassed
13:55≈ on time ≈ on timePassed
13:59 / 14:01≈ on time ≈ on timePassed
14:04≈ on time ≈ +1 minPassed
14:06≈ on time ≈ +1 minPassed
14:11 / 14:17≈ on time ≈ +1 minPassed
14:20≈ on time ≈ +1 minPassed
14:23≈ on time ≈ +1 minPassed
14:27≈ on time ≈ +1 minNext
14:31≈ on time ≈ +1 min
14:35≈ on time ≈ +1 min
14:41 / 14:42≈ on time ≈ +1 min
14:54≈ on time ≈ +2 min
14:57≈ on time ≈ +2 min
15:00≈ on time ≈ +2 min
15:03≈ on time ≈ +2 min
15:07≈ on time ≈ +2 min
15:09≈ on time ≈ +2 min
15:13≈ on time ≈ +2 min
15:16≈ on time ≈ +2 min
15: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
Wed 18 NovLyssach 14:19Partial coverage0 min—
Tue 17 NovThun 15:24+2 min+2 min
Mon 16 NovThun 15:22No data—
Sun 15 NovThun 15:220 min—
Sat 14 NovThun 15:22+1 min—
Fri 13 NovThun 15:220 min—
Thu 12 NovThun 15:220 min—
Wed 11 NovThun 15:19−1 min—
Tue 10 NovThun 15:22+2 min+2 min
Mon 9 NovThun 15:220 min—
Sun 8 NovThun 15:220 min—
Sat 7 NovThun 15:19−1 min—
Fri 6 NovThun 15:19−1 min—
Thu 5 NovThun 15:24+3 min+3 min
Wed 4 NovThun 15:220 min—
Tue 3 NovThun 15:42+20 min+20 min
Mon 2 NovThun 15:24+2 min+2 min
Sun 1 NovThun 15:220 min—
Sat 31 OctThun 15:21−1 min—
Fri 30 OctThun 15:220 min—
Thu 29 OctThun 15:220 min—
Wed 28 OctThun 15:27+5 min+5 min
Tue 27 OctThun 15:22−1 min—
Mon 26 OctThun 15:22−1 min—
Sun 25 OctThun 15:24+2 min+2 min
Sat 24 OctThun 15:220 min—
Fri 23 OctThun 15:220 min—
Thu 22 OctThun 15:220 min—
Wed 21 OctThun 15:220 min—
Tue 20 OctThun 15:220 min—