S40 98220 Piaseczno – Radzymin

View line S40

Piaseczno 20:11 → Radzymin 21:34 Mon, Tue, Wed, Thu, Fri 1 h 23 min · 28 stops PKP

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 20:11 from Piaseczno · Thu 5 Nov

Next departure 20:11 today · Piaseczno
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 5 no data
On-time · 90 days
74%
14/19 runs under 3 min
RT coverage: 19 full · 0 partial · 6 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+54min
9 in 10 runs arrive with less than this
30 days: +28 min

Last 30 days

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

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

Worst days

  • Thu 8 Oct Max en route +54 min · last fix heading to Radzymin +54 min
  • Wed 7 Oct Max en route +54 min · last fix heading to Radzymin +54 min
  • Tue 6 Oct Max en route +54 min · last fix heading to Radzymin +54 min
  • Mon 5 Oct Max en route +53 min · last fix heading to Radzymin +53 min
  • Fri 2 Oct Max en route +3 min · last fix heading to Radzymin +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 74% · 14
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 21% · 4

On-time by weekday

  • 75% M n=4
  • 75% T n=4
  • 75% W n=4
  • 67% T n=3
  • 75% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 19 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
20:11on time +54 min
20:14≈ on time ≈ +54 min
20:16 / 20:17≈ on time ≈ +54 min
20:19≈ on time ≈ +54 min
20:22 / 20:23≈ on time ≈ +54 min
20:25≈ on time ≈ +54 min
20:27 / 20:28≈ on time ≈ +54 min
20:29 / 20:30≈ on time ≈ +54 min
20:32≈ on time ≈ +54 min
20:36 / 20:37≈ on time ≈ +54 min
20:39≈ on time ≈ +54 min
20:41≈ on time ≈ +54 min
20:42 / 20:43≈ on time ≈ +54 min
20:45≈ on time ≈ +54 min
20:48 / 20:49≈ on time ≈ +54 min
20:51≈ on time ≈ +54 min
20:54 / 20:55≈ +1 min ≈ +54 min
20:57≈ +1 min ≈ +54 min
21:00≈ +1 min ≈ +54 min
21:03≈ +1 min ≈ +54 min
21:06≈ +1 min ≈ +54 min
21:11 / 21:14≈ +1 min ≈ +54 min
21:16≈ +1 min ≈ +54 min
21:18 / 21:19≈ +1 min ≈ +54 min
21:21 / 21:22≈ +1 min ≈ +54 min
21:25≈ +1 min ≈ +54 min
21:28 / 21:29≈ +1 min ≈ +54 min
21:34+1 min +54 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
Wed 4 NovRadzymin 21:340 min—
Tue 3 NovRadzymin 21:340 min—
Mon 2 NovRadzymin 21:340 min—
Fri 30 OctRadzymin 21:37+2 min+2 min
Thu 29 OctRadzymin 21:36+1 min+1 min
Wed 28 OctRadzymin 21:36+1 min+1 min
Tue 27 OctRadzymin 21:350 min—
Mon 26 OctRadzymin 21:360 min—
Fri 23 OctRadzymin 21:36No data—
Thu 22 OctRadzymin 21:35No data—
Wed 21 OctRadzymin 21:35No data—
Tue 20 OctRadzymin 21:35No data—
Mon 19 OctRadzymin 21:35No data—
Fri 16 OctRadzymin 21:350 min—
Thu 15 OctRadzymin 21:360 min—
Wed 14 OctRadzymin 21:350 min—
Tue 13 OctRadzymin 21:37+2 min+2 min
Mon 12 OctRadzymin 21:350 min—
Fri 9 OctRadzymin 21:36+1 min+1 min
Thu 8 OctRadzymin 22:29+54 min+54 min
Wed 7 OctRadzymin 22:29+54 min+54 min
Tue 6 OctRadzymin 22:29+54 min+54 min
Mon 5 OctRadzymin 22:28+53 min+53 min
Fri 2 OctRadzymin 21:34+3 min+3 min
Thu 1 OctRadzymin 21:33No data—