S4 94404 Tychy Lodowisko – Tychy

View line S4

Tychy Lodowisko 05:16 → Tychy 05:25 Daily 0 h 09 min · 5 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Tychy at 05:25 0 min

  1. Tychy Lodowisko05:16
  2. Tychy Grota Roweckiego05:18
  3. Tychy Aleja Bielska05:19
  4. Tychy Zachodnie05:21
  5. Tychy05:25

Next service: tomorrow 05:16 from Tychy Lodowisko · Fri 6 Nov

Next departure 05:16 tomorrow · Tychy Lodowisko
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 30 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=5
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=3
  • 100% S n=3
  • 100% S n=3

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
05:16on time on time
05:18≈ on time ≈ on time
05:19 / 05:20≈ on time ≈ on time
05:21≈ on time ≈ on time
05:25on 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
Thu 5 NovTychy 05:240 min—
Wed 4 NovTychy 05:240 min—
Tue 3 NovTychy 05:240 min—
Mon 2 NovTychy 05:240 min—
Sun 1 NovTychy 05:22No data—
Sat 31 OctTychy 05:210 min—
Fri 30 OctTychy 05:260 min—
Thu 29 OctTychy 05:260 min—
Wed 28 OctTychy 05:260 min—
Tue 27 OctTychy 05:270 min—
Mon 26 OctTychy 05:260 min—
Sun 25 OctTychy 05:21No data—
Sat 24 OctTychy 05:21No data—
Fri 23 OctTychy 05:29No data—
Thu 22 OctTychy 05:29No data—
Wed 21 OctTychy 05:29No data—
Tue 20 OctTychy 05:29No data—
Mon 19 OctTychy 05:290 min—
Sun 18 OctTychy 05:210 min—
Sat 17 OctTychy 05:210 min—
Fri 16 OctTychy 05:300 min—
Thu 15 OctTychy 05:29No data—
Wed 14 OctTychy 05:290 min—
Tue 13 OctTychy 05:290 min—
Mon 12 OctTychy 05:31+2 min+2 min
Sun 11 OctTychy 05:20−1 min—
Sat 10 OctTychy 05:210 min—
Fri 9 OctTychy 05:290 min—
Thu 8 OctTychy 05:300 min—
Wed 7 OctTychy 05:290 min—