S36 6592 Büren an der Aare – Lyss

View line S36

Büren an der Aare 06:46 → Lyss 06:56 Daily 0 h 10 min · 4 stops BLS

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: tomorrow 06:46 from Büren an der Aare · Tue 17 Nov

Next departure 06:46 tomorrow · Büren an der Aare
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 full · 0 partial · 0 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: +1 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 43 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
06:46on time on time
06:48≈ on time ≈ on time
06:52≈ on time ≈ +1 min
06:56on 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
Sun 15 NovLyss 20:570 min—
Sat 14 NovLyss 20:570 min—
Fri 13 NovLyss 20:570 min—
Thu 12 NovLyss 20:580 min—
Wed 11 NovLyss 20:58+1 min—
Tue 10 NovLyss 20:57+1 min—
Mon 9 NovLyss 20:57+1 min—
Sun 8 NovLyss 20:570 min—
Sat 7 NovLyss 20:57+1 min—
Fri 6 NovLyss 20:57+1 min—
Thu 5 NovLyss 20:57+1 min—
Wed 4 NovLyss 20:570 min—
Tue 3 NovLyss 20:570 min—
Mon 2 NovLyss 20:570 min—
Sun 1 NovLyss 20:570 min—
Sat 31 OctLyss 20:570 min—
Fri 30 OctLyss 20:58+1 min+1 min
Thu 29 OctLyss 20:570 min—
Wed 28 OctLyss 20:58+1 min—
Tue 27 OctLyss 20:58+1 min—
Mon 26 OctLyss 20:59+2 min+2 min
Sun 25 OctLyss 20:56−1 min—
Sat 24 OctLyss 20:560 min—
Fri 23 OctLyss 20:570 min—
Thu 22 OctLyss 20:58+1 min—
Wed 21 OctLyss 20:570 min—
Tue 20 OctLyss 20:580 min—
Mon 19 OctLyss 20:570 min—
Sun 18 OctLyss 20:570 min—
Sat 17 OctLyss 20:560 min—