S36 6583 Lyss – Büren an der Aare

View line S36

Lyss 17:03 → Büren an der Aare 17:13 Mon, Tue, Wed, Thu, Fri 0 h 10 min · 4 stops BLS

✓ Today’s run finished

Today it reached Büren an der Aare at 17:13 0 min

  1. Lyss17:03
  2. Busswil BE17:06
  3. Dotzigen17:09
  4. Büren an der Aare17:13

Next service: tomorrow 17:03 from Lyss · Tue 17 Nov

Next departure 17:03 tomorrow · Lyss
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
100%
32/32 runs under 3 min
RT coverage: 32 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 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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
17:03on time on time
17:06≈ on time ≈ +1 min
17:09≈ on time ≈ +1 min
17:13on 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
Mon 16 NovBüren an der Aare 17:140 min—
Fri 13 NovBüren an der Aare 17:140 min—
Thu 12 NovBüren an der Aare 17:14+1 min—
Wed 11 NovBüren an der Aare 17:140 min—
Tue 10 NovBüren an der Aare 17:140 min—
Mon 9 NovBüren an der Aare 17:140 min—
Fri 6 NovBüren an der Aare 17:140 min—
Thu 5 NovBüren an der Aare 17:140 min—
Wed 4 NovBüren an der Aare 17:140 min—
Tue 3 NovBüren an der Aare 17:140 min—
Mon 2 NovBüren an der Aare 17:140 min—
Fri 30 OctBüren an der Aare 17:140 min—
Thu 29 OctBüren an der Aare 17:150 min—
Wed 28 OctBüren an der Aare 17:15+1 min—
Tue 27 OctBüren an der Aare 17:15+1 min—
Mon 26 OctBüren an der Aare 17:140 min—
Fri 23 OctBüren an der Aare 17:15+1 min—
Thu 22 OctBüren an der Aare 17:150 min—
Wed 21 OctBüren an der Aare 17:140 min—
Tue 20 OctBüren an der Aare 17:150 min—
Mon 19 OctBüren an der Aare 17:16+3 min+3 min
Fri 16 OctBüren an der Aare 17:16+1 min+1 min
Thu 15 OctBüren an der Aare 17:140 min—
Wed 14 OctBüren an der Aare 17:15+1 min—
Tue 13 OctBüren an der Aare 17:15+1 min—
Mon 12 OctBüren an der Aare 17:15+1 min—
Fri 9 OctBüren an der Aare 17:150 min—
Thu 8 OctBüren an der Aare 17:140 min—
Wed 7 OctBüren an der Aare 17:15+1 min—
Tue 6 OctBüren an der Aare 17:140 min—