S4 15489 Thun – Belp

View line S4

Thun 23:38 → Belp 00:05 Mon, Tue, Wed, Thu, Sun 0 h 27 min · 9 stops BLS

It has not run yet today

Last recorded run: Tuesday 10 November −1 min

Next service: today 23:38 from Thun · Wed 11 Nov

Next departure 23:38 today · Thun
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Tue 22 Sept Max en route +7 min · last fix heading to Hasle-Rüegsau +7 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 93% · 27
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 88% T n=8
  • 100% W n=4
  • 100% T n=4
  • — F n=0
  • — S n=0
  • 100% S n=5

Stops and timetable

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

Last 90 days, 29 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
23:38on time on time
23:42≈ on time ≈ on time
23:44≈ on time ≈ on time
23:48≈ on time ≈ on time
23:50≈ on time ≈ on time
23:54≈ on time ≈ +1 min
23:58≈ on time ≈ +1 min
00:01≈ 1 min early ≈ +1 min
00:051 min early +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
Tue 10 NovBelp 00:04−1 min—
Mon 9 NovBelp 00:05−1 min—
Sun 8 NovBelp 00:04−1 min—
Thu 5 NovBelp 00:07+1 min+1 min
Wed 4 NovBelp 00:04−1 min—
Tue 3 NovBelp 00:04−1 min—
Mon 2 NovBelp 00:04−1 min—
Sun 1 NovBelp 00:04−1 min—
Thu 29 OctBelp 00:05−1 min—
Wed 28 OctBelp 00:060 min—
Tue 27 OctBelp 00:05−1 min—
Mon 26 OctBelp 00:06−1 min—
Sun 25 OctBelp 00:060 min—
Thu 22 OctBelp 00:07+1 min+1 min
Wed 21 OctBelp 00:05−1 min—
Tue 20 OctBelp 00:060 min—
Mon 19 OctBelp 00:05−1 min—
Thu 15 OctBelp 00:05−1 min—
Wed 14 OctBelp 00:060 min—
Tue 13 OctBelp 00:070 min—
Mon 12 OctBelp 00:060 min—
Sun 11 OctBelp 00:05−1 min—
Tue 6 OctBelp 00:05−1 min—
Mon 5 OctBelp 00:060 min—
Sun 4 OctBelp 00:060 min—
Tue 22 SeptHasle-Rüegsau 01:19+7 min+7 min
Mon 21 SeptLützelflüh-Goldbach 01:19−1 min+2 min
Tue 15 SeptLützelflüh-Goldbach 01:04+1 min+2 min
Mon 17 AugLützelflüh-Goldbach 01:150 min—