S44 16486 Belp – Thun

View line S44

Belp 23:24 → Thun 23:51 Mon, Tue, Wed, Thu, Sun 0 h 27 min · 9 stops BLS

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 23:24 from Belp · Mon 9 Nov

Next departure 23:24 today · Belp
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 1 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: 0 min

Last 30 days

Arrival delay at Thun, 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=6
  • 100% T n=6
  • 100% W n=7
  • 100% T n=5
  • — F n=0
  • — S n=0
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
23:24on time on time
23:27≈ on time ≈ on time
23:30≈ on time ≈ on time
23:33≈ on time ≈ on time
23:37≈ on time ≈ on time
23:39≈ on time ≈ on time
23:43≈ on time ≈ on time
23:46≈ on time ≈ on time
23:51on 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
Sun 8 NovThun 23:530 min—
Thu 5 NovThun 23:510 min—
Wed 4 NovThun 23:49−1 min—
Tue 3 NovThun 23:49−1 min—
Mon 2 NovThun 23:49−1 min—
Sun 1 NovThun 23:52−1 min—
Thu 29 OctThun 23:520 min—
Wed 28 OctThun 23:54+1 min+2 min
Tue 27 OctThun 23:52−1 min—
Mon 26 OctThun 23:530 min—
Sun 25 OctThun 23:510 min—
Thu 22 OctThun 23:53+1 min+1 min
Wed 21 OctThun 23:520 min—
Tue 20 OctThun 23:51−1 min—
Mon 19 OctThun 23:510 min—
Thu 15 OctThun 23:51−1 min—
Wed 14 OctThun 23:52−1 min—
Tue 13 OctThun 23:520 min—
Mon 12 OctThun 23:51−1 min—
Sun 11 OctThun 23:520 min—
Tue 6 OctThun 23:520 min—
Mon 5 OctThun 23:52−1 min—
Sun 4 OctThun 23:51−1 min—
Thu 1 OctThun 23:51No data—
Wed 30 SeptThun 23:50−1 min+2 min
Sun 6 SeptBern 23:10−1 min+1 min
Wed 2 SeptSumiswald-Grünen 22:370 min+2 min
Mon 31 AugSumiswald-Grünen 22:37+1 min+4 min
Thu 27 AugBern 23:100 min—
Wed 26 AugBern 23:10−1 min—