RB47 1271 Heimerdingen – Korntal

View line RB47

Heimerdingen 17:01 → Korntal 17:24 Daily 0 h 23 min · 7 stops SBB CFF FFS

It has not run yet today

Last recorded run: Sunday 15 November −2 min

Next service: today 17:01 from Heimerdingen · Mon 16 Nov

Next departure 17:01 today · Heimerdingen
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 4 no data
On-time · 90 days
98%
41/42 runs under 3 min
RT coverage: 42 full · 0 partial · 10 no data
Typical delay
−4min
Median at arrival, 90 days
30 days: −5 min
P90
0min
9 in 10 runs arrive with less than this
30 days: −3 min

Last 30 days

Arrival delay at Korntal, in minutes. One bar per run.

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

Worst days

  • Tue 6 Oct Max en route +9 min · last fix heading to Susch +8 min

Distribution · 90 days

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

  • Early 86% · 36
  • On time 12% · 5
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 89% T n=9
  • 100% W n=10
  • 100% T n=6
  • — F n=0
  • — S n=0
  • 100% S n=10

Stops and timetable

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

Last 90 days, 42 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
17:01on time on time
17:06≈ 1 min early ≈ on time
17:11≈ 2 min early ≈ on time
17:14 / 17:16≈ 2 min early ≈ on time
17:18≈ 3 min early ≈ on time
17:21≈ 4 min early ≈ on time
17:244 min early 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
Sun 15 NovKorntal 22:54−2 min—
Sat 14 NovKorntal 22:54No data—
Fri 13 NovKorntal 22:54No data—
Thu 12 NovKorntal 22:54−4 min—
Wed 11 NovKorntal 22:54−5 min—
Tue 10 NovKorntal 22:54−4 min—
Mon 9 NovKorntal 22:54−5 min—
Sun 8 NovKorntal 22:54−2 min—
Sat 7 NovKorntal 22:54No data—
Fri 6 NovKorntal 22:54No data—
Thu 5 NovKorntal 22:54−5 min—
Wed 4 NovKorntal 22:54−5 min—
Tue 3 NovKorntal 22:54−3 min—
Mon 2 NovKorntal 22:54−4 min—
Sun 1 NovKorntal 22:54−5 min—
Thu 29 OctSusch 20:49−5 min—
Wed 28 OctSusch 20:49−5 min—
Tue 27 OctSusch 20:49−5 min—
Mon 26 OctSusch 20:49−5 min—
Sun 25 OctSusch 20:49−5 min—
Thu 22 OctSusch 20:49−5 min—
Wed 21 OctSusch 20:49−5 min—
Tue 20 OctSusch 20:51−3 min—
Mon 19 OctSusch 20:51−3 min—
Sun 18 OctSusch 20:49−5 min—
Thu 15 OctSusch 20:54+1 min—
Wed 14 OctSusch 20:50−4 min—
Tue 13 OctSusch 20:50−4 min—
Mon 12 OctSusch 20:50−4 min—
Sun 11 OctSusch 20:49−5 min—