S2 15226 Langnau i.E. – Laupen BE

View line S2

Langnau i.E. 07:07 → Laupen BE 08:20 Daily 1 h 13 min · 22 stops BLS

✓ Today’s run finished

Today it reached Laupen BE at 08:20 0 min

  1. Langnau i.E.07:07
  2. Zäziwil07:21
  3. Worb SBB07:33
  4. Bern07:48
  5. Niederwangen07:59
  6. Flamatt08:09
  7. Laupen BE08:20

Next service: tomorrow 07:07 from Langnau i.E. · Sat 21 Nov

Next departure 07:07 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
95%
55/58 runs under 3 min
RT coverage: 58 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 Laupen BE, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 22 Oct Max en route +17 min · last fix heading to Laupen BE +17 min
  • Mon 19 Oct Max en route +4 min · last fix heading to Laupen BE +4 min
  • Wed 14 Oct Max en route +4 min · last fix heading to Laupen BE +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 55
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=8
  • 89% W n=9
  • 89% T n=9
  • 100% F n=10
  • 100% S n=6
  • 100% S n=9

Stops and timetable

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

Last 90 days, 58 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
07:07on time on time
07:10≈ on time ≈ on time
07:14≈ on time ≈ on time
07:18≈ on time ≈ on time
07:21≈ on time ≈ on time
07:25 / 07:26≈ on time ≈ +1 min
07:29≈ on time ≈ +1 min
07:33≈ on time ≈ +1 min
07:37≈ on time ≈ +1 min
07:41≈ on time ≈ +1 min
07:43≈ on time ≈ +1 min
07:48 / 07:50≈ on time ≈ +1 min
07:54≈ on time ≈ +1 min
07:56≈ on time ≈ +1 min
07:59≈ on time ≈ +2 min
08:01≈ on time ≈ +2 min
08:03≈ on time ≈ +2 min
08:05≈ on time ≈ +2 min
08:09 / 08:10≈ on time ≈ +2 min
08:11≈ on time ≈ +2 min
08:14≈ on time ≈ +2 min
08:20on 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 20 NovLaupen BE 08:190 min—
Thu 19 NovLaupen BE 08:22+1 min—
Wed 18 NovLaupen BE 08:190 min—
Tue 17 NovLaupen BE 08:22+1 min—
Mon 16 NovLaupen BE 08:190 min—
Sun 15 NovLaupen BE 08:19−1 min—
Sat 14 NovLaupen BE 08:190 min—
Fri 13 NovLaupen BE 08:22+1 min—
Thu 12 NovLaupen BE 08:24+2 min+2 min
Wed 11 NovLaupen BE 08:22+1 min+1 min
Tue 10 NovLaupen BE 08:22+1 min+1 min
Mon 9 NovLaupen BE 08:190 min—
Sun 8 NovLaupen BE 08:200 min—
Sat 7 NovLaupen BE 08:190 min—
Fri 6 NovLaupen BE 08:190 min—
Thu 5 NovLaupen BE 08:190 min—
Wed 4 NovLaupen BE 08:190 min—
Tue 3 NovLaupen BE 08:22+1 min—
Mon 2 NovLaupen BE 08:190 min—
Sun 1 NovLaupen BE 08:210 min—
Sat 31 OctLaupen BE 08:200 min—
Fri 30 OctLaupen BE 08:210 min—
Thu 29 OctLaupen BE 08:210 min—
Wed 28 OctLaupen BE 08:23+2 min+2 min
Tue 27 OctLaupen BE 08:23+1 min+1 min
Mon 26 OctLaupen BE 08:220 min—
Sun 25 OctLaupen BE 08:210 min—
Sat 24 OctLaupen BE 08:210 min—
Fri 23 OctLaupen BE 08:210 min—
Thu 22 OctLaupen BE 08:38+17 min+17 min