RL 97155 Warszawa Zachodnia – Modlin

View line RL

Warszawa Zachodnia 05:00 → Modlin 05:48 Daily 0 h 48 min · 11 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Modlin at 05:48 0 min

  1. Warszawa Zachodnia05:00
  2. Warszawa Wschodnia05:11
  3. Warszawa Targówek05:17
  4. Warszawa Płudy05:26
  5. Legionowo Przystanek05:35
  6. Chotomów05:37
  7. Modlin05:48

Next service: tomorrow 05:00 from Warszawa Zachodnia · Thu 12 Nov

Next departure 05:00 tomorrow · Warszawa Zachodnia
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
83%
33/40 runs under 3 min
RT coverage: 40 full · 0 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Modlin, 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 +38 min · last fix heading to Modlin +38 min
  • Mon 12 Oct Max en route +36 min · last fix heading to Modlin +36 min
  • Wed 30 Sept Max en route +9 min · last fix heading to Nowy Dwór Mazowiecki +7 min
  • Sun 1 Nov Max en route +6 min · last fix heading to Modlin +6 min
  • Fri 2 Oct Max en route +5 min · last fix heading to Nowy Dwór Mazowiecki +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 33
  • 3–10 min 13% · 5
  • 10–30 min 0% · 0
  • 30+ min 5% · 2

On-time by weekday

  • 83% M n=6
  • 83% T n=6
  • 86% W n=7
  • 83% T n=6
  • 71% F n=7
  • 100% S n=4
  • 75% S n=4

Stops and timetable

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

Last 90 days, 40 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
05:00on time +4 min
05:04 / 05:05≈ on time ≈ +4 min
05:11 / 05:14≈ on time ≈ +5 min
05:17≈ on time ≈ +5 min
05:22 / 05:23≈ on time ≈ +5 min
05:26 / 05:27≈ on time ≈ +5 min
05:32 / 05:33≈ on time ≈ +5 min
05:35≈ on time ≈ +5 min
05:37 / 05:38≈ on time ≈ +5 min
05:44 / 05:45≈ on time ≈ +5 min
05:48on time +5 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 11 NovModlin 05:490 min—
Tue 10 NovModlin 05:490 min—
Mon 9 NovModlin 05:490 min—
Sun 8 NovModlin 05:490 min—
Sat 7 NovModlin 05:490 min—
Fri 6 NovModlin 05:490 min—
Thu 5 NovModlin 05:490 min—
Wed 4 NovModlin 05:490 min—
Tue 3 NovModlin 05:490 min—
Mon 2 NovModlin 05:490 min—
Sun 1 NovModlin 05:55+6 min+6 min
Sat 31 OctModlin 05:490 min—
Fri 30 OctModlin 05:490 min—
Thu 29 OctModlin 05:490 min—
Wed 28 OctModlin 05:490 min—
Tue 27 OctModlin 05:500 min—
Mon 26 OctModlin 05:490 min—
Sun 25 OctModlin 05:49No data—
Sat 24 OctModlin 05:49No data—
Fri 23 OctModlin 05:49No data—
Thu 22 OctModlin 05:49No data—
Wed 21 OctModlin 05:49No data—
Tue 20 OctModlin 05:49No data—
Mon 19 OctModlin 05:490 min—
Sun 18 OctModlin 05:490 min—
Sat 17 OctModlin 05:490 min—
Fri 16 OctModlin 05:500 min—
Thu 15 OctModlin 05:490 min—
Wed 14 OctModlin 05:50+1 min+1 min
Tue 13 OctModlin 06:27+38 min+38 min