S4 11248 Wieliszew → Piaseczno

View line S4

Wieliszew 10:34 → Piaseczno 11:47 Sat, Sun 1 h 13 min · 25 stops SKM Warszawa

Running now · updated 11:05

Position estimated from the timetable

Between Warszawa Praga and Warszawa ZOO 0 min

Estimated arrival at Piaseczno 11:47 · 4 km/h

  1. Wieliszew10:34
  2. Warszawa Choszczówka10:49
  3. Warszawa Praga11:01
  4. Warszawa ZOO11:04
  5. Warszawa Koło11:12
  6. Warszawa Aleje Jerozolimskie11:25
  7. Piaseczno11:47

Today it is running no worse than usual: typical arrival delay is 0 min; 75% of the last 8 runs arrived on time.

On-time · 30 days
75%
6/8 runs under 3 min
RT coverage: 7 full · 1 partial · 2 no data
On-time · 90 days
85%
11/13 runs under 3 min
RT coverage: 12 full · 1 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Piaseczno, 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 1 Nov Max en route +4 min · last fix heading to Piaseczno +4 min
  • Sat 14 Nov Max en route +3 min · last fix heading to Piaseczno +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 11
  • 3–10 min 15% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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 10Today
10:34on time +1 minPassed
10:36 / 10:37≈ on time ≈ +1 minPassed
10:39≈ on time ≈ +1 minPassed
10:42 / 10:45≈ on time ≈ +1 minPassed
10:49 / 10:50≈ on time ≈ +1 minPassed
10:52 / 10:53≈ on time ≈ +1 minPassed
10:55 / 10:56≈ on time ≈ +1 minPassed
10:58 / 10:59≈ on time ≈ +1 minPassed
11:01≈ on time ≈ +1 minPassed
11:04 / 11:05≈ on time ≈ +1 minNext
11:07 / 11:08≈ on time ≈ +1 min
11:10≈ on time ≈ +1 min
11:12 / 11:13≈ on time ≈ +2 min
11:14 / 11:15≈ on time ≈ +2 min
11:16 / 11:17≈ on time ≈ +2 min
11:19 / 11:21≈ on time ≈ +2 min
11:25≈ on time ≈ +2 min
11:28≈ on time ≈ +2 min
11:30≈ on time ≈ +2 min
11:32 / 11:33≈ on time ≈ +2 min
11:35≈ on time ≈ +2 min
11:38 / 11:39≈ on time ≈ +2 min
11:41≈ on time ≈ +3 min
11:43 / 11:44≈ on time ≈ +3 min
11:47on time +3 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
Sat 21 NovWarszawa Praga 10:59Partial coverage0 min—
Sun 15 NovPiaseczno 11:49+1 min+1 min
Sat 14 NovPiaseczno 11:49+3 min+3 min
Wed 11 NovPiaseczno 11:480 min—
Sun 8 NovPiaseczno 11:490 min—
Sat 7 NovPiaseczno 11:480 min—
Sun 1 NovPiaseczno 11:52+4 min+4 min
Sat 31 OctPiaseczno 11:480 min—
Sun 25 OctPiaseczno 11:48No data—
Sat 24 OctPiaseczno 11:48No data—
Sun 18 OctPiaseczno 11:49+1 min+1 min
Sat 17 OctPiaseczno 11:480 min—
Sun 11 OctPiaseczno 11:480 min—
Sat 10 OctPiaseczno 11:480 min—
Sun 4 OctPiaseczno 11:480 min—
Sat 3 OctPiaseczno 11:46No data—