S4 94402 Tychy Lodowisko – Tychy

View line S4

Tychy Lodowisko 04:52 → Tychy 05:01 Mon, Tue, Wed, Thu, Fri 0 h 09 min · 5 stops Koleje Śląskie

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 04:52 from Tychy Lodowisko · Mon 16 Nov

Next departure 04:52 today · Tychy Lodowisko
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 5 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 29 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 Tychy, 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

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=4
  • 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 (5 stops).

Last 90 days, 25 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:52on time on time
04:54≈ on time ≈ on time
04:55 / 04:56≈ on time ≈ on time
04:57≈ on time ≈ on time
05:01on 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 1 August 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 13 NovTychy 05:020 min—
Thu 12 NovTychy 05:020 min—
Tue 10 NovTychy 05:030 min—
Mon 9 NovTychy 05:020 min—
Fri 6 NovTychy 05:020 min—
Thu 5 NovTychy 05:020 min—
Wed 4 NovTychy 05:020 min—
Tue 3 NovTychy 05:020 min—
Mon 2 NovTychy 05:020 min—
Fri 30 OctTychy 05:02No data—
Thu 29 OctTychy 05:020 min—
Wed 28 OctTychy 05:020 min—
Tue 27 OctTychy 05:030 min—
Mon 26 OctTychy 05:020 min—
Fri 23 OctTychy 05:02No data—
Thu 22 OctTychy 05:02No data—
Wed 21 OctTychy 05:02No data—
Tue 20 OctTychy 05:02No data—
Mon 19 OctTychy 05:020 min—
Fri 16 OctTychy 05:030 min—
Thu 15 OctTychy 05:020 min—
Wed 14 OctTychy 05:020 min—
Tue 13 OctTychy 05:020 min—
Mon 12 OctTychy 05:020 min—
Fri 9 OctTychy 05:020 min—
Thu 8 OctTychy 05:030 min—
Wed 7 OctTychy 05:020 min—
Tue 6 OctTychy 05:020 min—
Mon 5 OctTychy 05:030 min—
Fri 2 OctTychy 05:00No data—