S31 16376 Münchenbuchsee → Belp

View line S31

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

S31 16376 Münchenbuchsee–Belp: final delay under 3 min on 21 of its 21 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 21:10 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: Monday 20:33 from Münchenbuchsee · Mon 23 Nov

Next departure 20:33 Monday · Münchenbuchsee
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 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: +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

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

  • Early 11% · 4
  • On time 89% · 31
  • 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=7
  • 100% T n=7
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 35 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
20:33on time on time
20:35 / 20:36≈ on time ≈ on time
20:39≈ on time ≈ on time
20:44 / 20:47≈ on time ≈ on time
20:51≈ on time ≈ on time
20:53≈ on time ≈ on time
20:56≈ on time ≈ on time
20:58≈ on time ≈ on time
21:00≈ on time ≈ on time
21:03≈ on time ≈ on time
21:06on 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 20 NovBelp 21:040 min—
Thu 19 NovBelp 21:07+1 min+1 min
Wed 18 NovBelp 21:040 min—
Tue 17 NovBelp 21:070 min—
Mon 16 NovBelp 21:070 min—
Fri 13 NovBelp 21:040 min—
Thu 12 NovBelp 21:08+1 min—
Wed 11 NovBelp 21:040 min—
Tue 10 NovBelp 21:04−1 min—
Mon 9 NovBelp 21:070 min—
Fri 6 NovBelp 21:08+2 min+2 min
Thu 5 NovBelp 21:040 min—
Wed 4 NovBelp 21:040 min—
Tue 3 NovBelp 21:070 min—
Mon 2 NovBelp 21:070 min—
Fri 30 OctBelp 21:06−1 min—
Thu 29 OctBelp 21:070 min—
Wed 28 OctBelp 21:070 min—
Tue 27 OctBelp 21:06−1 min—
Mon 26 OctBelp 21:07−1 min—
Fri 23 OctBelp 21:06−1 min—
Thu 22 OctBelp 21:06−1 min—
Wed 21 OctBelp 21:070 min—
Tue 20 OctBelp 21:070 min—
Mon 19 OctBelp 21:060 min—
Fri 16 OctBelp 21:07−1 min—
Thu 15 OctBelp 21:07+1 min—
Wed 14 OctBelp 21:080 min—
Tue 13 OctBelp 21:070 min—
Mon 12 OctBelp 21:070 min—