Os 27129 27129 Loket – Chodov

View line Os 27129

Loket 14:27 → Chodov 14:45 Sat, Sun 0 h 18 min · 4 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 1 November No data

Next service: Saturday 14:27 from Loket · Sat 7 Nov

Next departure 14:27 Saturday · Loket
On-time · 30 days
—
Too little data (0/9 runs with data)
RT coverage: 0 full · 0 partial · 9 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Chodov, in minutes. One bar per run.

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

Worst days

  • Sat 3 Oct Max en route +8 min · last fix heading to — +7 min
  • Sun 13 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 89% S n=9
  • 89% S n=9

Stops and timetable

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

Last 90 days, 19 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:27on time +4 min
14:32≈ on time ≈ +3 min
14:35 / 14:42≈ on time ≈ +3 min
14:45on 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
Sun 1 NovChodov 14:46No data—
Sat 31 OctChodov 14:46No data—
Wed 28 OctChodov 14:46No data—
Sun 25 OctChodov 14:46No data—
Sat 24 OctChodov 14:46No data—
Sun 18 OctChodov 14:46No data—
Sat 17 OctChodov 14:46No data—
Sun 11 OctChodov 14:46No data—
Sat 10 OctChodov 14:46No data—
Sun 4 Oct— 14:490 min+1 min
Sat 3 Oct— 14:55+7 min+8 min
Mon 28 Sept— 14:490 min—
Sun 27 Sept— 14:490 min—
Sat 26 Sept— 14:500 min—
Sun 20 Sept— 14:49+1 min+2 min
Sat 19 Sept— 14:500 min—
Sun 13 Sept— 14:52+4 min+4 min
Sat 12 Sept— 14:500 min—
Sun 6 Sept— 14:49+1 min+1 min
Sat 5 Sept— 14:50+1 min+1 min
Sun 30 Aug— 14:490 min—
Sat 29 Aug— 14:500 min+1 min
Sun 23 Aug— 14:490 min—
Sat 22 Aug— 14:490 min—
Sun 16 Aug— 14:49+1 min+4 min
Sat 15 Aug— 14:480 min—
Sun 9 Aug— 14:490 min—
Sat 8 Aug— 14:49+1 min+1 min