Os 27744 27744 Zadní Třebaň – Liteň

View line Os 27744

Zadní Třebaň 05:56 → Liteň 06:05 Mon, Tue, Wed, Thu, Fri 0 h 09 min · 3 stops České dráhy, a.s.

It does not run today

Last recorded run: Monday 16 November 0 min

Next service: tomorrow 05:56 from Zadní Třebaň · Wed 18 Nov

Next departure 05:56 tomorrow · Zadní Třebaň
On-time · 30 days
47%
9/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
38%
23/60 runs under 3 min
RT coverage: 60 full · 0 partial · 1 no data
Typical delay
+4min
Median at arrival, 90 days
30 days: +3 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

Arrival delay at Liteň, 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 11 Nov Max en route +9 min · last fix heading to Liteň +9 min
  • Fri 2 Oct Max en route +7 min · last fix heading to — +7 min
  • Mon 14 Sept Max en route +7 min · last fix heading to — +7 min
  • Tue 1 Sept Max en route +7 min · last fix heading to — +7 min
  • Tue 10 Nov Max en route +6 min · last fix heading to Liteň +6 min

Distribution · 90 days

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

  • Early 5% · 3
  • On time 33% · 20
  • 3–10 min 62% · 37
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=12
  • 25% T n=12
  • 36% W n=11
  • 46% T n=13
  • 33% F n=12
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 60 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:56+3 min +5 min
06:01≈ +3 min ≈ +5 min
06:05+4 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 11 July 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
Mon 16 NovLiteň 06:090 min+1 min
Fri 13 NovLiteň 06:13+4 min+4 min
Thu 12 NovLiteň 06:14+5 min+5 min
Wed 11 NovLiteň 06:18+9 min+9 min
Tue 10 NovLiteň 06:14+6 min+6 min
Mon 9 NovLiteň 06:090 min—
Fri 6 NovLiteň 06:13+3 min+3 min
Thu 5 NovLiteň 06:09−1 min+1 min
Wed 4 NovLiteň 06:090 min—
Tue 3 NovLiteň 06:09−1 min—
Mon 2 NovLiteň 06:14+6 min+6 min
Fri 30 OctLiteň 06:12+2 min+4 min
Thu 29 OctLiteň 06:12+3 min+3 min
Tue 27 OctLiteň 06:13+4 min+4 min
Mon 26 OctLiteň 06:11+1 min+3 min
Fri 23 OctLiteň 06:06No data—
Thu 22 OctLiteň 06:10+4 min+4 min
Wed 21 OctLiteň 06:14+4 min+4 min
Tue 20 OctLiteň 06:11+1 min+2 min
Mon 19 OctLiteň 06:10+1 min+1 min
Fri 16 OctLiteň 06:11+2 min+3 min
Thu 15 OctLiteň 06:07−2 min—
Wed 14 OctLiteň 06:08−2 min—
Tue 13 OctLiteň 06:100 min+1 min
Mon 12 OctLiteň 06:10+1 min+2 min
Fri 9 OctLiteň 06:12+3 min+3 min
Thu 8 OctLiteň 06:090 min—
Wed 7 OctLiteň 06:13+4 min+4 min
Tue 6 OctLiteň 06:15+5 min+6 min
Mon 5 Oct— 06:210 min+3 min