S44 16440 Burgdorf – Thun

View line S44

Burgdorf 11:51 → Thun 12:51 Daily 1 h 00 min · 14 stops BLS

✓ Today’s run finished

Today it reached Thun at 12:51 −1 min

  1. Burgdorf11:51
  2. Hindelbank11:57
  3. Bern12:11
  4. Kaufdorf12:30
  5. Burgistein12:37
  6. Uetendorf12:43
  7. Thun12:51

Next service: tomorrow 11:51 from Burgdorf · Sat 21 Nov

Next departure 11:51 tomorrow · Burgdorf
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
96%
46/48 runs under 3 min
RT coverage: 48 full · 0 partial · 10 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

  • Fri 16 Oct Max en route +4 min · last fix heading to Thun +4 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Thun +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=8
  • 100% W n=10
  • 100% T n=3
  • 88% F n=8
  • 100% S n=8
  • 86% S n=7

Stops and timetable

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

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