S44 16432 Burgdorf → Thun

View line S44

Burgdorf 09:51 → Thun 10:51 Daily 1 h 00 min · 14 stops BLS

It has not run yet today

Last recorded run: Friday 20 November −1 min

Next service: today 09:51 from Burgdorf · Sat 21 Nov

Next departure 09:51 today · Burgdorf
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
98%
54/55 runs under 3 min
RT coverage: 55 full · 0 partial · 2 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: +2 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 23 Sept Max en route +5 min · last fix heading to Thun +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 54
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=10
  • 89% W n=9
  • 100% T n=5
  • 100% F n=9
  • 100% S n=6
  • 100% S n=8

Stops and timetable

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

Last 90 days, 55 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
09:51on time on time
09:53≈ on time ≈ on time
09:57≈ on time ≈ on time
10:05≈ on time ≈ on time
10:11 / 10:12≈ on time ≈ on time
10:24≈ on time ≈ +1 min
10:27≈ on time ≈ +1 min
10:30≈ on time ≈ +1 min
10:33≈ on time ≈ +1 min
10:37≈ on time ≈ +1 min
10:39≈ on time ≈ +1 min
10:43≈ on time ≈ +1 min
10:46≈ on time ≈ +1 min
10: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
Fri 20 NovThun 10:49−1 min—
Thu 19 NovThun 10:52No data—
Wed 18 NovThun 10:54+2 min+2 min
Tue 17 NovThun 10:520 min—
Mon 16 NovThun 10:49−1 min—
Sun 15 NovThun 10:520 min—
Sat 14 NovThun 10:54+2 min+2 min
Fri 13 NovThun 10:520 min—
Thu 12 NovThun 10:520 min—
Wed 11 NovThun 10:530 min—
Tue 10 NovThun 10:54+2 min+2 min
Mon 9 NovThun 10:52+1 min—
Sun 8 NovThun 10:52−1 min—
Sat 7 NovThun 10:520 min—
Fri 6 NovThun 10:520 min—
Thu 5 NovThun 10:520 min—
Wed 4 NovThun 10:520 min—
Tue 3 NovThun 10:520 min—
Mon 2 NovThun 10:520 min—
Sun 1 NovThun 10:51−1 min—
Sat 31 OctThun 10:51−1 min—
Fri 30 OctThun 10:520 min—
Thu 29 OctThun 10:52No data—
Wed 28 OctThun 10:520 min—
Tue 27 OctThun 10:520 min—
Mon 26 OctBurgdorf 11:010 min—
Sun 25 OctThun 10:53+1 min—
Sat 24 OctThun 10:510 min—
Fri 23 OctThun 10:53+2 min+2 min
Thu 22 OctThun 10:52−1 min—