D11 66535 Legnica → Lubin

View line D11

Legnica 05:45 → Lubin 06:01 Daily 0 h 16 min · 2 stops Koleje Dolnośląskie

D11 66535 Azuryt Legnica–Lubin: final delay under 3 min on 24 of its 28 runs with data in the last 30 days (86%). Median final delay: −1 min. TrainsRadar data as of 22 Nov 2026, 23:41 (GMT+1).

✓ Today’s run finished

Today it reached Lubin at 06:03 +2 min

  1. Legnica05:45
  2. Lubin06:01

Next service: tomorrow 05:45 from Legnica · Mon 23 Nov

Next departure 05:45 tomorrow · Legnica
On-time · 30 days
86%
24/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
91%
67/74 runs under 3 min
RT coverage: 74 full · 0 partial · 11 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 6 Nov Max en route +20 min · last fix heading to Lubin +20 min
  • Sun 1 Nov Max en route +15 min · last fix heading to Lubin +15 min
  • Thu 10 Sept Max en route +10 min · last fix heading to Lubin +10 min
  • Thu 15 Oct Max en route +7 min · last fix heading to Lubin +7 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Lubin +5 min

Distribution · 90 days

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

  • Early 45% · 33
  • On time 46% · 34
  • 3–10 min 5% · 4
  • 10–30 min 4% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=10
  • 91% W n=11
  • 80% T n=10
  • 91% F n=11
  • 100% S n=11
  • 70% S n=10

Stops and timetable

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

Last 90 days, 74 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:451 min early +2 min
06:011 min early +2 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
Sun 22 NovLubin 06:04+2 min+2 min
Sat 21 NovLubin 05:59−1 min—
Fri 20 NovLubin 05:59−2 min—
Thu 19 NovLubin 06:02−1 min—
Wed 18 NovLubin 05:59−1 min—
Tue 17 NovLubin 05:59−1 min—
Mon 16 NovLubin 06:03+1 min+1 min
Sun 15 NovLubin 06:020 min—
Sat 14 NovLubin 06:020 min—
Fri 13 NovLubin 06:020 min—
Thu 12 NovLubin 06:020 min—
Wed 11 NovLubin 05:59−3 min—
Tue 10 NovLubin 05:59−2 min—
Mon 9 NovLubin 06:04+2 min+2 min
Sun 8 NovLubin 06:04+3 min+3 min
Sat 7 NovLubin 05:59−2 min—
Fri 6 NovLubin 06:23+20 min+20 min
Thu 5 NovLubin 05:59−2 min—
Wed 4 NovLubin 05:59−1 min—
Tue 3 NovLubin 05:59−1 min—
Mon 2 NovLubin 05:59−2 min—
Sun 1 NovLubin 06:18+15 min+15 min
Sat 31 OctLubin 06:020 min—
Fri 30 OctLubin 06:020 min—
Thu 29 OctLubin 06:01−1 min—
Wed 28 OctLubin 06:05+3 min+3 min
Tue 27 OctLubin 06:01−1 min—
Mon 26 OctLubin 06:01−1 min—
Sun 25 OctLubin 06:02No data—
Sat 24 OctLubin 06:03No data—