S31 16318 Münchenbuchsee – Belp

View line S31

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

✓ Today’s run finished

Today it reached Belp at 06:37 +1 min

  1. Münchenbuchsee06:01
  2. Bern Wankdorf06:08
  3. Bern06:14
  4. Bern Weissenbühl06:23
  5. Kehrsatz Nord06:28
  6. Kehrsatz06:30
  7. Belp06:36

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

Next departure 06:01 tomorrow · Münchenbuchsee
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 31 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

Worst days

  • Mon 16 Nov Max en route +6 min · last fix heading to Belp +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 30
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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