RE1 21308 Dęblin – Grodzisk Mazowiecki

View line RE1

Dęblin 16:06 → Grodzisk Mazowiecki 18:56 Mon, Tue, Thu, Fri 2 h 50 min · 47 stops Koleje Mazowieckie

Running now · updated 18:08

Position estimated from the timetable

Between Warszawa Olszynka Grochowska and Warszawa Grochów +4 min

Estimated arrival at Grodzisk Mazowiecki 19:00 18:56 · 6 km/h

  1. Dęblin16:06
  2. Łaskarzew Przystanek16:33
  3. Chrosna17:00
  4. Warszawa Falenica17:27
  5. Warszawa Olszynka Grochowska18:03
  6. Warszawa Grochów18:06
  7. Grodzisk Mazowiecki18:56

Today it is running worse than usual: typical arrival delay is +2 min; 63% of the last 16 runs arrived on time.

On-time · 30 days
63%
10/16 runs under 3 min
RT coverage: 15 full · 1 partial · 5 no data
On-time · 90 days
77%
33/43 runs under 3 min
RT coverage: 42 full · 1 partial · 9 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +8 min

Last 30 days

Arrival delay at Grodzisk Mazowiecki, in minutes. One bar per run.

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

Worst days

  • Wed 4 Nov Max en route +35 min · last fix heading to Grodzisk Mazowiecki +35 min
  • Tue 27 Oct Max en route +10 min · last fix heading to Grodzisk Mazowiecki +10 min
  • Thu 5 Nov Max en route +5 min · last fix heading to Grodzisk Mazowiecki +5 min
  • Wed 28 Oct Max en route +5 min · last fix heading to Grodzisk Mazowiecki +5 min
  • Wed 30 Sept Max en route +5 min · last fix heading to Milanówek +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 77% · 33
  • 3–10 min 19% · 8
  • 10–30 min 2% · 1
  • 30+ min 2% · 1

On-time by weekday

  • 86% M n=7
  • 89% T n=9
  • 56% W n=9
  • 67% T n=9
  • 89% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 43 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
16:06+1 min +5 minPassed
16:10 / 16:11≈ +1 min ≈ +5 minPassed
16:14 / 16:15≈ +1 min ≈ +5 minPassed
16:17 / 16:18≈ +1 min ≈ +5 minPassed
16:20≈ +1 min ≈ +5 minPassed
16:23≈ +1 min ≈ +5 minPassed
16:26 / 16:27≈ +1 min ≈ +5 minPassed
16:30≈ +1 min ≈ +5 minPassed
16:33 / 16:34≈ +1 min ≈ +5 minPassed
16:36 / 16:37≈ +1 min ≈ +5 minPassed
16:40≈ +1 min ≈ +5 minPassed
16:45≈ +1 min ≈ +5 minPassed
16:49 / 16:50≈ +1 min ≈ +5 minPassed
16:53 / 16:54≈ +1 min ≈ +5 minPassed
16:57≈ +1 min ≈ +5 minPassed
17:00≈ +1 min ≈ +5 minPassed
17:02≈ +1 min ≈ +5 minPassed
17:05 / 17:06≈ +1 min ≈ +5 minPassed
17:09≈ +1 min ≈ +5 minPassed
17:11 / 17:12≈ +1 min ≈ +5 minPassed
17:14 / 17:15≈ +1 min ≈ +5 minPassed
17:17 / 17:20≈ +1 min ≈ +5 minPassed
17:23 / 17:24≈ +1 min ≈ +5 minPassed
17:27 / 17:43≈ +1 min ≈ +5 minPassed
17:45 / 17:46≈ +1 min ≈ +5 minPassed
17:48≈ +1 min ≈ +5 minPassed
17:52≈ +1 min ≈ +5 minPassed
17:54 / 17:55≈ +1 min ≈ +5 minPassed
17:57 / 17:58≈ +1 min ≈ +5 minPassed
18:00 / 18:01≈ +1 min ≈ +5 minPassed
18:03 / 18:04≈ +1 min ≈ +5 minPassed
18:06 / 18:07≈ +1 min ≈ +5 minNext
18:10 / 18:12≈ +1 min ≈ +5 min
18:14≈ +1 min ≈ +5 min
18:16 / 18:17≈ +1 min ≈ +5 min
18:19 / 18:21≈ +1 min ≈ +5 min
18:23 / 18:24≈ +1 min ≈ +5 min
18:27 / 18:28≈ +1 min ≈ +5 min
18:32 / 18:33≈ +1 min ≈ +5 min
18:35≈ +1 min ≈ +5 min
18:36 / 18:37≈ +1 min ≈ +5 min
18:39≈ +1 min ≈ +5 min
18:42 / 18:43≈ +1 min ≈ +5 min
18:45 / 18:46≈ +1 min ≈ +5 min
18:48 / 18:49≈ +1 min ≈ +5 min
18:52 / 18:53≈ +1 min ≈ +5 min
18:56+1 min +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
Thu 12 NovWarszawa Gocławek 18:04Partial coverage+4 min+4 min
Tue 10 NovGrodzisk Mazowiecki 18:570 min—
Mon 9 NovGrodzisk Mazowiecki 18:570 min—
Fri 6 NovGrodzisk Mazowiecki 18:580 min—
Thu 5 NovGrodzisk Mazowiecki 19:02+5 min+5 min
Wed 4 NovGrodzisk Mazowiecki 19:32+35 min+35 min
Tue 3 NovGrodzisk Mazowiecki 18:59+1 min+1 min
Mon 2 NovGrodzisk Mazowiecki 18:58+1 min+1 min
Fri 30 OctGrodzisk Mazowiecki 18:570 min—
Thu 29 OctGrodzisk Mazowiecki 18:59+2 min+2 min
Wed 28 OctGrodzisk Mazowiecki 19:02+5 min+5 min
Tue 27 OctGrodzisk Mazowiecki 19:07+10 min+10 min
Mon 26 OctGrodzisk Mazowiecki 19:01+3 min+3 min
Fri 23 OctGrodzisk Mazowiecki 18:58No data—
Thu 22 OctGrodzisk Mazowiecki 18:58No data—
Wed 21 OctGrodzisk Mazowiecki 18:57No data—
Tue 20 OctGrodzisk Mazowiecki 18:57No data—
Mon 19 OctGrodzisk Mazowiecki 18:57No data—
Fri 16 OctGrodzisk Mazowiecki 18:580 min—
Thu 15 OctGrodzisk Mazowiecki 18:59+2 min+2 min
Wed 14 OctGrodzisk Mazowiecki 18:570 min—
Tue 13 OctGrodzisk Mazowiecki 18:570 min—
Mon 12 OctGrodzisk Mazowiecki 18:570 min—
Fri 9 OctGrodzisk Mazowiecki 18:570 min—
Thu 8 OctGrodzisk Mazowiecki 18:58+1 min+1 min
Wed 7 OctGrodzisk Mazowiecki 18:58+1 min+1 min
Tue 6 OctGrodzisk Mazowiecki 18:58+1 min+1 min
Mon 5 OctGrodzisk Mazowiecki 18:59+2 min+2 min
Fri 2 OctGrodzisk Mazowiecki 18:56+1 min+1 min
Thu 1 OctGrodzisk Mazowiecki 18:56No data—