Os 16934 16934 Teplice v Čechách – Litvínov

View line Os 16934

Teplice v Čechách 07:09 → Litvínov 07:29 Sat, Sun 0 h 20 min · 8 stops RegioJet ÚK a.s.

It does not run today

Last recorded run: Sunday 1 November No data

Next service: tomorrow 07:09 from Teplice v Čechách · Sat 7 Nov

Next departure 07:09 tomorrow · Teplice v Čechách
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
78%
14/18 runs under 3 min
RT coverage: 18 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
P90
+13min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Litvínov, 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 13 Sept Max en route +91 min · last fix heading to — +89 min
  • Sun 27 Sept Max en route +15 min · last fix heading to — +13 min
  • Sat 12 Sept Max en route +16 min · last fix heading to — +13 min
  • Sat 3 Oct Max en route +12 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 6% · 1
  • On time 72% · 13
  • 3–10 min 6% · 1
  • 10–30 min 11% · 2
  • 30+ min 6% · 1

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 75% S n=8
  • 78% S n=9

Stops and timetable

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

Last 90 days, 18 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
Teplice v Čechách
07:09+1 min +14 min
Řetenice
07:11 / 07:12≈ +1 min ≈ +14 min
Jeníkov-Oldřichov
07:14≈ +1 min ≈ +14 min
Háj u Duchcova
07:17≈ on time ≈ +14 min
Osek
07:18 / 07:19≈ on time ≈ +14 min
Lom u Mostu
07:23≈ on time ≈ +13 min
Louka u Litvínova
07:26≈ on time ≈ +13 min
Litvínov
07:29on time +13 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 NovLitvínov 07:30No data—
Sat 31 OctLitvínov 07:30No data—
Wed 28 OctLitvínov 07:30No data—
Sun 25 OctLitvínov 07:31No data—
Sat 24 OctLitvínov 07:30No data—
Sun 18 OctLitvínov 07:31No data—
Sat 17 OctLitvínov 07:30No data—
Sun 11 OctLitvínov 07:30No data—
Sat 10 OctLitvínov 07:30No data—
Sun 4 Oct— 07:46+2 min+4 min
Sat 3 Oct— 07:53+9 min+12 min
Mon 28 Sept— 07:45+1 min+3 min
Sun 27 Sept— 07:57+13 min+15 min
Sat 26 Sept— 07:46+2 min+3 min
Sun 20 Sept— 07:42−1 min+1 min
Sat 19 Sept— 07:440 min+2 min
Sun 13 Sept— 09:12+89 min+91 min
Sat 12 Sept— 07:57+13 min+16 min
Sun 6 Sept— 07:430 min+2 min
Sat 5 Sept— 07:42−1 min+2 min
Sun 30 Aug— 07:42−1 min—
Sat 29 Aug— 07:43−1 min+1 min
Sun 23 Aug— 07:42−1 min+1 min
Sat 22 Aug— 07:42−1 min+2 min
Sun 16 Aug— 07:41−2 min—
Sat 15 Aug— 07:430 min+2 min
Sun 9 Aug— 07:430 min+2 min