Sp 1635 1635 Český Těšín – Návsí

View line Sp 1635

Český Těšín 04:48 → Návsí 05:13 Mon, Tue, Wed, Thu, Fri 0 h 25 min · 9 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 04:48 from Český Těšín · Mon 9 Nov

Next departure 04:48 Monday · Český Těšín
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Návsí, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
04:48on time +2 min
04:51≈ on time ≈ +2 min
04:52 / 04:53≈ on time ≈ +1 min
04:55 / 04:56≈ on time ≈ +1 min
04:59 / 05:00≈ on time ≈ +1 min
05:02≈ on time ≈ +1 min
05:05 / 05:06≈ on time ≈ +1 min
05:08 / 05:09≈ on time ≈ on time
05:13on 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 NovNávsí 05:14No data—
Thu 5 NovNávsí 05:14No data—
Wed 4 NovNávsí 05:14No data—
Tue 3 NovNávsí 05:15No data—
Mon 2 NovNávsí 05:14No data—
Fri 30 OctNávsí 05:14No data—
Thu 29 OctNávsí 05:14No data—
Tue 27 OctNávsí 05:14No data—
Mon 26 OctNávsí 05:14No data—
Fri 23 OctNávsí 05:14No data—
Thu 22 OctNávsí 05:14No data—
Wed 21 OctNávsí 05:14No data—
Tue 20 OctNávsí 05:14No data—
Mon 19 OctNávsí 05:14No data—
Fri 16 OctNávsí 05:14No data—
Thu 15 OctNávsí 05:14No data—
Wed 14 OctNávsí 05:14No data—
Tue 13 OctNávsí 05:14No data—
Mon 12 OctNávsí 05:14No data—
Fri 9 OctNávsí 05:14No data—
Thu 8 OctNávsí 05:14No data—
Wed 7 OctNávsí 05:14No data—
Tue 6 OctNávsí 05:14No data—
Mon 5 Oct— 05:280 min—
Fri 2 Oct— 05:270 min—
Thu 1 Oct— 05:270 min—
Wed 30 Sept— 05:26−1 min—
Tue 29 Sept— 05:270 min+1 min
Fri 25 Sept— 05:27−1 min—
Thu 24 Sept— 05:270 min—