S4 94416 Tychy Lodowisko – Tychy

View line S4

Tychy Lodowisko 07:57 → Tychy 08:06 Daily 0 h 09 min · 5 stops Koleje Śląskie

✓ Today’s run finished

Today, last fix heading to Tychy at 08:07 No data

  1. Tychy Lodowisko07:57
  2. Tychy Grota Roweckiego07:59
  3. Tychy Aleja Bielska08:00
  4. Tychy Zachodnie08:02
  5. Tychy08:06

Next service: tomorrow 07:57 from Tychy Lodowisko · Sun 8 Nov

Next departure 07:57 tomorrow · Tychy Lodowisko
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 10 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 41 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
07:57on time on time
07:59≈ on time ≈ on time
08:00 / 08:01≈ on time ≈ on time
08:02≈ on time ≈ on time
08:06on 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
Sat 7 NovTychy 08:07No data—
Fri 6 NovTychy 07:590 min—
Thu 5 NovTychy 07:590 min—
Wed 4 NovTychy 07:590 min—
Tue 3 NovTychy 07:590 min—
Mon 2 NovTychy 07:590 min—
Sun 1 NovTychy 08:08No data—
Sat 31 OctTychy 08:070 min—
Fri 30 OctTychy 08:00No data—
Thu 29 OctTychy 08:00No data—
Wed 28 OctTychy 08:000 min—
Tue 27 OctTychy 08:000 min—
Mon 26 OctTychy 08:000 min—
Sun 25 OctTychy 08:07No data—
Sat 24 OctTychy 08:09No data—
Fri 23 OctTychy 08:02No data—
Thu 22 OctTychy 08:02No data—
Wed 21 OctTychy 08:02No data—
Tue 20 OctTychy 08:02No data—
Mon 19 OctTychy 08:020 min—
Sun 18 OctTychy 08:090 min—
Sat 17 OctTychy 08:090 min—
Fri 16 OctTychy 08:020 min—
Thu 15 OctTychy 08:01−1 min—
Wed 14 OctTychy 08:020 min—
Tue 13 OctTychy 08:020 min—
Mon 12 OctTychy 08:030 min—
Sun 11 OctTychy 08:090 min—
Sat 10 OctTychy 08:090 min—
Fri 9 OctTychy 08:020 min—