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

View line Os 27747

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

✓ Today’s run finished

Today it reached Zadní Třebaň at 08:00 +5 min

  1. Liteň07:46
  2. Běleč07:49
  3. Zadní Třebaň07:55

Next service: Monday 07:46 from Liteň · Mon 9 Nov

Next departure 07:46 Monday · Liteň
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
97%
60/62 runs under 3 min
RT coverage: 62 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Zadní Třebaň, 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 +5 min · last fix heading to Zadní Třebaň +5 min
  • Wed 30 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 94% · 58
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=13
  • 92% W n=12
  • 100% T n=13
  • 92% 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, 62 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
07:46on time +2 min
07:49≈ on time ≈ +2 min
07:55on time +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 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
Fri 6 NovZadní Třebaň 07:59+5 min+5 min
Thu 5 NovZadní Třebaň 07:54−1 min—
Wed 4 NovZadní Třebaň 07:590 min+1 min
Tue 3 NovZadní Třebaň 07:590 min+2 min
Mon 2 NovZadní Třebaň 07:58+2 min+2 min
Fri 30 OctZadní Třebaň 07:59+1 min+1 min
Thu 29 OctZadní Třebaň 07:590 min+1 min
Tue 27 OctZadní Třebaň 07:56−2 min—
Mon 26 OctZadní Třebaň 08:00+1 min+1 min
Fri 23 OctZadní Třebaň 07:56No data—
Thu 22 OctZadní Třebaň 07:57+2 min+2 min
Wed 21 OctZadní Třebaň 07:59−1 min+1 min
Tue 20 OctZadní Třebaň 08:00+1 min+1 min
Mon 19 OctZadní Třebaň 07:590 min—
Fri 16 OctZadní Třebaň 07:56+1 min+1 min
Thu 15 OctZadní Třebaň 07:58−1 min—
Wed 14 OctZadní Třebaň 07:56−1 min+1 min
Tue 13 OctZadní Třebaň 07:590 min+1 min
Mon 12 OctZadní Třebaň 07:590 min—
Fri 9 OctZadní Třebaň 07:56−1 min—
Thu 8 OctZadní Třebaň 07:56+2 min+2 min
Wed 7 OctZadní Třebaň 07:59+1 min+1 min
Tue 6 OctZadní Třebaň 07:57+1 min+1 min
Mon 5 Oct— 08:100 min—
Fri 2 Oct— 08:09−1 min—
Thu 1 Oct— 08:090 min+1 min
Wed 30 Sept— 08:13+4 min+4 min
Tue 29 Sept— 08:100 min—
Fri 25 Sept— 08:090 min+1 min
Thu 24 Sept— 08:090 min+1 min