S44 16472 Burgdorf → Thun

View line S44

Burgdorf 19:51 → Thun 20:51 Daily 1 h 00 min · 14 stops BLS

S44 16472 Burgdorf–Thun: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Thun: 20:51. TrainsRadar data as of 22 Nov 2026, 20:47 (GMT+1).

Running now · updated 20:46

Position estimated from the timetable

Between Uetendorf Allmend and Thun 0 min

Estimated arrival at Thun 20:51 · 36 km/h

  1. Burgdorf19:51
  2. Hindelbank19:57
  3. Bern20:11
  4. Kaufdorf20:30
  5. Burgistein20:37
  6. Uetendorf Allmend20:46
  7. Thun20:51

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 30 runs arrived on time.

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
100%
60/60 runs under 3 min
RT coverage: 59 full · 1 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 60
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 100% W n=9
  • 100% T n=10
  • 100% F n=9
  • 100% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 60 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 10Today
19:51on time on timePassed
19:53≈ on time ≈ on timePassed
19:57≈ on time ≈ on timePassed
20:05≈ on time ≈ on timePassed
20:11 / 20:12≈ on time ≈ +1 minPassed
20:24≈ on time ≈ +1 minPassed
20:27≈ on time ≈ +1 minPassed
20:30≈ on time ≈ +1 minPassed
20:33≈ on time ≈ +1 minPassed
20:37≈ on time ≈ +1 minPassed
20:39≈ on time ≈ +1 minPassed
20:43≈ on time ≈ +1 minPassed
20:46≈ on time ≈ +1 minPassed
20:51on time +2 minNext

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 22 NovUetendorf Allmend 20:44Partial coverage0 min—
Sat 21 NovThun 20:520 min—
Fri 20 NovThun 20:49−1 min—
Thu 19 NovThun 20:54+3 min+3 min
Wed 18 NovThun 20:52+1 min—
Tue 17 NovThun 20:530 min—
Mon 16 NovThun 20:53+2 min+2 min
Sun 15 NovThun 20:520 min—
Sat 14 NovThun 20:490 min—
Fri 13 NovThun 20:52−1 min—
Thu 12 NovThun 20:530 min—
Wed 11 NovThun 20:520 min—
Tue 10 NovThun 20:49−1 min—
Mon 9 NovThun 20:52−1 min—
Sun 8 NovThun 20:520 min—
Sat 7 NovThun 20:49−1 min—
Fri 6 NovThun 20:49−1 min—
Thu 5 NovThun 20:520 min—
Wed 4 NovThun 20:520 min—
Tue 3 NovThun 20:54+1 min+1 min
Mon 2 NovThun 20:520 min—
Sun 1 NovThun 20:520 min—
Sat 31 OctThun 20:520 min—
Fri 30 OctThun 20:520 min—
Thu 29 OctThun 20:54+2 min+2 min
Wed 28 OctThun 20:53+1 min+1 min
Tue 27 OctThun 20:520 min—
Mon 26 OctThun 20:52−1 min—
Sun 25 OctThun 20:510 min—
Sat 24 OctThun 20:520 min—