S31 16358 Münchenbuchsee – Belp

View line S31

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

✓ Today’s run finished

Today it reached Belp at 16:36 0 min

  1. Münchenbuchsee16:01
  2. Bern Wankdorf16:08
  3. Bern16:14
  4. Bern Weissenbühl16:23
  5. Kehrsatz Nord16:28
  6. Kehrsatz16:30
  7. Belp16:36

Next service: tomorrow 16:01 from Münchenbuchsee · Wed 18 Nov

Next departure 16:01 tomorrow · 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%
32/32 runs under 3 min
RT coverage: 32 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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

  • Early 0% · 0
  • On time 100% · 32
  • 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=7
  • 100% W n=6
  • 100% T n=6
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

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