S37 8008 Siselen-Finsterhennen – Ins

View line S37

Siselen-Finsterhennen 05:29 → Ins 05:39 Mon, Tue, Wed, Thu, Fri, Sat 0 h 10 min · 4 stops Aare Seeland mobil

✓ Today’s run finished

Today it reached Ins at 05:40 +1 min

  1. Siselen-Finsterhennen05:29
  2. Brüttelen05:32
  3. Ins Dorf05:36
  4. Ins05:39

Next service: tomorrow 05:29 from Siselen-Finsterhennen · Wed 18 Nov

Next departure 05:29 tomorrow · Siselen-Finsterhennen
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 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: +1 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

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

  • Early 0% · 0
  • On time 100% · 39
  • 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=6
  • 100% T n=6
  • 100% F n=6
  • 100% S n=7
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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:29on time on time
05:32≈ on time ≈ on time
05:36≈ on time ≈ +1 min
05:39+1 min +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 17 NovIns 05:39+1 min—
Mon 16 NovIns 05:39+1 min—
Sat 14 NovIns 05:39+1 min—
Fri 13 NovIns 05:40+1 min—
Thu 12 NovIns 05:39+1 min+1 min
Wed 11 NovIns 05:39+1 min+1 min
Tue 10 NovIns 05:390 min—
Mon 9 NovIns 05:39+1 min+1 min
Sat 7 NovIns 05:39+1 min—
Fri 6 NovIns 05:39+1 min—
Thu 5 NovIns 05:390 min—
Wed 4 NovIns 05:39+1 min—
Tue 3 NovIns 05:42+2 min+2 min
Mon 2 NovIns 05:39+1 min+1 min
Sat 31 OctIns 05:41+1 min—
Fri 30 OctIns 05:400 min—
Thu 29 OctIns 05:42+2 min+2 min
Wed 28 OctIns 05:400 min—
Tue 27 OctIns 05:400 min—
Mon 26 OctIns 05:40+1 min—
Sat 24 OctIns 05:42+2 min+2 min
Fri 23 OctIns 05:41+1 min+1 min
Thu 22 OctIns 05:41+1 min+1 min
Wed 21 OctIns 05:41+1 min+1 min
Tue 20 OctIns 05:400 min+1 min
Mon 19 OctIns 05:41+1 min+2 min
Sat 17 OctIns 05:410 min—
Fri 16 OctIns 05:400 min+1 min
Thu 15 OctIns 05:42+2 min+2 min
Wed 14 OctIns 05:41+1 min—