Sp 3352 3352 Studénka – Štramberk

View line Sp 3352

Studénka 06:15 → Štramberk 06:40 Daily 0 h 25 min · 8 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Saturday 7 November No data

Next service: today 06:15 from Studénka · Sun 8 Nov

Next departure 06:15 today · Studénka
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
77%
43/56 runs under 3 min
RT coverage: 56 full · 0 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
P90
+14min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Štramberk, in minutes. One bar per run.

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

Worst days

  • Mon 14 Sept Max en route +52 min · last fix heading to — +50 min
  • Mon 17 Aug Max en route +29 min · last fix heading to — +29 min
  • Wed 9 Sept Max en route +27 min · last fix heading to — +25 min
  • Sat 15 Aug Max en route +18 min · last fix heading to — +17 min
  • Wed 19 Aug Max en route +17 min · last fix heading to — +16 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 77% · 43
  • 3–10 min 11% · 6
  • 10–30 min 11% · 6
  • 30+ min 2% · 1

On-time by weekday

  • 75% M n=8
  • 75% T n=8
  • 63% W n=8
  • 75% T n=8
  • 75% F n=8
  • 75% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 56 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:15on time +8 min
06:21≈ on time ≈ +8 min
06:23≈ on time ≈ +10 min
06:25 / 06:26≈ on time ≈ +11 min
06:29 / 06:30≈ +1 min ≈ +12 min
06:33 / 06:34≈ on time ≈ +13 min
06:35 / 06:36≈ on time ≈ +13 min
06:40on time +14 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 NovŠtramberk 06:39No data—
Fri 6 NovŠtramberk 06:39No data—
Thu 5 NovŠtramberk 06:39No data—
Wed 4 NovŠtramberk 06:39No data—
Tue 3 NovŠtramberk 06:39No data—
Mon 2 NovŠtramberk 06:39No data—
Sun 1 NovŠtramberk 06:41No data—
Sat 31 OctŠtramberk 06:41No data—
Fri 30 OctŠtramberk 06:41No data—
Thu 29 OctŠtramberk 06:41No data—
Wed 28 OctŠtramberk 06:41No data—
Tue 27 OctŠtramberk 06:41No data—
Mon 26 OctŠtramberk 06:41No data—
Sun 25 OctŠtramberk 06:41No data—
Sat 24 OctŠtramberk 06:41No data—
Fri 23 OctŠtramberk 06:41No data—
Thu 22 OctŠtramberk 06:41No data—
Wed 21 OctŠtramberk 06:41No data—
Tue 20 OctŠtramberk 06:41No data—
Mon 19 OctŠtramberk 06:41No data—
Sun 18 OctŠtramberk 06:41No data—
Sat 17 OctŠtramberk 06:41No data—
Fri 16 OctŠtramberk 06:41No data—
Thu 15 OctŠtramberk 06:41No data—
Wed 14 OctŠtramberk 06:41No data—
Tue 13 OctŠtramberk 06:41No data—
Mon 12 OctŠtramberk 06:41No data—
Sun 11 OctŠtramberk 06:41No data—
Sat 10 OctŠtramberk 06:41No data—
Fri 9 OctŠtramberk 06:41No data—