S3 15344 Biel/Bienne → Belp

View line S3

Biel/Bienne 11:54 → Belp 12:51 Daily 0 h 57 min · 18 stops BLS

S3 15344 Biel/Bienne–Belp: final delay under 3 min on 22 of its 22 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Belp: 12:51. TrainsRadar data as of 22 Nov 2026, 12:43 (GMT+1).

Running now · updated 12:43

Position estimated from the timetable

Between Kehrsatz Nord and Kehrsatz 0 min

Estimated arrival at Belp 12:51 · 65 km/h

  1. Biel/Bienne11:54
  2. Busswil BE12:02
  3. Schüpfen12:13
  4. Bern Wankdorf12:25
  5. Kehrsatz Nord12:43
  6. Kehrsatz12:45
  7. Belp12:51

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 22 runs arrived on time.

On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 8 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 38 full · 1 partial · 12 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

Worst days

  • Wed 21 Oct Max en route +3 min · last fix heading to Belp +3 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 92% · 36
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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 10Today
11:54on time on timePassed
11:57≈ on time ≈ on timePassed
12:00≈ on time ≈ on timePassed
12:02≈ on time ≈ on timePassed
12:06 / 12:07≈ on time ≈ on timePassed
12:10≈ on time ≈ on timePassed
12:13≈ on time ≈ on timePassed
12:18≈ on time ≈ on timePassed
12:21≈ on time ≈ on timePassed
12:25≈ on time ≈ +1 minPassed
12:30 / 12:32≈ on time ≈ +1 minPassed
12:36≈ on time ≈ +1 minPassed
12:38≈ on time ≈ +1 minPassed
12:41≈ on time ≈ +1 minPassed
12:43≈ on time ≈ +1 minPassed
12:45≈ on time ≈ +1 minNext
12:48≈ on time ≈ +1 min
12:51on 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
Sun 22 NovWabern bei Bern 12:39Partial coverage0 min—
Sat 21 NovBelp 12:520 min—
Fri 20 NovBelp 12:53+1 min—
Thu 19 NovBelp 12:49No data—
Wed 18 NovBelp 12:520 min—
Tue 17 NovBelp 12:530 min—
Mon 16 NovBelp 12:52No data—
Sun 15 NovBelp 12:520 min—
Sat 14 NovBelp 12:490 min—
Fri 13 NovBelp 12:520 min—
Thu 12 NovBelp 12:52No data—
Wed 11 NovBelp 12:520 min—
Tue 10 NovBelp 12:52−1 min—
Mon 9 NovBelp 12:52No data—
Sun 8 NovBelp 12:490 min—
Sat 7 NovBelp 12:490 min—
Fri 6 NovBelp 12:520 min—
Thu 5 NovBelp 12:52No data—
Wed 4 NovBelp 12:490 min—
Tue 3 NovBelp 12:520 min—
Mon 2 NovBelp 12:52No data—
Sun 1 NovBelp 12:53+1 min+1 min
Sat 31 OctBelp 12:51−1 min—
Fri 30 OctBelp 12:53+1 min+1 min
Thu 29 OctBelp 12:52No data—
Wed 28 OctBelp 12:520 min—
Tue 27 OctBelp 12:520 min—
Mon 26 OctBelp 12:52No data—
Sun 25 OctBelp 12:50−1 min—
Sat 24 OctBelp 12:53+1 min—