R3 19442 Warszawa Wschodnia – Sochaczew

View line R3

Warszawa Wschodnia 08:17 → Sochaczew 09:24 Sat, Sun 1 h 07 min · 19 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Sochaczew at 09:32 +8 min

  1. Warszawa Wschodnia08:17
  2. Warszawa Śródmieście08:24
  3. Warszawa Włochy08:37
  4. Ożarów Mazowiecki08:49
  5. Błonie09:00
  6. Seroki09:10
  7. Sochaczew09:24
On-time · 30 days
67%
6/9 runs under 3 min
RT coverage: 9 full · 0 partial · 2 no data
On-time · 90 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 5 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +8 min

Last 30 days

Arrival delay at Sochaczew, 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 +9 min · last fix heading to Sochaczew +9 min
  • Sun 15 Nov Max en route +8 min · last fix heading to Sochaczew +8 min
  • Sat 14 Nov Max en route +8 min · last fix heading to Sochaczew +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 15
  • 3–10 min 17% · 3
  • 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
  • 89% S n=9
  • 75% S n=8

Stops and timetable

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

Last 90 days, 18 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
08:17+1 min +3 min
08:19≈ +1 min ≈ +3 min
08:21 / 08:22≈ +1 min ≈ +3 min
08:24 / 08:26≈ +1 min ≈ +3 min
08:28 / 08:29≈ +1 min ≈ +3 min
08:32 / 08:33≈ +1 min ≈ +4 min
08:37 / 08:38≈ +1 min ≈ +4 min
08:42≈ +1 min ≈ +4 min
08:45≈ +1 min ≈ +5 min
08:49≈ +1 min ≈ +5 min
08:53 / 08:54≈ +1 min ≈ +5 min
08:57≈ +1 min ≈ +6 min
09:00≈ +1 min ≈ +6 min
09:03≈ +1 min ≈ +6 min
09:06 / 09:07≈ +1 min ≈ +7 min
09:10≈ +1 min ≈ +7 min
09:13 / 09:14≈ +1 min ≈ +7 min
09:18≈ +1 min ≈ +8 min
09:24+1 min +8 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
Sun 15 NovSochaczew 09:33+8 min+8 min
Sat 14 NovSochaczew 09:33+8 min+8 min
Wed 11 NovSochaczew 09:380 min—
Sun 8 NovSochaczew 09:24+1 min+1 min
Sat 7 NovSochaczew 09:24+1 min+1 min
Sun 1 NovSochaczew 09:48+9 min+9 min
Sat 31 OctSochaczew 09:40+2 min+2 min
Sun 25 OctSochaczew 09:38No data—
Sat 24 OctSochaczew 09:38No data—
Sun 18 OctSochaczew 09:380 min—
Sat 17 OctSochaczew 09:380 min+2 min
Sun 11 OctSochaczew 09:380 min—
Sat 10 OctSochaczew 09:380 min+2 min
Sun 4 OctSochaczew 09:380 min—
Sat 3 OctSochaczew 09:36+1 min+1 min
Sun 27 SeptSochaczew 09:36+1 min+1 min
Sat 26 SeptSochaczew 09:36+1 min+1 min
Sun 20 SeptSochaczew 09:36No data—
Sat 19 SeptSochaczew 09:36+1 min+1 min
Sun 13 SeptSochaczew 09:37+1 min+1 min
Sat 12 SeptSochaczew 09:36+1 min+1 min
Sun 6 SeptSochaczew 09:36No data—
Sat 5 SeptSochaczew 09:36No data—