S1 99252 Pruszków – Otwock

View line S1

Pruszków 17:29 → Otwock 18:40 Mon, Tue, Wed, Thu 1 h 11 min · 24 stops PKP

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 17:29 from Pruszków · Thu 5 Nov

Next departure 17:29 today · Pruszków
On-time · 30 days
68%
15/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
81%
29/36 runs under 3 min
RT coverage: 36 full · 0 partial · 31 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +9 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

  • Tue 13 Oct Max en route +13 min · last fix heading to Otwock +13 min
  • Mon 12 Oct Max en route +12 min · last fix heading to Otwock +12 min
  • Tue 3 Nov Max en route +9 min · last fix heading to Otwock +9 min
  • Mon 2 Nov Max en route +9 min · last fix heading to Otwock +9 min
  • Wed 28 Oct Max en route +4 min · last fix heading to Otwock +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 29
  • 3–10 min 14% · 5
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 57% T n=7
  • 83% W n=6
  • 100% T n=4
  • 100% F n=3
  • 100% S n=3
  • 80% S n=5

Stops and timetable

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

Last 90 days, 36 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
17:29+1 min +3 min
17:32≈ +1 min ≈ +3 min
17:34 / 17:35≈ +1 min ≈ +3 min
17:36 / 17:37≈ +1 min ≈ +3 min
17:39 / 17:40≈ +1 min ≈ +3 min
17:44 / 17:46≈ +1 min ≈ +3 min
17:48 / 17:49≈ +1 min ≈ +3 min
17:52 / 17:53≈ +1 min ≈ +3 min
17:55 / 17:56≈ +1 min ≈ +4 min
17:58≈ +1 min ≈ +4 min
18:01 / 18:02≈ +1 min ≈ +4 min
18:05≈ +1 min ≈ +4 min
18:07 / 18:08≈ +1 min ≈ +4 min
18:10≈ +1 min ≈ +5 min
18:13 / 18:15≈ +1 min ≈ +5 min
18:17≈ +1 min ≈ +5 min
18:19 / 18:20≈ +1 min ≈ +5 min
18:23≈ +1 min ≈ +5 min
18:25≈ +1 min ≈ +6 min
18:28 / 18:30≈ +1 min ≈ +6 min
18:32≈ +1 min ≈ +6 min
18:34 / 18:35≈ +1 min ≈ +6 min
18:37 / 18:38≈ +1 min ≈ +6 min
18:40+1 min +7 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 NovOtwock 18:390 min—
Tue 3 NovOtwock 18:50+9 min+9 min
Mon 2 NovOtwock 18:49+9 min+9 min
Sun 1 NovOtwock 18:48+3 min+3 min
Sat 31 OctOtwock 18:450 min—
Fri 30 OctOtwock 18:43+1 min+1 min
Thu 29 OctOtwock 18:43+1 min+1 min
Wed 28 OctOtwock 18:46+4 min+4 min
Tue 27 OctOtwock 18:45+3 min+3 min
Mon 26 OctOtwock 18:44+2 min+2 min
Sun 25 OctOtwock 18:45No data—
Sat 24 OctOtwock 18:45No data—
Fri 23 OctOtwock 18:42No data—
Thu 22 OctOtwock 18:42No data—
Wed 21 OctOtwock 18:42No data—
Tue 20 OctOtwock 18:42No data—
Mon 19 OctOtwock 18:42No data—
Sun 18 OctOtwock 18:450 min—
Sat 17 OctOtwock 18:450 min—
Fri 16 OctOtwock 18:44+2 min+2 min
Thu 15 OctOtwock 18:44+2 min+2 min
Wed 14 OctOtwock 18:43+1 min+1 min
Tue 13 OctOtwock 18:55+13 min+13 min
Mon 12 OctOtwock 18:54+12 min+12 min
Sun 11 OctOtwock 18:450 min—
Sat 10 OctOtwock 18:450 min—
Fri 9 OctOtwock 18:420 min—
Thu 8 OctOtwock 18:420 min—
Wed 7 OctOtwock 18:420 min—
Tue 6 OctOtwock 18:420 min—