RL 97110 Warszawa Lotnisko Chopina – Modlin

View line RL

Warszawa Lotnisko Chopina 05:41 → Modlin 06:48 Wed 1 h 07 min · 16 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Modlin at 06:48 0 min

  1. Warszawa Lotnisko Chopina05:41
  2. Warszawa Rakowiec05:49
  3. Warszawa Zachodnia05:57
  4. Warszawa Targówek06:17
  5. Warszawa Płudy06:26
  6. Chotomów06:37
  7. Modlin06:48
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%
34/41 runs under 3 min
RT coverage: 41 full · 0 partial · 31 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: +2 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

  • Sun 6 Sept Max en route +17 min · last fix heading to Legionowo +17 min
  • Sat 5 Sept Max en route +17 min · last fix heading to Legionowo +17 min
  • Sun 8 Nov Max en route +14 min · last fix heading to Modlin +14 min
  • Mon 28 Sept Max en route +5 min · last fix heading to Nowy Dwór Mazowiecki +5 min
  • Fri 25 Sept Max en route +5 min · last fix heading to Nowy Dwór Mazowiecki +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 34
  • 3–10 min 10% · 4
  • 10–30 min 7% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=6
  • 100% W n=6
  • 83% T n=6
  • 83% F n=6
  • 80% S n=5
  • 40% S n=5

Stops and timetable

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

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