S1 40113 Częstochowa → Gliwice

View line S1

Częstochowa 21:55 → Gliwice 23:49 Sat, Sun 1 h 54 min · 22 stops Koleje Śląskie

S1 40113 Jura Częstochowa–Gliwice: final delay under 3 min on 6 of its 9 runs with data in the last 30 days (67%). Median final delay: +1 min. TrainsRadar data as of 23 Nov 2026, 00:01 (GMT+1).

It does not run today

Last recorded run: Sunday 22 November +1 min

Next service: Saturday 21:55 from Częstochowa · Sat 28 Nov

Next departure 21:55 Saturday · Częstochowa
On-time · 30 days
67%
6/9 runs under 3 min
RT coverage: 9 full · 0 partial · 1 no data
On-time · 90 days
80%
12/15 runs under 3 min
RT coverage: 15 full · 0 partial · 6 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+28min
9 in 10 runs arrive with less than this
30 days: +42 min

Last 30 days

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

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

Worst days

  • Sun 15 Nov Max en route +42 min · last fix heading to Gliwice +42 min
  • Sat 14 Nov Max en route +42 min · last fix heading to Gliwice +42 min
  • Sun 1 Nov Max en route +8 min · last fix heading to Gliwice +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 12
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 13% · 2

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=1
  • — T n=0
  • — F n=0
  • 83% S n=6
  • 75% S n=8

Stops and timetable

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

Last 90 days, 15 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
21:55on time +16 min
21:59 / 22:00≈ on time ≈ +16 min
22:06 / 22:07≈ on time ≈ +17 min
22:14≈ on time ≈ +18 min
22:21 / 22:22≈ on time ≈ +19 min
22:27≈ on time ≈ +19 min
22:35 / 22:36≈ on time ≈ +20 min
22:39≈ on time ≈ +21 min
22:42 / 22:43≈ on time ≈ +21 min
22:45≈ on time ≈ +21 min
22:48≈ on time ≈ +22 min
22:55 / 22:58≈ +1 min ≈ +22 min
23:04≈ +1 min ≈ +23 min
23:07 / 23:08≈ +1 min ≈ +24 min
23:15 / 23:22≈ +1 min ≈ +25 min
23:25≈ +1 min ≈ +26 min
23:29 / 23:30≈ +1 min ≈ +26 min
23:32≈ +1 min ≈ +27 min
23:35 / 23:36≈ +1 min ≈ +27 min
23:38≈ +1 min ≈ +27 min
23:42 / 23:43≈ +1 min ≈ +28 min
23:49+1 min +28 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
Sun 22 NovGliwice 23:49+1 min+1 min
Sat 21 NovGliwice 23:52+2 min+2 min
Sun 15 NovGliwice 00:32+42 min+42 min
Sat 14 NovGliwice 00:32+42 min+42 min
Wed 11 NovGliwice 23:490 min—
Sun 8 NovGliwice 23:490 min—
Sat 7 NovGliwice 23:490 min—
Sun 1 NovGliwice 23:58+8 min+8 min
Sat 31 OctGliwice 23:52+1 min+1 min
Sun 25 OctGliwice 23:50No data—
Sat 24 OctGliwice 23:50No data—
Sun 18 OctGliwice 23:510 min—
Sat 17 OctGliwice 23:500 min—
Sun 11 OctGliwice 23:52+2 min+2 min
Sat 10 OctGliwice 23:50No data—
Sun 4 OctGliwice 23:510 min—
Sat 3 OctGliwice 23:500 min—
Sun 27 SeptGliwice 23:48No data—
Sat 26 SeptGliwice 23:48No data—
Sun 20 SeptGliwice 23:48+2 min+2 min
Sat 19 SeptGliwice 23:48No data—