S4 15434 Langnau i.E. – Thun

View line S4

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

✓ Today’s run finished

Today it reached Thun at 11:21 0 min

  1. Langnau i.E.09:40
  2. Lützelflüh-Goldbach09:55
  3. Burgdorf10:11
  4. Zollikofen10:31
  5. Belp10:54
  6. Burgistein11:07
  7. Thun11:21

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

Next departure 09:40 tomorrow · Langnau i.E.
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
98%
44/45 runs under 3 min
RT coverage: 45 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

  • Fri 28 Aug Max en route +6 min · last fix heading to Uetendorf Allmend +6 min

Distribution · 90 days

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

  • Early 9% · 4
  • On time 89% · 40
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 45 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
09:40on time on time
09:44≈ on time ≈ on time
09:46≈ on time ≈ on time
09:51 / 09:52≈ on time ≈ on time
09:55≈ on time ≈ on time
09:59 / 10:01≈ on time ≈ on time
10:04≈ on time ≈ on time
10:06≈ on time ≈ on time
10:11 / 10:17≈ on time ≈ on time
10:20≈ on time ≈ on time
10:23≈ on time ≈ on time
10:27≈ on time ≈ on time
10:31≈ on time ≈ on time
10:35≈ on time ≈ on time
10:41 / 10:42≈ on time ≈ on time
10:54≈ on time ≈ on time
10:57≈ on time ≈ on time
11:00≈ on time ≈ on time
11:03≈ on time ≈ on time
11:07≈ on time ≈ on time
11:09≈ on time ≈ on time
11:13≈ on time ≈ on time
11:16≈ on time ≈ on time
11:21on time on time

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 11:220 min—
Sun 8 NovThun 11:19−1 min—
Sat 7 NovThun 11:220 min—
Fri 6 NovThun 11:220 min—
Thu 5 NovThun 11:220 min—
Wed 4 NovThun 11:220 min—
Tue 3 NovThun 11:220 min—
Mon 2 NovThun 11:220 min—
Sun 1 NovThun 11:210 min—
Sat 31 OctThun 11:220 min—
Fri 30 OctThun 11:21−1 min—
Thu 29 OctThun 11:22No data—
Wed 28 OctThun 11:25+3 min+3 min
Tue 27 OctThun 11:220 min—
Mon 26 OctThun 11:230 min—
Sun 25 OctThun 11:22+1 min—
Sat 24 OctThun 11:220 min—
Fri 23 OctThun 11:21−1 min—
Thu 22 OctThun 11:220 min—
Wed 21 OctThun 11:21−1 min—
Tue 20 OctThun 11:230 min—
Mon 19 OctThun 11:220 min—
Sun 18 OctThun 11:220 min—
Sat 17 OctThun 11:220 min—
Fri 16 OctThun 11:21−1 min—
Thu 15 OctThun 11:220 min—
Wed 14 OctThun 11:21−1 min—
Tue 13 OctThun 11:230 min—
Mon 12 OctThun 11:220 min—
Sun 11 OctThun 11:220 min—