S31 16336 Münchenbuchsee – Belp

View line S31

Münchenbuchsee 10:33 → Belp 11:06 Mon, Tue, Wed, Thu, Fri 0 h 33 min · 11 stops BLS

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 10:33 from Münchenbuchsee · Wed 18 Nov

Next departure 10:33 today · Münchenbuchsee
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 33 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: 0 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
10:33on time on time
10:35 / 10:36≈ on time ≈ on time
10:39≈ on time ≈ on time
10:44 / 10:47≈ on time ≈ on time
10:51≈ on time ≈ on time
10:53≈ on time ≈ on time
10:56≈ on time ≈ on time
10:58≈ on time ≈ on time
11:00≈ on time ≈ on time
11:03≈ on time ≈ +1 min
11:06on 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 NovBelp 11:070 min—
Mon 16 NovBelp 11:070 min—
Fri 13 NovBelp 11:070 min—
Thu 12 NovBelp 11:07+1 min—
Wed 11 NovBelp 11:070 min—
Tue 10 NovBelp 11:070 min—
Mon 9 NovBelp 11:070 min—
Fri 6 NovBelp 11:070 min—
Thu 5 NovBelp 11:070 min—
Wed 4 NovBelp 11:070 min—
Tue 3 NovBelp 11:070 min—
Mon 2 NovBelp 11:070 min—
Fri 30 OctBelp 11:070 min—
Thu 29 OctBelp 11:07No data—
Wed 28 OctBelp 11:070 min—
Tue 27 OctBelp 11:070 min—
Mon 26 OctBelp 11:080 min—
Fri 23 OctBelp 11:070 min—
Thu 22 OctBelp 11:070 min—
Wed 21 OctBelp 11:070 min—
Tue 20 OctBelp 11:080 min—
Mon 19 OctBelp 11:070 min—
Fri 16 OctWabern bei Bern 10:570 min—
Thu 15 OctWabern bei Bern 10:570 min—
Wed 14 OctWabern bei Bern 10:56−1 min—
Tue 13 OctWabern bei Bern 10:59+2 min+2 min
Mon 12 OctWabern bei Bern 10:57+2 min+2 min
Fri 9 OctWabern bei Bern 10:56−1 min—
Thu 8 OctWabern bei Bern 10:58+1 min—
Wed 7 OctWabern bei Bern 10:560 min—