S8 40427 Chorzów Batory – Lubliniec

View line S8

Chorzów Batory 17:15 → Lubliniec 18:17 Mon, Tue, Wed, Thu, Fri 1 h 02 min · 16 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Lubliniec at 18:23 +6 min

  1. Chorzów Batory17:15
  2. Chorzów Stary17:23
  3. Bytom Karb17:30
  4. Radzionków17:39
  5. Tarnowskie Góry17:46
  6. Koszęcin18:06
  7. Lubliniec18:17

Next service: Monday 17:15 from Chorzów Batory · Mon 16 Nov

Next departure 17:15 Monday · Chorzów Batory
On-time · 30 days
75%
12/16 runs under 3 min
RT coverage: 16 full · 0 partial · 5 no data
On-time · 90 days
76%
26/34 runs under 3 min
RT coverage: 34 full · 0 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +8 min

Last 30 days

Arrival delay at Lubliniec, in minutes. One bar per run.

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

Worst days

  • Fri 30 Oct Max en route +14 min · last fix heading to Lubliniec +14 min
  • Fri 6 Nov Max en route +9 min · last fix heading to Lubliniec +9 min
  • Fri 13 Nov Max en route +6 min · last fix heading to Lubliniec +6 min
  • Tue 27 Oct Max en route +4 min · last fix heading to Lubliniec +4 min
  • Thu 10 Sept Max en route +4 min · last fix heading to Lubliniec +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 26
  • 3–10 min 21% · 7
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 86% T n=7
  • 86% W n=7
  • 71% T n=7
  • 43% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 34 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
17:15on time +4 min
17:17 / 17:18≈ on time ≈ +4 min
17:19 / 17:20≈ on time ≈ +4 min
17:23≈ on time ≈ +4 min
17:27 / 17:28≈ on time ≈ +4 min
17:30 / 17:31≈ on time ≈ +4 min
17:34≈ on time ≈ +4 min
17:36 / 17:37≈ on time ≈ +4 min
17:39≈ on time ≈ +4 min
17:42≈ on time ≈ +4 min
17:46 / 17:48≈ on time ≈ +4 min
17:53 / 17:54≈ on time ≈ +4 min
18:00 / 18:01≈ on time ≈ +4 min
18:06 / 18:07≈ on time ≈ +4 min
18:11≈ on time ≈ +4 min
18:17on time +4 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 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 NovLubliniec 18:24+6 min+6 min
Thu 12 NovLubliniec 18:19+1 min+1 min
Tue 10 NovLubliniec 18:180 min—
Mon 9 NovLubliniec 18:180 min—
Fri 6 NovLubliniec 18:27+9 min+9 min
Thu 5 NovLubliniec 18:19+1 min+1 min
Wed 4 NovLubliniec 18:180 min—
Tue 3 NovLubliniec 18:20+2 min+2 min
Mon 2 NovLubliniec 18:19+2 min+2 min
Fri 30 OctLubliniec 18:32+14 min+14 min
Thu 29 OctLubliniec 18:190 min—
Wed 28 OctLubliniec 18:180 min—
Tue 27 OctLubliniec 18:22+4 min+4 min
Mon 26 OctLubliniec 18:190 min—
Fri 23 OctLubliniec 18:19No data—
Thu 22 OctLubliniec 18:19No data—
Wed 21 OctLubliniec 18:18No data—
Tue 20 OctLubliniec 18:18No data—
Mon 19 OctLubliniec 18:18No data—
Fri 16 OctLubliniec 18:180 min—
Thu 15 OctLubliniec 18:17−1 min—
Wed 14 OctLubliniec 18:180 min—
Tue 13 OctLubliniec 18:180 min—
Mon 12 OctLubliniec 18:180 min—
Fri 9 OctLubliniec 18:180 min—
Thu 8 OctLubliniec 18:190 min—
Wed 7 OctLubliniec 18:180 min—
Tue 6 OctLubliniec 18:180 min—
Mon 5 OctLubliniec 18:180 min—
Fri 2 OctLubliniec 18:16No data—