S36 6568 Büren an der Aare → Lyss

View line S36

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

S36 6568 Büren an der Aare–Lyss: final delay under 3 min on 21 of its 21 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Lyss: 11:56. TrainsRadar data as of 22 Nov 2026, 11:49 (GMT+1).

Running now · updated 11:49

Position estimated from the timetable

Between Dotzigen and Busswil BE 0 min

Estimated arrival at Lyss 11:56 · 46 km/h

  1. Büren an der Aare11:46
  2. Dotzigen11:48
  3. Busswil BE11:52
  4. Lyss11:56

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 21 runs arrived on time.

On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 12 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

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

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

On-time by weekday

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

Stops and timetable

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

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