S36 6551 Lyss – Büren an der Aare

View line S36

Lyss 05:33 → Büren an der Aare 05:43 Daily 0 h 10 min · 4 stops BLS

✓ Today’s run finished

Today it reached Büren an der Aare at 05:43 0 min

  1. Lyss05:33
  2. Busswil BE05:36
  3. Dotzigen05:39
  4. Büren an der Aare05:43

Next service: tomorrow 05:33 from Lyss · Sun 8 Nov

Full trip card
Next departure 05:33 tomorrow · Lyss
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Büren an der Aare, 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

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=4
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 34 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
Lyss
05:33on time on time
Busswil BE
05:36≈ on time ≈ +1 min
Dotzigen
05:39≈ +1 min ≈ +1 min
Büren an der Aare
05:43+1 min +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
Sat 7 NovBüren an der Aare 05:440 min—
Fri 6 NovBüren an der Aare 05:440 min—
Thu 5 NovBüren an der Aare 05:440 min—
Wed 4 NovBüren an der Aare 05:44No data—
Tue 3 NovBüren an der Aare 05:440 min—
Mon 2 NovBüren an der Aare 05:440 min—
Sun 1 NovBüren an der Aare 05:440 min—
Sat 31 OctBüren an der Aare 05:45+1 min—
Fri 30 OctBüren an der Aare 05:440 min—
Thu 29 OctBüren an der Aare 05:45+1 min+1 min
Wed 28 OctBüren an der Aare 05:45+1 min—
Tue 27 OctBüren an der Aare 05:45+1 min—
Mon 26 OctBüren an der Aare 05:450 min—
Sun 25 OctBüren an der Aare 05:44+1 min—
Sat 24 OctBüren an der Aare 05:45+1 min+1 min
Fri 23 OctBüren an der Aare 05:46+2 min+2 min
Thu 22 OctBüren an der Aare 05:45+1 min—
Wed 21 OctBüren an der Aare 05:450 min—
Tue 20 OctBüren an der Aare 05:45+1 min—
Mon 19 OctBüren an der Aare 05:45+1 min—
Sun 18 OctBüren an der Aare 05:450 min—
Sat 17 OctBüren an der Aare 05:45+1 min+1 min
Fri 16 OctBüren an der Aare 05:440 min—
Thu 15 OctBüren an der Aare 05:450 min—
Wed 14 OctBüren an der Aare 05:46+2 min+2 min
Tue 13 OctBüren an der Aare 05:430 min—
Mon 12 OctBüren an der Aare 05:45+1 min—
Sun 11 OctBüren an der Aare 05:45+1 min—
Sat 10 OctBüren an der Aare 05:45+1 min—
Fri 9 OctBüren an der Aare 05:46+2 min+2 min