S4 30486 Langnau i.E. – Burgdorf

View line S4

Langnau i.E. 22:40 → Burgdorf 23:11 Tue, Wed, Thu, Fri, Sun 0 h 31 min · 9 stops SBB CFF FFS

It does not run today

Last recorded run: Tuesday 3 November No data

Next service: Wednesday 22:40 from Langnau i.E. · Wed 11 Nov

Next departure 22:40 Wednesday · Langnau i.E.
On-time · 30 days
—
Too little data (0/11 runs with data)
RT coverage: 0 full · 0 partial · 11 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Burgdorf, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 6 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
22:40on time on time
22:44≈ on time ≈ on time
22:46≈ on time ≈ on time
22:51 / 22:52≈ on time ≈ on time
22:55≈ on time ≈ on time
22:59 / 23:01≈ on time ≈ on time
23:04≈ on time ≈ on time
23:06≈ on time ≈ on time
23:11on time on time

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
Tue 3 NovBurgdorf 23:12No data—
Sun 1 NovBurgdorf 23:12No data—
Fri 23 OctVallorbe 01:00No data—
Thu 22 OctVallorbe 01:00No data—
Wed 21 OctVallorbe 01:00No data—
Tue 20 OctVallorbe 01:00No data—
Fri 16 OctVallorbe 01:00No data—
Thu 15 OctVallorbe 01:00No data—
Wed 14 OctVallorbe 01:00No data—
Tue 13 OctVallorbe 01:00No data—
Sat 10 OctThun 00:23No data—
Sat 26 SeptPully 19:390 min—
Mon 7 SeptBussigny 23:060 min+3 min
Sun 6 SeptBussigny 00:060 min—
Sat 5 SeptMorges 01:59−1 min+10 min
Sat 29 AugBrig 23:320 min+34 min
Thu 13 AugBurgdorf 01:200 min+5 min