S36 6573 Lyss – Büren an der Aare

View line S36

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

✓ Today’s run finished

Today, last fix heading to Büren an der Aare at 13:44 No data

  1. Lyss13:33
  2. Busswil BE13:36
  3. Dotzigen13:39
  4. Büren an der Aare13:43

Next service: tomorrow 13:33 from Lyss · Fri 6 Nov

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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=1
  • 100% F n=4
  • 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, 28 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
13:33on time on time
13:36≈ on time ≈ +1 min
13:39≈ on time ≈ +1 min
13:43on 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
Thu 5 NovBüren an der Aare 13:44No data—
Wed 4 NovBüren an der Aare 13:440 min—
Tue 3 NovBüren an der Aare 13:440 min—
Mon 2 NovBüren an der Aare 13:44No data—
Sun 1 NovBüren an der Aare 13:45+1 min+1 min
Sat 31 OctBüren an der Aare 13:440 min—
Fri 30 OctBüren an der Aare 13:440 min—
Thu 29 OctBüren an der Aare 13:44No data—
Wed 28 OctBüren an der Aare 13:450 min—
Tue 27 OctBüren an der Aare 13:45+1 min—
Mon 26 OctBüren an der Aare 13:44No data—
Sun 25 OctBüren an der Aare 13:440 min—
Sat 24 OctBüren an der Aare 13:440 min—
Fri 23 OctBüren an der Aare 13:440 min—
Thu 22 OctBüren an der Aare 13:44No data—
Wed 21 OctBüren an der Aare 13:45+1 min+1 min
Tue 20 OctBüren an der Aare 13:440 min—
Mon 19 OctBüren an der Aare 13:440 min—
Sun 18 OctBüren an der Aare 13:46+2 min+2 min
Sat 17 OctBüren an der Aare 13:44+1 min—
Fri 16 OctBüren an der Aare 13:450 min—
Thu 15 OctBüren an der Aare 13:44No data—
Wed 14 OctBüren an der Aare 13:45+1 min+1 min
Tue 13 OctBüren an der Aare 13:45+1 min—
Mon 12 OctBüren an der Aare 13:44No data—
Sun 11 OctBüren an der Aare 13:440 min—
Sat 10 OctBüren an der Aare 13:450 min—
Fri 9 OctBüren an der Aare 13:44+1 min—
Thu 8 OctBüren an der Aare 13:45+1 min+1 min
Wed 7 OctBüren an der Aare 13:440 min—