S31 16360 Biel/Bienne – Belp

View line S31

Biel/Bienne 16:15 → Belp 17:06 Mon, Tue, Wed, Thu, Fri 0 h 51 min · 14 stops BLS

✓ Today’s run finished

Today it reached Belp at 17:08 +2 min

  1. Biel/Bienne16:15
  2. Schüpfen16:28
  3. Zollikofen16:35
  4. Bern Europaplatz16:51
  5. Wabern bei Bern16:56
  6. Kehrsatz17:00
  7. Belp17:06

Next service: tomorrow 16:15 from Biel/Bienne · Wed 18 Nov

Next departure 16:15 tomorrow · Biel/Bienne
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 1 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 2 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

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

  • Early 0% · 0
  • On time 100% · 30
  • 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=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 (14 stops).

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