S31 16348 Münchenbuchsee – Belp

View line S31

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:33 from Münchenbuchsee · Fri 6 Nov

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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=8
  • 100% W n=5
  • 100% T n=1
  • 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, 22 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
13:33on time on time
13:35 / 13:36≈ on time ≈ on time
13:39≈ on time ≈ on time
13:44 / 13:47≈ on time ≈ on time
13:51≈ on time ≈ on time
13:53≈ on time ≈ on time
13:56≈ on time ≈ +1 min
13:58≈ on time ≈ +1 min
14:00≈ on time ≈ +1 min
14:03≈ on time ≈ +1 min
14: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
Thu 5 NovBelp 14:07No data—
Wed 4 NovBelp 14:070 min—
Tue 3 NovBelp 14:070 min—
Mon 2 NovBelp 14:07No data—
Fri 30 OctBelp 14:070 min—
Thu 29 OctBelp 14:07No data—
Wed 28 OctBelp 14:070 min—
Tue 27 OctBelp 14:070 min—
Mon 26 OctBelp 14:07No data—
Fri 23 OctBelp 14:070 min—
Thu 22 OctBelp 14:07No data—
Wed 21 OctBelp 14:070 min—
Tue 20 OctBelp 14:070 min—
Mon 19 OctBelp 14:07No data—
Fri 16 OctWabern bei Bern 13:560 min—
Thu 15 OctWabern bei Bern 13:57No data—
Wed 14 OctWabern bei Bern 13:570 min—
Tue 13 OctWabern bei Bern 13:580 min—
Mon 12 OctWabern bei Bern 13:570 min—
Fri 9 OctWabern bei Bern 13:58+1 min—
Thu 8 OctWabern bei Bern 13:58+1 min—
Wed 7 OctWabern bei Bern 13:58+1 min+1 min
Tue 6 OctWabern bei Bern 13:570 min—
Mon 5 OctWabern bei Bern 13:580 min—
Tue 22 SeptBelp 21:050 min—
Tue 15 SeptWabern bei Bern 19:550 min+4 min
Fri 11 SeptWabern bei Bern 18:550 min+4 min
Mon 7 SeptBelp 21:05−1 min+1 min
Tue 1 SeptBelp 21:050 min+2 min