S31 16371 Belp – Münchenbuchsee

View line S31

Belp 18:23 → Münchenbuchsee 18:57 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 11 stops BLS

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 18:23 from Belp · Mon 9 Nov

Next departure 18:23 Monday · Belp
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 1 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

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

  • Early 0% · 0
  • On time 100% · 24
  • 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=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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:23on time on time
18:24≈ on time ≈ on time
18:27≈ on time ≈ on time
18:29≈ on time ≈ on time
18:32≈ on time ≈ on time
18:34≈ on time ≈ on time
18:37≈ on time ≈ on time
18:44 / 18:46≈ on time ≈ on time
18:49≈ on time ≈ on time
18:53 / 18:54≈ on time ≈ on time
18:57on 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 18:58+1 min—
Thu 5 NovMünchenbuchsee 18:59+1 min+1 min
Wed 4 NovMünchenbuchsee 18:580 min—
Tue 3 NovMünchenbuchsee 18:580 min—
Mon 2 NovMünchenbuchsee 18:58−1 min—
Fri 30 OctMünchenbuchsee 18:580 min—
Thu 29 OctMünchenbuchsee 18:580 min—
Wed 28 OctMünchenbuchsee 18:580 min—
Tue 27 OctMünchenbuchsee 18:580 min—
Mon 26 OctMünchenbuchsee 18:580 min—
Fri 23 OctMünchenbuchsee 18:580 min—
Thu 22 OctMünchenbuchsee 18:580 min—
Wed 21 OctMünchenbuchsee 18:580 min—
Tue 20 OctMünchenbuchsee 18:580 min—
Mon 19 OctMünchenbuchsee 18:570 min—
Fri 16 OctMünchenbuchsee 18:580 min—
Thu 15 OctMünchenbuchsee 18:580 min—
Wed 14 OctMünchenbuchsee 18:570 min—
Tue 13 OctMünchenbuchsee 18:580 min—
Mon 12 OctMünchenbuchsee 18:570 min—
Fri 9 OctMünchenbuchsee 18:59No data—
Thu 8 OctMünchenbuchsee 18:570 min—
Wed 7 OctMünchenbuchsee 18:580 min—
Tue 6 OctMünchenbuchsee 18:580 min—
Mon 5 OctMünchenbuchsee 18:580 min—