S31 16330 Münchenbuchsee – Belp

View line S31

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

✓ Today’s run finished

Today it reached Belp at 09:38 +2 min

  1. Münchenbuchsee09:01
  2. Bern Wankdorf09:08
  3. Bern09:14
  4. Bern Weissenbühl09:23
  5. Kehrsatz Nord09:28
  6. Kehrsatz09:30
  7. Belp09:36

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

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

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 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, 24 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
09:01on time on time
09:03≈ on time ≈ on time
09:08 / 09:09≈ on time ≈ on time
09:14 / 09:17≈ on time ≈ on time
09:21≈ on time ≈ +1 min
09:23≈ on time ≈ +1 min
09:26≈ on time ≈ +1 min
09:28≈ on time ≈ +1 min
09:30≈ on time ≈ +1 min
09:33≈ on time ≈ +1 min
09: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 09:39+2 min+2 min
Thu 5 NovBelp 09:340 min—
Wed 4 NovBelp 09:370 min—
Tue 3 NovBelp 09:370 min—
Mon 2 NovBelp 09:340 min—
Fri 30 OctBelp 09:36−1 min—
Thu 29 OctBelp 09:37No data—
Wed 28 OctBelp 09:380 min—
Tue 27 OctBelp 09:37−1 min—
Mon 26 OctMünchenbuchsee 11:010 min+2 min
Fri 23 OctBelp 09:36−1 min—
Thu 22 OctBelp 09:37−1 min—
Wed 21 OctBelp 09:370 min—
Tue 20 OctBelp 09:380 min—
Mon 19 OctBelp 09:36−1 min—
Fri 16 OctWabern bei Bern 09:270 min—
Thu 15 OctWabern bei Bern 09:270 min—
Wed 14 OctWabern bei Bern 09:28+1 min+1 min
Tue 13 OctWabern bei Bern 09:29+1 min+1 min
Mon 12 OctWabern bei Bern 09:270 min—
Fri 9 OctWabern bei Bern 09:27+1 min—
Thu 8 OctWabern bei Bern 09:270 min—
Wed 7 OctWabern bei Bern 09:270 min—
Tue 6 OctWabern bei Bern 09:30+2 min+2 min
Mon 5 OctWabern bei Bern 09:280 min—