S2 15274 Langnau i.E. – Laupen BE

View line S2

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

✓ Today’s run finished

Today it reached Laupen BE at 20:20 0 min

  1. Langnau i.E.19:07
  2. Zäziwil19:21
  3. Worb SBB19:33
  4. Bern19:48
  5. Niederwangen19:59
  6. Flamatt20:09
  7. Laupen BE20:20

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

Next departure 19:07 tomorrow · Langnau i.E.
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 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: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 39
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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