R90 15435 Warszawa Zachodnia (Peron 9) – Działdowo

View line R90

Warszawa Zachodnia (Peron 9) 19:17 → Działdowo 21:45 Sat 2 h 28 min · 40 stops Koleje Mazowieckie

Running now · updated 20:29

Position estimated from the timetable

Between Jackowo Dworskie and Świercze 0 min

Estimated arrival at Działdowo 21:45 · 113 km/h

  1. Warszawa Zachodnia (Peron 9)19:17
  2. Warszawa Praga19:34
  3. Legionowo Przystanek19:52
  4. Studzianki Nowe20:16
  5. Jackowo Dworskie20:26
  6. Świercze20:30
  7. Działdowo21:45
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 3 full · 1 partial · 1 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 6 full · 1 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Działdowo, in minutes. One bar per run.

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

Worst days

  • Sat 19 Sept Max en route +6 min · last fix heading to Działdowo +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 6
  • 3–10 min 14% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 86% S n=7
  • — S n=0

Stops and timetable

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

Last 90 days, 7 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 10Today
19:17on time +2 minPassed
19:18 / 19:19≈ on time ≈ +3 minPassed
19:20 / 19:21≈ on time ≈ +3 minPassed
19:22 / 19:23≈ on time ≈ +3 minPassed
19:25≈ on time ≈ +3 minPassed
19:28 / 19:29≈ on time ≈ +3 minPassed
19:31≈ on time ≈ +3 minPassed
19:34 / 19:35≈ on time ≈ +3 minPassed
19:37≈ on time ≈ +3 minPassed
19:39 / 19:40≈ on time ≈ +3 minPassed
19:42≈ on time ≈ +3 minPassed
19:44 / 19:45≈ on time ≈ +3 minPassed
19:49 / 19:50≈ on time ≈ +3 minPassed
19:52≈ on time ≈ +3 minPassed
19:54 / 19:55≈ on time ≈ +3 minPassed
19:59 / 20:00≈ on time ≈ +3 minPassed
20:03≈ on time ≈ +3 minPassed
20:06 / 20:07≈ on time ≈ +3 minPassed
20:10≈ on time ≈ +3 minPassed
20:13 / 20:14≈ on time ≈ +3 minPassed
20:16≈ on time ≈ +3 minPassed
20:19 / 20:20≈ on time ≈ +3 minPassed
20:23 / 20:24≈ on time ≈ +3 minPassed
20:26 / 20:27≈ on time ≈ +3 minPassed
20:30≈ on time ≈ +3 minNext
20:33 / 20:34≈ on time ≈ +3 min
20:37≈ on time ≈ +3 min
20:41≈ on time ≈ +3 min
20:47≈ on time ≈ +3 min
20:49 / 20:50≈ on time ≈ +3 min
20:55 / 20:56≈ on time ≈ +3 min
20:58 / 20:59≈ on time ≈ +3 min
21:02 / 21:10≈ on time ≈ +3 min
21:12 / 21:13≈ on time ≈ +3 min
21:16 / 21:17≈ on time ≈ +3 min
21:20 / 21:21≈ on time ≈ +3 min
21:23 / 21:31≈ on time ≈ +3 min
21:35≈ on time ≈ +3 min
21:38≈ on time ≈ +3 min
21:45on 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
Sat 14 NovŚwiercze 20:29Partial coverage0 min—
Sat 7 NovDziałdowo 21:440 min—
Sat 31 OctDziałdowo 21:470 min—
Sat 24 OctDziałdowo 21:47No data—
Sat 17 OctDziałdowo 21:460 min—
Sat 10 OctDziałdowo 21:460 min—
Sat 3 OctDziałdowo 21:440 min—
Sat 26 SeptDziałdowo 21:44No data—
Sat 19 SeptDziałdowo 21:44+6 min+6 min
Sat 12 SeptDziałdowo 21:45No data—
Sat 5 SeptDziałdowo 21:44No data—