R90 15423 Warszawa Zachodnia (Peron 9) – Działdowo
Alerts for train 15423
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line R90.
Running now · updated 09:57
Position estimated from the timetable
Between Czeruchy and Krośnice Mazowieckie 0 min
Estimated arrival at Działdowo 10:44 · 85 km/h
- Warszawa Zachodnia (Peron 9)08:13
- Warszawa Praga08:34
- Legionowo Przystanek08:52
- Studzianki Nowe09:16
- Czeruchy09:55
- Krośnice Mazowieckie09:58
- Działdowo10:44
Today it is running no worse than usual: typical arrival delay is 0 min; 75% of the last 24 runs arrived on time.
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
- Fri 11 Sept Max en route +91 min · last fix heading to Brody Warszawskie +91 min
- Mon 26 Oct Max en route +33 min · last fix heading to Działdowo +33 min
- Tue 27 Oct Max en route +22 min · last fix heading to Działdowo +22 min
- Mon 12 Oct Max en route +11 min · last fix heading to Działdowo +11 min
- Tue 13 Oct Max en route +9 min · last fix heading to Działdowo +9 min
Distribution · 90 days
49 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 59% · 29
- 3–10 min 33% · 16
- 10–30 min 4% · 2
- 30+ min 4% · 2
On-time by weekday
- 57% M n=7
- 50% T n=6
- 63% W n=8
- 56% T n=9
- 71% F n=7
- 50% S n=6
- 67% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (40 stops).
Last 90 days, 49 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.
| Stop | Sched. | Usually | 9 days in 10 | Today |
|---|---|---|---|---|
| 08:13 | on time | +6 min | Passed | |
| 08:15 | ≈ on time | ≈ +6 min | Passed | |
| 08:17 / 08:18 | ≈ on time | ≈ +6 min | Passed | |
| 08:19 / 08:20 | ≈ on time | ≈ +6 min | Passed | |
| 08:22 | ≈ on time | ≈ +6 min | Passed | |
| 08:25 / 08:29 | ≈ on time | ≈ +6 min | Passed | |
| 08:31 | ≈ on time | ≈ +6 min | Passed | |
| 08:34 / 08:35 | ≈ on time | ≈ +6 min | Passed | |
| 08:37 | ≈ on time | ≈ +6 min | Passed | |
| 08:39 / 08:40 | ≈ on time | ≈ +6 min | Passed | |
| 08:42 | ≈ on time | ≈ +6 min | Passed | |
| 08:44 / 08:45 | ≈ on time | ≈ +6 min | Passed | |
| 08:49 / 08:50 | ≈ on time | ≈ +6 min | Passed | |
| 08:52 | ≈ +1 min | ≈ +6 min | Passed | |
| 08:54 / 08:55 | ≈ +1 min | ≈ +6 min | Passed | |
| 08:59 / 09:00 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:03 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:06 / 09:07 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:10 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:13 / 09:14 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:16 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:19 / 09:20 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:23 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:26 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:29 / 09:30 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:33 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:36 / 09:37 | ≈ +1 min | ≈ +6 min | Passed | |
| 09:40 / 09:41 | ≈ +1 min | ≈ +7 min | Passed | |
| 09:46 / 09:47 | ≈ +1 min | ≈ +7 min | Passed | |
| 09:49 / 09:50 | ≈ +1 min | ≈ +7 min | Passed | |
| 09:55 / 09:56 | ≈ +1 min | ≈ +7 min | Passed | |
| 09:58 / 09:59 | ≈ +1 min | ≈ +7 min | ||
| 10:02 / 10:10 | ≈ +1 min | ≈ +7 min | ||
| 10:12 | ≈ +1 min | ≈ +7 min | ||
| 10:16 | ≈ +1 min | ≈ +8 min | ||
| 10:20 | ≈ +1 min | ≈ +8 min | ||
| 10:22 / 10:30 | ≈ +1 min | ≈ +8 min | ||
| 10:34 | ≈ +1 min | ≈ +8 min | ||
| 10:37 | ≈ +1 min | ≈ +8 min | ||
| 10:44 | +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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 15 Nov | Czeruchy 09:54Partial coverage | 0 min | — |
| Sat 14 Nov | Działdowo 10:58 | +3 min | +3 min |
| Fri 13 Nov | Działdowo 10:44 | 0 min | — |
| Thu 12 Nov | Działdowo 10:44 | 0 min | — |
| Wed 11 Nov | Działdowo 10:54 | 0 min | — |
| Tue 10 Nov | Działdowo 10:44 | 0 min | — |
| Mon 9 Nov | Działdowo 10:45 | 0 min | — |
| Sun 8 Nov | Działdowo 10:45 | 0 min | — |
| Sat 7 Nov | Działdowo 11:03 | +8 min | +8 min |
| Fri 6 Nov | Działdowo 10:44 | +1 min | +1 min |
| Thu 5 Nov | Działdowo 10:44 | 0 min | — |
| Wed 4 Nov | Działdowo 10:44 | 0 min | — |
| Tue 3 Nov | Działdowo 10:44 | 0 min | — |
| Mon 2 Nov | Działdowo 10:44 | 0 min | — |
| Sun 1 Nov | Działdowo 10:52 | +7 min | +7 min |
| Sat 31 Oct | Działdowo 10:55 | 0 min | — |
| Fri 30 Oct | Działdowo 10:45 | 0 min | — |
| Thu 29 Oct | Działdowo 10:45 | 0 min | — |
| Wed 28 Oct | Działdowo 10:50 | +5 min | +5 min |
| Tue 27 Oct | Działdowo 11:07 | +22 min | +22 min |
| Mon 26 Oct | Działdowo 11:14 | +33 min | +33 min |
| Sun 25 Oct | Działdowo 10:45 | No data | — |
| Sat 24 Oct | Działdowo 10:56 | No data | — |
| Fri 23 Oct | Działdowo 10:46 | No data | — |
| Thu 22 Oct | Działdowo 10:46 | No data | — |
| Wed 21 Oct | Działdowo 10:46 | No data | — |
| Tue 20 Oct | Działdowo 10:46 | No data | — |
| Mon 19 Oct | Działdowo 10:46 | 0 min | — |
| Sun 18 Oct | Działdowo 10:47 | +1 min | +1 min |
| Sat 17 Oct | Działdowo 10:56 | 0 min | — |