IR65 3318 Biel/Bienne – Bern

View line IR65

Biel/Bienne 05:52 → Bern 06:18 Daily 0 h 26 min · 3 stops BLS

✓ Today’s run finished

Today it reached Bern at 06:18 0 min

  1. Biel/Bienne05:52
  2. Lyss06:00
  3. Bern06:18

Next service: tomorrow 05:52 from Biel/Bienne · Wed 11 Nov

Next departure 05:52 tomorrow · Biel/Bienne
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 9 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 Bern, 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 3% · 1
  • On time 97% · 36
  • 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=6
  • 100% S n=7

Stops and timetable

Timetable of the latest run from the operator’s GTFS (3 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
05:52on time on time
06:00 / 06:01≈ on time ≈ on time
06:18on 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
Tue 10 NovBern 06:190 min—
Mon 9 NovBern 06:190 min—
Sun 8 NovBern 06:19No data—
Sat 7 NovBern 06:190 min—
Fri 6 NovBern 06:190 min—
Thu 5 NovBern 06:19No data—
Wed 4 NovBern 06:190 min—
Tue 3 NovBern 06:19−1 min—
Mon 2 NovBern 06:19+1 min—
Sun 1 NovBern 06:190 min—
Sat 31 OctBern 06:20+1 min—
Fri 30 OctBern 06:19No data—
Thu 29 OctBern 06:18−1 min—
Wed 28 OctBern 06:190 min—
Tue 27 OctBern 06:190 min—
Mon 26 OctBern 06:180 min—
Sun 25 OctBern 06:180 min—
Sat 24 OctBern 06:21+2 min+2 min
Fri 23 OctBern 06:190 min—
Thu 22 OctBern 06:19−1 min—
Wed 21 OctBern 06:190 min—
Tue 20 OctBern 06:19No data—
Mon 19 OctBern 06:19No data—
Sun 18 OctBern 06:19−1 min—
Sat 17 OctBern 06:190 min—
Fri 16 OctBern 06:190 min—
Thu 15 OctBern 06:190 min—
Wed 14 OctBern 06:20+1 min—
Tue 13 OctBern 06:190 min—
Mon 12 OctBern 06:19No data—