S4 99450 Piaseczno → Wieliszew

View line S4

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

S4 99450/1 Piaseczno–Wieliszew: final delay under 3 min on 8 of its 8 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 14:48 (GMT+1).

✓ Today’s run finished

Today it reached Wieliszew at 13:21 0 min

  1. Piaseczno12:11
  2. Warszawa Okęcie12:22
  3. Warszawa Aleje Jerozolimskie12:32
  4. Warszawa Koło12:42
  5. Warszawa Praga12:54
  6. Warszawa Choszczówka13:06
  7. Wieliszew13:21

Next service: tomorrow 12:11 from Piaseczno · Sun 22 Nov

Next departure 12:11 tomorrow · Piaseczno
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 2 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 3 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: +1 min

Last 30 days

Arrival delay at Wieliszew, 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

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

  • Early 0% · 0
  • On time 100% · 13
  • 3–10 min 0% · 0
  • 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
  • 100% S n=6
  • 100% 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 10
12:11on time on time
12:14≈ on time ≈ on time
12:16 / 12:17≈ on time ≈ on time
12:19≈ on time ≈ on time
12:22 / 12:23≈ on time ≈ on time
12:25≈ on time ≈ on time
12:27 / 12:28≈ on time ≈ on time
12:29 / 12:30≈ on time ≈ on time
12:32≈ on time ≈ on time
12:36 / 12:37≈ on time ≈ on time
12:39≈ on time ≈ on time
12:41≈ on time ≈ on time
12:42 / 12:43≈ on time ≈ on time
12:45≈ on time ≈ on time
12:48 / 12:49≈ on time ≈ on time
12:51≈ on time ≈ on time
12:54 / 12:55≈ on time ≈ on time
12:57≈ on time ≈ on time
13:00≈ on time ≈ on time
13:03≈ on time ≈ on time
13:06≈ on time ≈ on time
13:11 / 13:14≈ on time ≈ on time
13:16≈ on time ≈ on time
13:18 / 13:19≈ on time ≈ on time
13:21on 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 21 NovWieliszew 13:230 min—
Sun 15 NovWieliszew 13:230 min—
Sat 14 NovWieliszew 13:230 min—
Wed 11 NovWieliszew 13:230 min—
Sun 8 NovWieliszew 13:230 min—
Sat 7 NovWieliszew 13:230 min—
Sun 1 NovWieliszew 13:26+3 min+3 min
Sat 31 OctWieliszew 13:230 min—
Sun 25 OctWieliszew 13:23No data—
Sat 24 OctWieliszew 13:23No data—
Sun 18 OctWieliszew 13:230 min—
Sat 17 OctWieliszew 13:230 min+1 min
Sun 11 OctWieliszew 13:230 min—
Sat 10 OctWieliszew 13:230 min—
Sun 4 OctWieliszew 13:230 min—
Sat 3 OctWieliszew 13:21No data—