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

View line Os 6887

Litvínov 19:36 → Teplice v Čechách 19:57 Mon, Tue, Wed, Thu, Fri 0 h 21 min · 8 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Teplice v Čechách at 19:58 No data

  1. Litvínov19:36
  2. Louka u Litvínova19:38
  3. Lom u Mostu19:41
  4. Háj u Duchcova19:48
  5. Jeníkov-Oldřichov19:51
  6. Řetenice19:54
  7. Teplice v Čechách19:57

Next service: tomorrow 19:36 from Litvínov · Tue 10 Nov

Next departure 19:36 tomorrow · Litvínov
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
97%
36/37 runs under 3 min
RT coverage: 37 full · 0 partial · 25 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 Teplice v Čechách, in minutes. One bar per run.

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

Worst days

  • Tue 15 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 36
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 86% T n=7
  • 100% W n=8
  • 100% T n=8
  • 100% 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, 37 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
19:36on time on time
19:38≈ on time ≈ on time
19:41≈ on time ≈ on time
19:45 / 19:46≈ on time ≈ +1 min
19:48 / 19:49≈ on time ≈ +1 min
19:51 / 19:52≈ on time ≈ +1 min
19:54 / 19:55≈ on time ≈ +2 min
19:57on 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
Mon 9 NovTeplice v Čechách 19:58No data—
Fri 6 NovDěčín hl. n. 20:54No data—
Thu 5 NovTeplice v Čechách 19:58No data—
Wed 4 NovTeplice v Čechách 19:58No data—
Tue 3 NovTeplice v Čechách 19:58No data—
Mon 2 NovTeplice v Čechách 19:58No data—
Fri 30 OctDěčín hl. n. 20:54No data—
Thu 29 OctTeplice v Čechách 19:58No data—
Tue 27 OctDěčín hl. n. 20:55No data—
Mon 26 OctTeplice v Čechách 19:58No data—
Fri 23 OctDěčín hl. n. 20:54No data—
Thu 22 OctTeplice v Čechách 19:58No data—
Wed 21 OctTeplice v Čechách 19:58No data—
Tue 20 OctTeplice v Čechách 19:58No data—
Mon 19 OctTeplice v Čechách 19:58No data—
Fri 16 OctDěčín hl. n. 20:54No data—
Thu 15 OctTeplice v Čechách 19:58No data—
Wed 14 OctTeplice v Čechách 19:58No data—
Tue 13 OctTeplice v Čechách 19:58No data—
Mon 12 OctTeplice v Čechách 19:59No data—
Fri 9 OctDěčín hl. n. 20:54No data—
Thu 8 OctTeplice v Čechách 19:58No data—
Wed 7 OctTeplice v Čechách 19:58No data—
Tue 6 OctTeplice v Čechách 19:58No data—
Mon 5 OctTeplice v Čechách 19:58No data—
Fri 2 Oct— 21:08+1 min+2 min
Thu 1 Oct— 20:120 min—
Wed 30 Sept— 20:12+1 min+1 min
Tue 29 Sept— 20:14+2 min+2 min
Fri 25 Sept— 21:080 min—