S37 7062 Biel/Bienne → Ins

View line S37

Biel/Bienne 11:50 → Ins 12:24 Daily 0 h 34 min · 16 stops Aare Seeland mobil

S37 7062 Biel/Bienne–Ins: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 15:29 (GMT+1).

✓ Today’s run finished

Today it reached Ins at 12:26 +2 min

  1. Biel/Bienne11:50
  2. Ipsach11:54
  3. Sutz11:57
  4. Gerolfingen12:03
  5. Hagneck12:09
  6. Brüttelen12:17
  7. Ins12:24

Next service: tomorrow 11:50 from Biel/Bienne · Sun 22 Nov

Next departure 11:50 tomorrow · Biel/Bienne
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
50/50 runs under 3 min
RT coverage: 50 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Ins, 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

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=8
  • 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 (16 stops).

Last 90 days, 50 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
11:50on time on time
11:52≈ on time ≈ on time
11:53≈ on time ≈ on time
11:54≈ on time ≈ on time
11:55≈ on time ≈ on time
11:57≈ on time ≈ on time
12:00≈ on time ≈ on time
12:02≈ on time ≈ on time
12:03≈ on time ≈ +1 min
12:06 / 12:07≈ on time ≈ +1 min
12:09≈ on time ≈ +1 min
12:11≈ on time ≈ +1 min
12:14≈ on time ≈ +1 min
12:17≈ on time ≈ +1 min
12:21≈ on time ≈ +2 min
12:24on time +2 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 NovIns 12:27+2 min+2 min
Fri 20 NovButtes 17:240 min+2 min
Thu 19 NovButtes 17:240 min—
Wed 18 NovButtes 17:24+1 min+6 min
Tue 17 NovButtes 17:240 min+2 min
Mon 16 NovButtes 17:240 min+6 min
Sun 15 NovButtes 17:24+1 min+2 min
Sat 14 NovButtes 17:240 min—
Fri 13 NovButtes 17:28+2 min+2 min
Thu 12 NovButtes 17:27+2 min+2 min
Wed 11 NovButtes 17:27+1 min+2 min
Tue 10 NovButtes 17:24+1 min+2 min
Mon 9 NovButtes 17:240 min—
Sun 8 NovButtes 17:24+1 min+1 min
Sat 7 NovButtes 17:27+2 min+3 min
Fri 6 NovButtes 17:28+2 min+2 min
Thu 5 NovButtes 17:240 min—
Wed 4 NovButtes 17:24+2 min+2 min
Tue 3 NovButtes 17:240 min+2 min
Mon 2 NovButtes 17:240 min—
Sun 1 NovButtes 17:260 min+2 min
Sat 31 OctButtes 17:260 min+1 min
Fri 30 OctButtes 17:260 min+3 min
Thu 29 OctButtes 17:260 min—
Wed 28 OctButtes 17:260 min+2 min
Tue 27 OctButtes 17:260 min+2 min
Mon 26 OctButtes 17:29+2 min+3 min
Sun 25 OctButtes 17:250 min+2 min
Sat 24 OctButtes 17:25−1 min+3 min
Fri 23 OctButtes 17:27+1 min+2 min