S36 6598 Büren an der Aare – Lyss

View line S36

Büren an der Aare 23:48 → Lyss 23:58 Daily 0 h 10 min · 4 stops BLS

It has not run yet today

Last recorded run: Friday 13 November +1 min

Next service: today 23:48 from Büren an der Aare · Sat 14 Nov

Next departure 23:48 today · Büren an der Aare
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
96%
50/52 runs under 3 min
RT coverage: 52 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Lyss, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 10 Nov Max en route +3 min · last fix heading to Lyss +3 min
  • Wed 14 Oct Max en route +3 min · last fix heading to Lyss +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 86% T n=7
  • 89% W n=9
  • 100% T n=8
  • 100% F n=6
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 52 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
23:48on time on time
23:50≈ on time ≈ on time
23:54≈ on time ≈ +1 min
23:58+1 min +2 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 13 NovLyss 23:59+1 min—
Thu 12 NovLyss 23:590 min—
Wed 11 NovLyss 23:590 min—
Tue 10 NovLyss 00:03+3 min+3 min
Mon 9 NovLyss 00:000 min—
Sun 8 NovLyss 23:590 min—
Sat 7 NovLyss 23:59+1 min+1 min
Fri 6 NovLyss 23:590 min—
Thu 5 NovLyss 23:59+1 min—
Wed 4 NovLyss 23:590 min—
Tue 3 NovLyss 23:590 min—
Mon 2 NovLyss 23:59−1 min—
Sun 1 NovLyss 23:590 min—
Sat 31 OctLyss 00:01+2 min+2 min
Fri 30 OctLyss 23:590 min—
Thu 29 OctLyss 00:00+1 min—
Wed 28 OctLyss 23:590 min—
Tue 27 OctLyss 00:00+1 min—
Mon 26 OctLyss 00:00+1 min—
Sun 25 OctLyss 00:00+2 min+2 min
Sat 24 OctLyss 00:00+2 min+2 min
Fri 23 OctLyss 00:01+2 min+2 min
Thu 22 OctLyss 00:00+1 min—
Wed 21 OctLyss 00:00+1 min+1 min
Tue 20 OctLyss 00:000 min—
Mon 19 OctLyss 00:00+1 min—
Sun 18 OctLyss 00:000 min—
Sat 17 OctLyss 00:00+1 min—
Fri 16 OctLyss 00:000 min—
Thu 15 OctLyss 23:59+1 min—