S31 16377 Belp – Münchenbuchsee

View line S31

Belp 19:53 → Münchenbuchsee 20:27 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 11 stops BLS

✓ Today’s run finished

Today it reached Münchenbuchsee at 20:27 0 min

  1. Belp19:53
  2. Kehrsatz19:57
  3. Kehrsatz Nord19:59
  4. Bern Weissenbühl20:04
  5. Bern20:14
  6. Bern Wankdorf20:19
  7. Münchenbuchsee20:27

Next service: Monday 19:53 from Belp · Mon 9 Nov

Next departure 19:53 Monday · Belp
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%
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
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Münchenbuchsee, 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
19:53on time on time
19:54≈ on time ≈ on time
19:57≈ on time ≈ on time
19:59≈ on time ≈ on time
20:02≈ on time ≈ on time
20:04≈ on time ≈ on time
20:07≈ on time ≈ on time
20:14 / 20:16≈ on time ≈ on time
20:19≈ on time ≈ on time
20:23 / 20:24≈ on time ≈ on time
20:27on time on time

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 NovMünchenbuchsee 20:280 min—
Thu 5 NovMünchenbuchsee 20:270 min—
Wed 4 NovMünchenbuchsee 20:280 min—
Tue 3 NovMünchenbuchsee 20:280 min—
Mon 2 NovMünchenbuchsee 20:280 min—
Fri 30 OctMünchenbuchsee 20:280 min—
Thu 29 OctMünchenbuchsee 20:280 min—
Wed 28 OctMünchenbuchsee 20:280 min—
Tue 27 OctMünchenbuchsee 20:28−1 min—
Mon 26 OctMünchenbuchsee 20:280 min—
Fri 23 OctMünchenbuchsee 20:29+1 min—
Thu 22 OctMünchenbuchsee 20:280 min—
Wed 21 OctMünchenbuchsee 20:270 min+25 min
Tue 20 OctMünchenbuchsee 20:280 min—
Mon 19 OctMünchenbuchsee 20:270 min—
Fri 16 OctMünchenbuchsee 20:280 min—
Thu 15 OctMünchenbuchsee 20:280 min—
Wed 14 OctMünchenbuchsee 20:290 min—
Tue 13 OctMünchenbuchsee 20:290 min—
Mon 12 OctMünchenbuchsee 20:280 min—
Fri 9 OctMünchenbuchsee 20:280 min—
Thu 8 OctMünchenbuchsee 20:280 min—
Wed 7 OctMünchenbuchsee 20:280 min—
Tue 6 OctMünchenbuchsee 20:280 min—
Mon 5 OctMünchenbuchsee 20:280 min—