IR65 3368 Biel/Bienne – Bern

View line IR65

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

✓ Today’s run finished

Today it reached Bern at 18:48 −1 min

  1. Biel/Bienne18:22
  2. Lyss18:30
  3. Bern18:48

Next service: tomorrow 18:22 from Biel/Bienne · Sun 8 Nov

Next departure 18:22 tomorrow · Biel/Bienne
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
42/42 runs under 3 min
RT coverage: 42 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 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

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

  • Early 12% · 5
  • On time 88% · 37
  • 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=6
  • 100% W n=5
  • 100% T n=4
  • 100% F n=8
  • 100% S n=8
  • 100% S n=6

Stops and timetable

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

Last 90 days, 42 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
18:22on time on time
18:30 / 18:31≈ on time ≈ on time
18:48on 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 7 NovBern 18:48−1 min—
Fri 6 NovBern 18:49+1 min+1 min
Thu 5 NovBern 18:48−1 min—
Wed 4 NovBern 18:49No data—
Tue 3 NovBern 18:48−1 min—
Mon 2 NovBern 18:490 min—
Sun 1 NovBern 18:490 min—
Sat 31 OctBern 18:47−2 min—
Fri 30 OctBern 18:48−1 min—
Thu 29 OctBern 18:490 min—
Wed 28 OctBern 18:49−1 min+1 min
Tue 27 OctBern 18:50+1 min+2 min
Mon 26 OctBern 18:48−1 min—
Sun 25 OctBern 18:51+2 min+3 min
Sat 24 OctBern 18:490 min+2 min
Fri 23 OctBern 18:48−1 min—
Thu 22 OctBern 18:49−1 min—
Wed 21 OctBern 18:48−1 min—
Tue 20 OctBern 18:490 min+1 min
Mon 19 OctBern 18:480 min—
Sun 18 OctBern 18:490 min—
Sat 17 OctBern 18:47−1 min—
Fri 16 OctBern 18:500 min—
Thu 15 OctBern 18:48−1 min—
Wed 14 OctBern 18:48−1 min—
Tue 13 OctBern 18:490 min+3 min
Mon 12 OctBern 18:48−1 min—
Sun 11 OctBern 18:48−1 min—
Sat 10 OctBern 18:490 min—
Fri 9 OctBern 18:50+1 min—