RE1 5241 Herisau – Konstanz

View line RE1

Herisau 21:05 → Konstanz 21:50 Daily 0 h 45 min · 5 stops Thurbo

✓ Today’s run finished

Today it reached Konstanz at 21:50 0 min

  1. Herisau21:05
  2. St. Gallen21:14
  3. Romanshorn21:33
  4. Kreuzlingen Hafen21:47
  5. Konstanz21:50

Next service: tomorrow 21:05 from Herisau · Sat 7 Nov

Next departure 21:05 tomorrow · Herisau
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

Stops and timetable

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

Last 90 days, 37 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
21:05on time on time
21:14 / 21:15≈ on time ≈ on time
21:33≈ on time ≈ on time
21:47≈ on time ≈ on time
21:50on time on time

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:490 min—
Thu 5 NovKonstanz 21:490 min—
Wed 4 NovKonstanz 21:490 min—
Tue 3 NovKonstanz 21:49−1 min—
Mon 2 NovKonstanz 21:490 min—
Sun 1 NovKonstanz 21:52+1 min—
Sat 31 OctKonstanz 21:510 min—
Fri 30 OctKonstanz 21:50−1 min—
Thu 29 OctKonstanz 21:50−1 min—
Wed 28 OctKonstanz 21:50−1 min—
Tue 27 OctKonstanz 21:520 min+3 min
Mon 26 OctKonstanz 21:51−1 min—
Sun 25 OctKonstanz 21:50−1 min—
Sat 24 OctKonstanz 21:50−1 min—
Fri 23 OctKonstanz 21:510 min—
Thu 22 OctKonstanz 21:520 min—
Wed 21 OctKonstanz 21:50−1 min—
Tue 20 OctKonstanz 21:510 min—
Mon 19 OctKonstanz 21:50−1 min—
Sun 18 OctKonstanz 21:51−1 min—
Sat 17 OctKonstanz 21:500 min—
Fri 16 OctKonstanz 21:51−1 min—
Thu 15 OctKonstanz 21:510 min—
Wed 14 OctKonstanz 21:51−1 min—
Tue 13 OctKonstanz 21:520 min—
Mon 12 OctKonstanz 21:510 min—
Sun 11 OctKonstanz 21:510 min—
Sat 10 OctKonstanz 21:54+3 min+3 min
Fri 9 OctKonstanz 21:51−1 min—
Thu 8 OctKonstanz 21:53+2 min+2 min