S44 16412 Bern – Thun

View line S44

Bern 05:02 → Thun 05:50 Daily 0 h 48 min · 16 stops BLS

✓ Today’s run finished

Today it reached Thun at 05:50 −1 min

  1. Bern05:02
  2. Wabern bei Bern05:10
  3. Kehrsatz05:15
  4. Toffen05:24
  5. Thurnen05:32
  6. Uetendorf05:42
  7. Thun05:50

Next service: tomorrow 05:02 from Bern · Sun 8 Nov

Next departure 05:02 tomorrow · Bern
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 47 full · 0 partial · 4 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 Thun, 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 12 Aug Max en route +11 min · last fix heading to Thurnen +4 min
  • Mon 2 Nov Max en route +4 min · last fix heading to Thun +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 45
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=7
  • 89% W n=9
  • 100% T n=5
  • 100% F n=6
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 47 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
05:02on time on time
05:05 / 05:06≈ on time ≈ on time
05:08≈ on time ≈ on time
05:10 / 05:11≈ on time ≈ on time
05:13≈ on time ≈ on time
05:15≈ on time ≈ on time
05:18≈ on time ≈ +1 min
05:20 / 05:21≈ on time ≈ +1 min
05:24 / 05:27≈ on time ≈ +1 min
05:29≈ on time ≈ +1 min
05:32≈ on time ≈ +1 min
05:36≈ on time ≈ +1 min
05:38≈ on time ≈ +1 min
05:42≈ on time ≈ +1 min
05:45≈ on time ≈ +1 min
05:50on 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
Sat 7 NovThun 05:49−1 min—
Fri 6 NovThun 05:49−1 min—
Thu 5 NovThun 05:490 min—
Wed 4 NovThun 05:49−1 min—
Tue 3 NovThun 05:49−1 min—
Mon 2 NovThun 05:54+4 min+4 min
Sun 1 NovThun 05:510 min—
Sat 31 OctThun 05:510 min—
Fri 30 OctThun 05:50−1 min—
Thu 29 OctThun 05:510 min—
Wed 28 OctThun 05:510 min—
Tue 27 OctThun 05:52+1 min—
Mon 26 OctThun 05:510 min—
Sun 25 OctThun 05:500 min—
Sat 24 OctThun 05:50−1 min—
Fri 23 OctThun 05:510 min—
Thu 22 OctThun 05:53+2 min+2 min
Wed 21 OctThun 05:510 min—
Tue 20 OctThun 05:510 min+1 min
Mon 19 OctThun 05:510 min—
Sun 18 OctThun 05:52+1 min—
Sat 17 OctThun 05:510 min—
Fri 16 OctThun 05:510 min—
Thu 15 OctThun 05:51−1 min—
Wed 14 OctThun 05:510 min—
Tue 13 OctThun 05:52+2 min+2 min
Mon 12 OctThun 05:510 min+2 min
Sun 11 OctThun 05:510 min—
Sat 10 OctThun 05:520 min—
Fri 9 OctThun 05:510 min—