S14 23906 Berg – Konstanz

View line S14

Berg 20:46 → Konstanz 21:05 Daily 0 h 19 min · 7 stops Thurbo

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 20:46 from Berg · Sat 7 Nov

Next departure 20:46 today · Berg
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
97%
34/35 runs under 3 min
RT coverage: 35 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 Konstanz, in minutes. One bar per run.

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

Worst days

  • Wed 28 Oct Max en route +3 min · last fix heading to Konstanz +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 34
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 83% W n=6
  • 100% T n=5
  • 100% F n=6
  • 100% S n=5
  • 100% S n=2

Stops and timetable

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

Last 90 days, 35 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
20:46on time on time
20:49≈ on time ≈ +1 min
20:52≈ on time ≈ +1 min
20:55≈ on time ≈ +1 min
20:58≈ on time ≈ +1 min
21:02≈ on time ≈ +1 min
21:05on 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
Fri 6 NovKonstanz 21:07+1 min+1 min
Thu 5 NovKonstanz 21:07+2 min+2 min
Wed 4 NovKonstanz 21:040 min—
Tue 3 NovKonstanz 21:07+1 min—
Mon 2 NovKonstanz 21:040 min—
Sat 31 OctKonstanz 21:060 min—
Fri 30 OctKonstanz 21:07+1 min—
Thu 29 OctKonstanz 21:060 min—
Wed 28 OctKonstanz 21:09+3 min+3 min
Tue 27 OctKonstanz 21:07+1 min+1 min
Mon 26 OctKonstanz 21:060 min—
Sat 24 OctKonstanz 21:060 min—
Fri 23 OctKonstanz 21:07+1 min+1 min
Thu 22 OctKonstanz 21:060 min—
Wed 21 OctKonstanz 21:08+2 min+2 min
Tue 20 OctKonstanz 21:060 min—
Mon 19 OctKonstanz 21:060 min—
Sun 18 OctKonstanz 21:040 min—
Sat 17 OctKonstanz 21:030 min—
Fri 16 OctKonstanz 21:06+2 min+2 min
Thu 15 OctKonstanz 21:040 min—
Wed 14 OctKonstanz 21:04−1 min—
Tue 13 OctKonstanz 21:050 min—
Mon 12 OctKonstanz 21:07+3 min+3 min
Sun 11 OctKonstanz 21:03−1 min—
Sat 10 OctKonstanz 21:050 min—
Fri 9 OctKonstanz 21:050 min—
Thu 8 OctKonstanz 21:050 min—
Wed 7 OctKonstanz 21:050 min—
Tue 6 OctKonstanz 21:040 min—