IR65 3376 Biel/Bienne → Bern

View line IR65

Biel/Bienne 20:22 → Bern 20:48 Daily 0 h 26 min · 3 stops BLS

IR65 3376 Biel/Bienne–Bern: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. Running now, on time. Expected at Bern: 20:48. TrainsRadar data as of 21 Nov 2026, 20:45 (GMT+1).

Running now · updated 20:44

Position estimated from the timetable

Between Lyss and Bern −1 min

Estimated arrival at Bern 20:48 · 78 km/h

  1. Biel/Bienne20:22
  2. Lyss20:30
  3. Bern20:48

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

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
50/51 runs under 3 min
RT coverage: 51 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 Bern, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 7 Nov Max en route +16 min · last fix heading to Bern +16 min

Distribution · 90 days

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

  • Early 14% · 7
  • On time 84% · 43
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=8
  • 88% S n=8
  • 100% S n=7

Stops and timetable

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

Last 90 days, 51 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
20:22on time on timePassed
20:30 / 20:31≈ on time ≈ on timePassed
20:48on time +1 minNext

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 NovBern 20:44−1 min+3 min
Fri 20 NovBern 20:490 min—
Thu 19 NovBern 20:48−1 min+3 min
Wed 18 NovBern 20:48−1 min+1 min
Tue 17 NovBern 20:490 min+2 min
Mon 16 NovBern 20:490 min+2 min
Sun 15 NovBern 20:490 min—
Sat 14 NovBern 20:490 min—
Fri 13 NovBern 20:490 min—
Thu 12 NovBern 20:49+1 min+1 min
Wed 11 NovBern 20:48−1 min—
Tue 10 NovBern 20:480 min—
Mon 9 NovBern 20:48−1 min—
Sun 8 NovBern 20:490 min—
Sat 7 NovBern 21:02+16 min+16 min
Fri 6 NovBern 20:480 min—
Thu 5 NovBern 20:49+1 min—
Wed 4 NovBern 20:490 min—
Tue 3 NovBern 20:48−1 min—
Mon 2 NovBern 20:48−1 min—
Sun 1 NovBern 20:490 min—
Sat 31 OctBern 20:47−2 min—
Fri 30 OctBern 20:490 min—
Thu 29 OctBern 20:48−1 min—
Wed 28 OctBern 20:490 min—
Tue 27 OctBern 20:48−1 min+2 min
Mon 26 OctBern 20:49−1 min+2 min
Sun 25 OctBern 20:490 min+3 min
Sat 24 OctBern 20:490 min—
Fri 23 OctBern 20:50+1 min+1 min