S2 15222 Langnau i.E. – Laupen BE

View line S2

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

✓ Today’s run finished

Today it reached Laupen BE at 07:20 0 min

  1. Langnau i.E.06:07
  2. Zäziwil06:21
  3. Worb SBB06:33
  4. Bern06:48
  5. Niederwangen06:59
  6. Flamatt07:09
  7. Laupen BE07:20

Next service: tomorrow 06:07 from Langnau i.E. · Wed 18 Nov

Next departure 06: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
96%
46/48 runs under 3 min
RT coverage: 48 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 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

  • Tue 13 Oct Max en route +4 min · last fix heading to Laupen BE +4 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Laupen BE +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 46
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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