S31 16368 Münchenbuchsee – Belp

View line S31

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

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: Monday 18:33 from Münchenbuchsee · Mon 9 Nov

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

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

  • Early 0% · 0
  • On time 100% · 25
  • 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=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, 25 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
18:33on time on time
18:35 / 18:36≈ on time ≈ on time
18:39≈ on time ≈ on time
18:44 / 18:47≈ on time ≈ on time
18:51≈ on time ≈ on time
18:53≈ on time ≈ on time
18:56≈ on time ≈ on time
18:58≈ on time ≈ on time
19:00≈ on time ≈ on time
19:03≈ on time ≈ +1 min
19: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
Fri 6 NovBelp 19:040 min—
Thu 5 NovBelp 19:040 min—
Wed 4 NovBelp 19:07−1 min—
Tue 3 NovBelp 19:070 min—
Mon 2 NovBelp 19:080 min—
Fri 30 OctBelp 19:070 min—
Thu 29 OctBelp 19:08+1 min—
Wed 28 OctBelp 19:06−1 min—
Tue 27 OctBelp 19:080 min—
Mon 26 OctBelp 19:08+1 min—
Fri 23 OctBelp 19:070 min—
Thu 22 OctBelp 19:08+1 min+1 min
Wed 21 OctBelp 19:070 min—
Tue 20 OctBelp 19:06−1 min—
Mon 19 OctBelp 19:06−1 min—
Fri 16 OctWabern bei Bern 18:570 min—
Thu 15 OctWabern bei Bern 18:570 min—
Wed 14 OctWabern bei Bern 18:570 min—
Tue 13 OctWabern bei Bern 18:570 min—
Mon 12 OctWabern bei Bern 18:560 min—
Fri 9 OctWabern bei Bern 18:58+1 min—
Thu 8 OctWabern bei Bern 18:570 min—
Wed 7 OctWabern bei Bern 18:580 min—
Tue 6 OctWabern bei Bern 18:570 min—
Mon 5 OctWabern bei Bern 18:58+1 min—