S2 15295 Laupen BE – Bern

View line S2

Laupen BE 00:10 → Bern 00:40 Daily 0 h 30 min · 11 stops BLS

✓ Today’s run finished

Today it reached Bern at 00:40 −1 min

  1. Laupen BE00:10
  2. Flamatt Dorf00:17
  3. Flamatt00:19
  4. Thörishaus Station00:25
  5. Niederwangen00:29
  6. Bern Bümpliz Süd00:32
  7. Bern00:40

Next service: tomorrow 00:10 from Laupen BE · Sun 8 Nov

Next departure 00:10 tomorrow · Laupen BE
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
94%
46/49 runs under 3 min
RT coverage: 49 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Bern, in minutes. One bar per run.

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

Worst days

  • Sun 13 Sept Max en route +4 min · last fix heading to Bern +4 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Bern +4 min
  • Thu 5 Nov Max en route +4 min · last fix heading to Bern +4 min

Distribution · 90 days

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

  • Early 31% · 15
  • On time 63% · 31
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 49 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
00:10on time on time
00:15≈ on time ≈ +1 min
00:17≈ on time ≈ +1 min
00:19 / 00:20≈ on time ≈ +1 min
00:23≈ on time ≈ +1 min
00:25≈ on time ≈ +1 min
00:27≈ on time ≈ +1 min
00:29≈ on time ≈ +1 min
00:32 / 00:33≈ on time ≈ +2 min
00:35≈ on time ≈ +2 min
00:40on 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
Sat 7 NovBern 00:39−1 min—
Fri 6 NovBern 00:42+1 min+1 min
Thu 5 NovBern 00:44+4 min+4 min
Wed 4 NovBern 00:44+4 min+4 min
Tue 3 NovBern 00:43+2 min+2 min
Mon 2 NovBern 00:39−2 min—
Sun 1 NovBern 00:40−1 min—
Sat 31 OctBern 00:39−2 min—
Fri 30 OctBern 00:410 min—
Thu 29 OctBern 00:40−2 min—
Wed 28 OctBern 00:40−1 min—
Tue 27 OctBern 00:410 min—
Mon 26 OctBern 00:43+2 min+2 min
Sun 25 OctBern 00:40−1 min—
Sat 24 OctBern 00:43+2 min+2 min
Fri 23 OctBern 00:41No data—
Thu 22 OctBern 00:39−1 min—
Wed 21 OctBern 00:40−1 min—
Tue 20 OctBern 00:42+2 min+2 min
Mon 19 OctBern 00:42+1 min—
Sun 18 OctBern 00:39−1 min—
Sat 17 OctBern 00:40−2 min—
Fri 16 OctBern 00:40−1 min—
Thu 15 OctBern 00:40−2 min—
Wed 14 OctBern 00:40−1 min—
Tue 13 OctBern 00:40−1 min—
Mon 12 OctBern 00:410 min—
Sun 11 OctBern 00:40−1 min—
Sat 10 OctBern 00:41−1 min—
Fri 9 OctBern 00:40−2 min—