S4 15454 Langnau i.E. – Thun

View line S4

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

✓ Today’s run finished

Today it reached Thun at 16:22 +1 min

  1. Langnau i.E.14:40
  2. Lützelflüh-Goldbach14:55
  3. Burgdorf15:11
  4. Zollikofen15:31
  5. Belp15:54
  6. Burgistein16:07
  7. Thun16:21

Next service: tomorrow 14:40 from Langnau i.E. · Fri 13 Nov

Next departure 14:40 tomorrow · Langnau i.E.
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
46/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 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: +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 3 Nov Max en route +6 min · last fix heading to Thun +6 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 94% · 44
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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