S3 15358 Biel/Bienne – Belp

View line S3

Biel/Bienne 15:24 → Belp 16:21 Daily 0 h 57 min · 18 stops BLS

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

Next service: today 15:24 from Biel/Bienne · Thu 19 Nov

Next departure 15:24 today · Biel/Bienne
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
100%
46/46 runs under 3 min
RT coverage: 46 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

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

  • Early 7% · 3
  • On time 93% · 43
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 100% W n=6
  • 100% T n=6
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 46 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
15:24on time on time
15:27≈ on time ≈ on time
15:30≈ on time ≈ on time
15:32≈ on time ≈ on time
15:36 / 15:37≈ on time ≈ on time
15:40≈ on time ≈ on time
15:43≈ on time ≈ on time
15:48≈ on time ≈ on time
15:51≈ on time ≈ on time
15:55≈ on time ≈ +1 min
16:00 / 16:02≈ on time ≈ +1 min
16:06≈ on time ≈ +1 min
16:08≈ on time ≈ +1 min
16:11≈ on time ≈ +1 min
16:13≈ on time ≈ +1 min
16:15≈ on time ≈ +1 min
16:18≈ on time ≈ +1 min
16:21on time +1 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
Wed 18 NovBelp 16:22+1 min—
Tue 17 NovBelp 16:230 min—
Mon 16 NovBelp 16:190 min—
Sun 15 NovBelp 16:220 min—
Sat 14 NovBelp 16:220 min—
Fri 13 NovBelp 16:220 min—
Thu 12 NovBelp 16:220 min—
Wed 11 NovBelp 16:220 min—
Tue 10 NovBelp 16:220 min—
Mon 9 NovBelp 16:220 min—
Sun 8 NovBelp 16:22−1 min—
Sat 7 NovBelp 16:190 min—
Fri 6 NovBelp 16:190 min—
Thu 5 NovBelp 16:220 min—
Wed 4 NovBelp 16:22No data—
Tue 3 NovBelp 16:220 min—
Mon 2 NovBelp 16:230 min—
Sun 1 NovBelp 16:220 min—
Sat 31 OctBelp 16:220 min—
Fri 30 OctBelp 16:220 min—
Thu 29 OctBelp 16:21−1 min—
Wed 28 OctBelp 16:220 min—
Tue 27 OctBelp 16:220 min—
Mon 26 OctBelp 16:22−1 min—
Sun 25 OctBelp 16:23+1 min+1 min
Sat 24 OctBelp 16:23+1 min+1 min
Fri 23 OctBelp 16:23+1 min+1 min
Thu 22 OctBelp 16:220 min—
Wed 21 OctBelp 16:220 min—
Tue 20 OctBelp 16:21−1 min—