Os 17680 17680 Jirkov – Chomutov

View line Os 17680

Jirkov 04:48 → Chomutov 04:56 Mon, Tue, Wed, Thu, Fri 0 h 08 min · 4 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Chomutov at 04:57 No data

  1. Jirkov04:48
  2. Chomutov město04:52
  3. Chomutov město04:53
  4. Chomutov04:56

Next service: tomorrow 04:48 from Jirkov · Fri 6 Nov

Next departure 04:48 tomorrow · Jirkov
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Chomutov, 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 14 Aug Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 39
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 100% T n=8
  • 88% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
04:48on time on time
04:52 / 04:53≈ +1 min ≈ +1 min
04:53≈ +1 min ≈ +1 min
04:56+1 min +1 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
Thu 5 NovChomutov 04:57No data—
Wed 4 NovChomutov 04:57No data—
Tue 3 NovChomutov 04:57No data—
Mon 2 NovChomutov 04:57No data—
Fri 30 OctChomutov 04:57No data—
Thu 29 OctChomutov 04:57No data—
Tue 27 OctChomutov 04:57No data—
Mon 26 OctChomutov 04:57No data—
Fri 23 OctChomutov 04:57No data—
Thu 22 OctChomutov 04:57No data—
Wed 21 OctChomutov 04:57No data—
Tue 20 OctChomutov 04:57No data—
Mon 19 OctChomutov 04:57No data—
Fri 16 OctChomutov 04:57No data—
Thu 15 OctChomutov 04:57No data—
Wed 14 OctChomutov 04:57No data—
Tue 13 OctChomutov 04:57No data—
Mon 12 OctChomutov 04:57No data—
Fri 9 OctChomutov 04:57No data—
Thu 8 OctChomutov 04:57No data—
Wed 7 OctChomutov 04:57No data—
Tue 6 OctChomutov 04:57No data—
Mon 5 Oct— 05:100 min—
Fri 2 Oct— 05:11+1 min+1 min
Thu 1 Oct— 05:100 min—
Wed 30 Sept— 05:11+1 min+1 min
Tue 29 Sept— 05:520 min—
Fri 25 Sept— 05:110 min—
Thu 24 Sept— 05:11+1 min+1 min
Wed 23 Sept— 05:11+1 min+1 min