S35 6515 Kerzers – Lyss

View line S35

Kerzers 19:06 → Lyss 19:26 Daily 0 h 20 min · 8 stops BLS

✓ Today’s run finished

Today it reached Lyss at 19:27 +1 min

  1. Kerzers19:06
  2. Kerzers Papiliorama19:08
  3. Fräschels19:10
  4. Bargen BE19:16
  5. Aarberg19:19
  6. Lyss Grien19:22
  7. Lyss19:26

Next service: tomorrow 19:06 from Kerzers · Fri 6 Nov

Next departure 19:06 tomorrow · Kerzers
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
97%
36/37 runs under 3 min
RT coverage: 37 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: +2 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

Worst days

  • Tue 13 Oct Max en route +4 min · last fix heading to Lyss +4 min

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 97% · 36
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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 10
19:06on time on time
19:08≈ on time ≈ on time
19:10≈ on time ≈ on time
19:13 / 19:14≈ on time ≈ on time
19:16 / 19:17≈ on time ≈ +1 min
19:19≈ on time ≈ +1 min
19:22≈ on time ≈ +1 min
19:26on 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 NovLyss 09:28+1 min—
Wed 4 NovLyss 09:240 min—
Tue 3 NovLyss 09:29+2 min+2 min
Mon 2 NovLyss 09:280 min—
Sun 1 NovLyss 09:270 min—
Sat 31 OctLyss 09:27+1 min—
Fri 30 OctLyss 09:270 min—
Thu 29 OctLyss 09:27No data—
Wed 28 OctLyss 09:29+1 min+1 min
Tue 27 OctLyss 09:28+1 min—
Mon 26 OctLyss 09:270 min—
Sun 25 OctLyss 09:27+1 min—
Sat 24 OctLyss 09:270 min—
Fri 23 OctLyss 09:28+1 min+1 min
Thu 22 OctLyss 09:27−1 min—
Wed 21 OctLyss 09:28+1 min—
Tue 20 OctLyss 09:29+1 min+1 min
Mon 19 OctLyss 09:270 min—
Sun 18 OctLyss 09:270 min—
Sat 17 OctLyss 09:270 min—
Fri 16 OctLyss 09:27+1 min—
Thu 15 OctLyss 09:29+2 min+2 min
Wed 14 OctLyss 09:28+1 min—
Tue 13 OctLyss 09:31+4 min+4 min
Mon 12 OctLyss 09:29+2 min+2 min
Sun 11 OctLyss 09:28+1 min—
Sat 10 OctLyss 09:29+1 min+1 min
Fri 9 OctLyss 09:270 min—
Thu 8 OctLyss 09:270 min—
Wed 7 OctLyss 09:27+1 min—