S6 87660 Konstanz – Engen

View line S6

Konstanz 06:45 → Engen 07:32 Daily 0 h 47 min · 16 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Engen at 07:33 No data

  1. Konstanz06:45
  2. Konstanz-Wollmatingen06:51
  3. Hegne06:56
  4. Radolfzell07:07
  5. Singen (Htw) Industriegebiet07:15
  6. Mühlhausen (b Engen)07:25
  7. Engen07:32

Next service: tomorrow 06:45 from Konstanz · Fri 20 Nov

Next departure 06:45 tomorrow · Konstanz
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 47 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

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

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

  • Early 10% · 2
  • On time 90% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 21 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
06:45on time +1 min
06:48≈ on time ≈ +1 min
06:49 / 06:50≈ on time ≈ +1 min
06:51 / 06:52≈ on time ≈ +1 min
06:53 / 06:54≈ on time ≈ +1 min
06:56 / 06:57≈ on time ≈ on time
06:59 / 07:00≈ on time ≈ +1 min
07:04 / 07:05≈ on time ≈ +1 min
07:07 / 07:08≈ on time ≈ +1 min
07:11 / 07:12≈ on time ≈ +1 min
07:15≈ on time ≈ +1 min
07:18 / 07:19≈ on time ≈ +1 min
07:20 / 07:21≈ on time ≈ +1 min
07:25 / 07:26≈ on time ≈ +1 min
07:28 / 07:29≈ on time ≈ +1 min
07:32on 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 19 NovEngen 07:33No data—
Wed 18 NovEngen 07:33No data—
Tue 17 NovEngen 07:33No data—
Mon 16 NovEngen 07:33No data—
Sun 15 NovEngen 07:33No data—
Sat 14 NovEngen 07:33No data—
Fri 13 NovEngen 07:33No data—
Thu 12 NovEngen 07:34No data—
Wed 11 NovEngen 07:33No data—
Tue 10 NovEngen 07:33No data—
Mon 9 NovEngen 07:33No data—
Sun 8 NovEngen 07:34No data—
Sat 7 NovEngen 07:33No data—
Fri 6 NovEngen 07:33No data—
Thu 5 NovEngen 07:33No data—
Wed 4 NovEngen 07:33No data—
Tue 3 NovEngen 07:33No data—
Mon 2 NovEngen 07:33No data—
Sun 1 NovEngen 07:33No data—
Sat 31 OctEngen 07:33No data—
Fri 30 OctEngen 07:33No data—
Thu 29 OctEngen 07:33No data—
Wed 28 OctEngen 07:33No data—
Tue 27 OctEngen 07:33No data—
Mon 26 OctEngen 07:34No data—
Sun 25 OctEngen 07:33No data—
Sat 24 OctEngen 07:33No data—
Fri 23 OctEngen 07:33No data—
Thu 22 OctEngen 07:33No data—
Wed 21 OctEngen 07:33No data—