S44 16444 Burgdorf – Thun

View line S44

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

✓ Today’s run finished

Today, last fix heading to Thun at 13:52 No data

  1. Burgdorf12:51
  2. Hindelbank12:57
  3. Bern13:11
  4. Kaufdorf13:30
  5. Burgistein13:37
  6. Uetendorf13:43
  7. Thun13:51

Next service: tomorrow 12:51 from Burgdorf · Fri 6 Nov

Next departure 12:51 tomorrow · Burgdorf
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 41 full · 0 partial · 8 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

  • Sun 18 Oct Max en route +4 min · last fix heading to Thun +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=8
  • 100% W n=8
  • 100% T n=2
  • 100% F n=7
  • 100% S n=5
  • 88% S n=8

Stops and timetable

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

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