S31 16374 Münchenbuchsee – Belp

View line S31

Münchenbuchsee 20:01 → Belp 20:36 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 11 stops BLS

✓ Today’s run finished

Today it reached Belp at 20:37 +1 min

  1. Münchenbuchsee20:01
  2. Bern Wankdorf20:08
  3. Bern20:14
  4. Bern Weissenbühl20:23
  5. Kehrsatz Nord20:28
  6. Kehrsatz20:30
  7. Belp20:36

Next service: Monday 20:01 from Münchenbuchsee · Mon 9 Nov

Next departure 20:01 Monday · Münchenbuchsee
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 26 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 Belp, 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

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

  • Early 12% · 3
  • On time 88% · 23
  • 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=5
  • 100% T n=5
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 26 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
20:01on time on time
20:03≈ on time ≈ on time
20:08 / 20:09≈ on time ≈ on time
20:14 / 20:17≈ on time ≈ on time
20:21≈ on time ≈ +1 min
20:23≈ on time ≈ +1 min
20:26≈ on time ≈ +1 min
20:28≈ on time ≈ +1 min
20:30≈ on time ≈ +1 min
20:33≈ on time ≈ +1 min
20:36on 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 NovBelp 20:38+1 min+1 min
Thu 5 NovBelp 20:34−1 min—
Wed 4 NovBelp 20:370 min—
Tue 3 NovBelp 20:39+1 min+1 min
Mon 2 NovBelp 20:340 min—
Fri 30 OctBelp 20:36−1 min—
Thu 29 OctBelp 20:370 min—
Wed 28 OctBelp 20:370 min—
Tue 27 OctBelp 20:38+1 min+1 min
Mon 26 OctBelp 20:38+1 min—
Fri 23 OctBelp 20:38+1 min+1 min
Thu 22 OctBelp 20:38+1 min—
Wed 21 OctBelp 20:35−1 min—
Tue 20 OctBelp 20:37−1 min—
Mon 19 OctBelp 20:360 min—
Fri 16 OctWabern bei Bern 20:29+1 min+1 min
Thu 15 OctWabern bei Bern 20:270 min—
Wed 14 OctWabern bei Bern 20:28+1 min—
Tue 13 OctWabern bei Bern 20:280 min—
Mon 12 OctWabern bei Bern 20:29+3 min+3 min
Fri 9 OctWabern bei Bern 20:28+1 min—
Thu 8 OctWabern bei Bern 20:29+1 min+1 min
Wed 7 OctWabern bei Bern 20:270 min—
Tue 6 OctWabern bei Bern 20:270 min—
Mon 5 OctWabern bei Bern 20:29+2 min+2 min
Mon 14 SeptWabern bei Bern 20:26−1 min—