Os 27130 27130 Chodov – Loket

View line Os 27130

Chodov 17:22 → Loket 17:33 Tue, Sat, Sun 0 h 11 min · 4 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 8 November No data

Next service: Saturday 17:22 from Chodov · Sat 14 Nov

Next departure 17:22 Saturday · Chodov
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
82%
14/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
9 in 10 runs arrive with less than this

Last 30 days

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

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

Worst days

  • Sun 6 Sept Max en route +8 min · last fix heading to — +8 min
  • Sat 12 Sept Max en route +5 min · last fix heading to — +5 min
  • Sat 5 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 14
  • 3–10 min 18% · 3
  • 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
  • 75% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 17 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
17:22on time +4 min
17:25 / 17:26≈ on time ≈ +4 min
17:28≈ on time ≈ +4 min
17:33on time +4 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 8 NovLoket 17:34No data—
Sat 7 NovLoket 17:34No data—
Sun 1 NovLoket 17:34No data—
Sat 31 OctLoket 17:34No data—
Wed 28 OctLoket 17:34No data—
Sun 25 OctLoket 17:34No data—
Sat 24 OctLoket 17:34No data—
Sun 18 OctLoket 17:34No data—
Sat 17 OctLoket 17:34No data—
Sun 11 OctLoket 17:34No data—
Sat 10 OctLoket 17:34No data—
Sun 4 Oct— 17:49+1 min+1 min
Sat 3 Oct— 17:480 min—
Mon 28 Sept— 17:480 min—
Sun 27 Sept— 17:470 min—
Sat 26 Sept— 17:480 min—
Sun 20 Sept— 17:470 min—
Sat 19 Sept— 17:49+1 min+2 min
Sun 13 Sept— 17:49+2 min+3 min
Sat 12 Sept— 17:52+5 min+5 min
Sun 6 Sept— 17:55+8 min+8 min
Sat 5 Sept— 17:51+3 min+3 min
Sun 30 Aug— 17:49+2 min+2 min
Sat 29 Aug— 17:470 min—
Sun 23 Aug— 17:470 min—
Sat 22 Aug— 17:48+1 min+2 min
Sun 16 Aug— 17:470 min—
Sat 15 Aug— 17:470 min—