S4 30483 Bern – Lützelflüh-Goldbach

View line S4

Bern 00:23 → Lützelflüh-Goldbach 01:20 Mon, Tue, Wed, Thu, Fri, Sun 0 h 57 min · 11 stops BLS

It has not run yet today

Last recorded run: Wednesday 18 November No data

Next service: Sunday 00:23 from Bern · Sun 22 Nov

Next departure 00:23 Sunday · Bern
On-time · 30 days
—
Too little data (0/18 runs with data)
RT coverage: 0 full · 0 partial · 18 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 7 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Lützelflüh-Goldbach, 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 100% W n=1
  • 100% T n=2
  • — F n=0
  • — S n=0
  • 100% S n=1

Stops and timetable

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

Last 90 days, 7 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
00:23on time on time
00:26≈ on time ≈ on time
00:30≈ on time ≈ on time
00:33 / 00:34≈ on time ≈ on time
00:38≈ on time ≈ on time
00:41≈ on time ≈ on time
00:45 / 00:49≈ on time ≈ on time
00:51 / 00:52≈ on time ≈ +1 min
00:54≈ on time ≈ +1 min
00:58 / 01:18≈ on time ≈ +1 min
01:20on 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
Wed 18 NovBern 22:19Partial coverageNo data—
Tue 17 NovBern 22:19Partial coverageNo data—
Mon 16 NovBern 22:19No data—
Sun 15 NovBern 22:19No data—
Fri 13 NovLangnau i.E. 23:19No data—
Thu 12 NovLangnau i.E. 23:20No data—
Wed 11 NovLangnau i.E. 23:19No data—
Tue 10 NovBern 22:19No data—
Mon 9 NovBern 22:18No data—
Thu 5 NovBern 22:19No data—
Wed 4 NovBern 22:19Partial coverageNo data—
Tue 3 NovLangnau i.E. 23:19No data—
Mon 2 NovBern 22:19No data—
Sun 1 NovLangnau i.E. 23:19No data—
Thu 29 OctBern 22:19No data—
Wed 28 OctBern 22:19No data—
Tue 27 OctBern 22:19No data—
Mon 26 OctBern 22:19No data—
Fri 9 OctBurgistein 21:52No data—
Thu 8 OctBurgistein 21:51No data—
Wed 7 OctBurgistein 21:51No data—
Thu 1 OctBelp 00:060 min—
Tue 29 SeptBelp 23:04+2 min+2 min
Mon 28 SeptBelp 23:05−1 min+5 min
Sun 27 SeptSt-Maurice 23:42+1 min—
Sat 26 SeptSt-Maurice 15:42No data—
Thu 3 SeptLützelflüh-Goldbach 01:040 min+2 min
Wed 2 SeptLützelflüh-Goldbach 01:04+1 min—
Mon 31 AugLützelflüh-Goldbach 01:040 min+8 min