S4 15446 Langnau i.E. – Thun

View line S4

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

✓ Today’s run finished

Today, last fix heading to Thun at 14:22 No data

  1. Langnau i.E.12:40
  2. Lützelflüh-Goldbach12:55
  3. Burgdorf13:11
  4. Zollikofen13:31
  5. Belp13:54
  6. Burgistein14:07
  7. Thun14:21

Next service: tomorrow 12:40 from Langnau i.E. · Tue 10 Nov

Next departure 12:40 tomorrow · Langnau i.E.
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 31 full · 0 partial · 9 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: 0 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

  • Sun 1 Nov Max en route +4 min · last fix heading to Thun +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=1
  • 100% T n=6
  • 100% W n=6
  • 100% T n=2
  • 100% F n=5
  • 100% S n=5
  • 83% S n=6

Stops and timetable

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

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