RE75 2101 Kreuzlingen – Konstanz

View line RE75

Kreuzlingen 05:46 → Konstanz 05:49 Daily 0 h 03 min · 2 stops Thurbo

✓ Today’s run finished

Today it reached Konstanz at 05:50 +1 min

  1. Kreuzlingen05:46
  2. Konstanz05:49

Next service: tomorrow 05:46 from Kreuzlingen · Sun 8 Nov

Next departure 05:46 tomorrow · Kreuzlingen
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 4 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 5 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 Konstanz, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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:46+1 min +1 min
05:49+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
Sat 7 NovKonstanz 05:49+1 min—
Fri 6 NovKonstanz 05:49+1 min—
Thu 5 NovKonstanz 05:49+1 min—
Wed 4 NovKonstanz 05:49+1 min—
Tue 3 NovKonstanz 05:49+1 min—
Mon 2 NovKonstanz 05:49+1 min—
Sun 1 NovKonstanz 05:50+1 min—
Sat 31 OctKonstanz 05:500 min—
Fri 30 OctKonstanz 05:500 min—
Thu 29 OctKonstanz 05:51+1 min—
Wed 28 OctKonstanz 05:51+1 min—
Tue 27 OctKonstanz 05:51+1 min—
Mon 26 OctKonstanz 05:490 min—
Sun 25 OctKonstanz 05:50No data—
Sat 24 OctKonstanz 05:500 min—
Fri 23 OctKonstanz 05:51+1 min—
Thu 22 OctKonstanz 05:50No data—
Wed 21 OctKonstanz 05:50No data—
Tue 20 OctKonstanz 05:50No data—
Mon 19 OctKonstanz 05:51+1 min—
Sun 18 OctKonstanz 05:51+1 min—
Sat 17 OctKonstanz 05:51+1 min—
Fri 16 OctKonstanz 05:500 min—
Thu 15 OctKonstanz 05:500 min—
Wed 14 OctKonstanz 05:500 min—
Tue 13 OctKonstanz 05:50+1 min—
Mon 12 OctKonstanz 05:50+1 min—
Sun 11 OctKonstanz 05:51+1 min—
Sat 10 OctKonstanz 05:51+1 min—
Fri 9 OctKonstanz 05:51+1 min—