D11 66545 Legnica – Lubin

View line D11

Legnica 14:15 → Lubin 14:35 Daily 0 h 20 min · 6 stops Koleje Dolnośląskie

✓ Today’s run finished

Today it reached Lubin at 14:52 +17 min

  1. Legnica14:15
  2. Rzeszotary14:19
  3. Raszówka14:24
  4. Gorzelin14:27
  5. Chróstnik14:30
  6. Lubin14:35

Next service: tomorrow 14:15 from Legnica · Sat 21 Nov

Next departure 14:15 tomorrow · Legnica
On-time · 30 days
75%
18/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
62%
39/63 runs under 3 min
RT coverage: 63 full · 0 partial · 19 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +14 min

Last 30 days

Arrival delay at Lubin, 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 18 Nov Max en route +30 min · last fix heading to Lubin +30 min
  • Thu 19 Nov Max en route +29 min · last fix heading to Lubin +29 min
  • Fri 20 Nov Max en route +17 min · last fix heading to Lubin +17 min
  • Thu 3 Sept Max en route +13 min · last fix heading to Raszówka +13 min
  • Tue 6 Oct Max en route +12 min · last fix heading to Lubin +12 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 60% · 38
  • 3–10 min 29% · 18
  • 10–30 min 8% · 5
  • 30+ min 2% · 1

On-time by weekday

  • 44% M n=9
  • 44% T n=9
  • 63% W n=8
  • 67% T n=9
  • 75% F n=8
  • 70% S n=10
  • 70% S n=10

Stops and timetable

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

Last 90 days, 63 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
14:15+1 min +9 min
14:19 / 14:20≈ +1 min ≈ +9 min
14:24≈ +1 min ≈ +9 min
14:27≈ +1 min ≈ +9 min
14:30≈ +1 min ≈ +9 min
14:35+1 min +9 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
Fri 20 NovLubin 14:54+17 min+17 min
Thu 19 NovLubin 15:04+29 min+29 min
Wed 18 NovLubin 15:04+30 min+30 min
Tue 17 NovLubin 14:340 min—
Mon 16 NovLubin 14:340 min—
Sun 15 NovLubin 14:34−1 min—
Sat 14 NovLubin 14:340 min—
Fri 13 NovLubin 14:340 min—
Thu 12 NovLubin 14:370 min—
Wed 11 NovLubin 14:38+2 min+2 min
Tue 10 NovLubin 14:39+3 min+3 min
Mon 9 NovLubin 14:340 min—
Sun 8 NovLubin 14:34−2 min—
Sat 7 NovLubin 14:370 min—
Fri 6 NovLubin 14:37+1 min+1 min
Thu 5 NovLubin 14:340 min—
Wed 4 NovLubin 14:340 min—
Tue 3 NovLubin 14:37+1 min+1 min
Mon 2 NovLubin 14:43+7 min+7 min
Sun 1 NovLubin 14:41+5 min+5 min
Sat 31 OctLubin 14:360 min—
Fri 30 OctLubin 14:37+1 min+1 min
Thu 29 OctLubin 14:360 min—
Wed 28 OctLubin 14:36No data—
Tue 27 OctLubin 14:36No data—
Mon 26 OctLubin 14:370 min—
Sun 25 OctLubin 14:36No data—
Sat 24 OctLubin 14:36No data—
Fri 23 OctLubin 14:36No data—
Thu 22 OctLubin 14:36No data—