S14 23864 Berg – Konstanz

View line S14

Berg 13:46 → Konstanz 14:05 Daily 0 h 19 min · 7 stops Thurbo

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:46 from Berg · Fri 6 Nov

Next departure 13:46 today · Berg
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 8 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 32 full · 0 partial · 8 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 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

  • Sat 17 Oct Max en route +5 min · last fix heading to Konstanz +5 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Konstanz +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 30
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 67% T n=3
  • 100% F n=5
  • 83% S n=6
  • 100% S n=3

Stops and timetable

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

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