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

View line Os 16924

Teplice v Čechách 01:34 → Litvínov 01:54 Mon, Tue, Wed, Thu, Fri 0 h 20 min · 8 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Litvínov at 01:54 No data

  1. Teplice v Čechách01:34
  2. Řetenice01:36
  3. Jeníkov-Oldřichov01:39
  4. Osek01:44
  5. Lom u Mostu01:49
  6. Louka u Litvínova01:51
  7. Litvínov01:54

Next service: tomorrow 01:34 from Teplice v Čechách · Thu 12 Nov

Next departure 01:34 tomorrow · Teplice v Čechách
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
67%
24/36 runs under 3 min
RT coverage: 36 full · 0 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
P90
+14min
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

  • Fri 21 Aug Max en route +20 min · last fix heading to — +20 min
  • Wed 2 Sept Max en route +19 min · last fix heading to — +19 min
  • Thu 20 Aug Max en route +34 min · last fix heading to — +19 min
  • Wed 19 Aug Max en route +18 min · last fix heading to — +18 min
  • Tue 8 Sept Max en route +10 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 24
  • 3–10 min 17% · 6
  • 10–30 min 17% · 6
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 71% T n=7
  • 57% W n=7
  • 57% T n=7
  • 63% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 36 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
01:34on time +17 min
01:36 / 01:37≈ +1 min ≈ +15 min
01:39 / 01:40≈ +1 min ≈ +13 min
01:42≈ +1 min ≈ +12 min
01:44 / 01:45≈ +1 min ≈ +10 min
01:49≈ +1 min ≈ +12 min
01:51 / 01:52≈ on time ≈ +13 min
01:54on time +14 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
Wed 11 NovLitvínov 01:54No data—
Tue 10 NovLitvínov 01:54No data—
Mon 9 NovLitvínov 01:54No data—
Fri 6 NovLitvínov 01:54No data—
Thu 5 NovLitvínov 01:54No data—
Wed 4 NovLitvínov 01:54No data—
Tue 3 NovLitvínov 01:54No data—
Mon 2 NovLitvínov 01:54No data—
Fri 30 OctLitvínov 01:55No data—
Thu 29 OctLitvínov 01:55No data—
Tue 27 OctLitvínov 01:55No data—
Mon 26 OctLitvínov 01:55No data—
Fri 23 OctLitvínov 01:55No data—
Thu 22 OctLitvínov 01:55No data—
Wed 21 OctLitvínov 01:55No data—
Tue 20 OctLitvínov 01:55No data—
Mon 19 OctLitvínov 01:55No data—
Fri 16 OctLitvínov 01:55No data—
Thu 15 OctLitvínov 01:55No data—
Wed 14 OctLitvínov 01:55No data—
Tue 13 OctLitvínov 01:55No data—
Mon 12 OctLitvínov 01:55No data—
Fri 9 OctLitvínov 01:55No data—
Thu 8 OctLitvínov 01:55No data—
Wed 7 OctLitvínov 01:55No data—
Tue 6 OctLitvínov 01:55No data—
Mon 5 Oct— 02:080 min—
Fri 2 Oct— 02:080 min—
Thu 1 Oct— 01:590 min—
Wed 30 Sept— 01:590 min+2 min