S1 99260 Pruszków – Otwock

View line S1

Pruszków 19:29 → Otwock 20:51 Mon, Tue 1 h 22 min · 24 stops SKM Warszawa

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 19:29 from Pruszków · Tue 17 Nov

Next departure 19:29 today · Pruszków
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
89%
41/46 runs under 3 min
RT coverage: 46 full · 0 partial · 33 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: +1 min

Last 30 days

Arrival delay at Otwock, 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 10 Sept Max en route +13 min · last fix heading to Warszawa Falenica +13 min
  • Thu 29 Oct Max en route +11 min · last fix heading to Otwock +7 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Otwock +3 min
  • Sun 6 Sept Max en route +3 min · last fix heading to Otwock Świder +3 min
  • Sat 5 Sept Max en route +3 min · last fix heading to Otwock Świder +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 41
  • 3–10 min 9% · 4
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=7
  • 67% T n=6
  • 100% F n=6
  • 86% S n=7
  • 78% S n=9

Stops and timetable

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

Last 90 days, 46 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
19:29on time +2 min
19:32≈ on time ≈ +2 min
19:34 / 19:35≈ on time ≈ +2 min
19:36 / 19:37≈ on time ≈ +2 min
19:39 / 19:40≈ on time ≈ +2 min
19:44 / 19:45≈ on time ≈ +2 min
19:48 / 19:49≈ on time ≈ +2 min
19:51 / 19:53≈ on time ≈ +2 min
19:55≈ on time ≈ +2 min
19:57 / 19:58≈ on time ≈ +2 min
20:00 / 20:02≈ on time ≈ +2 min
20:06≈ on time ≈ +3 min
20:09 / 20:10≈ on time ≈ +3 min
20:13 / 20:14≈ on time ≈ +3 min
20:16 / 20:20≈ on time ≈ +3 min
20:22 / 20:23≈ on time ≈ +3 min
20:26≈ on time ≈ +3 min
20:29 / 20:30≈ on time ≈ +3 min
20:31 / 20:32≈ on time ≈ +3 min
20:35 / 20:41≈ on time ≈ +3 min
20:43≈ on time ≈ +3 min
20:45 / 20:46≈ on time ≈ +3 min
20:48≈ on time ≈ +3 min
20:51on 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
Mon 16 NovOtwock 20:520 min—
Sun 15 NovOtwock 20:480 min—
Sat 14 NovOtwock 20:480 min—
Fri 13 NovOtwock 20:530 min—
Thu 12 NovOtwock 20:520 min—
Wed 11 NovOtwock 20:480 min—
Tue 10 NovOtwock 20:520 min—
Mon 9 NovOtwock 20:520 min—
Sun 8 NovOtwock 20:49+1 min+1 min
Sat 7 NovOtwock 20:49+1 min+1 min
Fri 6 NovOtwock 20:520 min—
Thu 5 NovOtwock 20:530 min—
Wed 4 NovOtwock 20:520 min—
Tue 3 NovOtwock 20:530 min—
Mon 2 NovOtwock 20:520 min—
Sun 1 NovOtwock 20:49+3 min+3 min
Sat 31 OctOtwock 20:480 min—
Fri 30 OctOtwock 20:520 min—
Thu 29 OctOtwock 20:59+7 min+11 min
Wed 28 OctOtwock 20:520 min—
Tue 27 OctOtwock 20:520 min—
Mon 26 OctOtwock 20:530 min—
Sun 25 OctOtwock 20:48No data—
Sat 24 OctOtwock 20:48No data—
Fri 23 OctOtwock 20:53No data—
Thu 22 OctOtwock 20:52No data—
Wed 21 OctOtwock 20:52No data—
Tue 20 OctOtwock 20:52No data—
Mon 19 OctOtwock 20:52No data—
Sun 18 OctOtwock 20:480 min—