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

View line Os 16949

Litvínov 22:06 → Teplice v Čechách 22:26 Daily 0 h 20 min · 8 stops RegioJet ÚK a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 22:06 from Litvínov · Thu 5 Nov

Next departure 22:06 today · Litvínov
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
95%
55/58 runs under 3 min
RT coverage: 58 full · 0 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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

  • Sat 19 Sept Max en route +4 min · last fix heading to — +3 min
  • Thu 17 Sept Max en route +4 min · last fix heading to — +3 min
  • Mon 10 Aug Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 55
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=8
  • 100% W n=8
  • 88% T n=8
  • 100% F n=8
  • 89% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 58 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
22:06on time on time
22:08≈ on time ≈ on time
22:11≈ on time ≈ +1 min
22:15≈ on time ≈ +1 min
22:17≈ on time ≈ +1 min
22:19≈ on time ≈ +1 min
22:22 / 22:23≈ on time ≈ +1 min
22:26on time +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
Wed 4 NovTeplice v Čechách 22:27No data—
Tue 3 NovTeplice v Čechách 22:27No data—
Mon 2 NovTeplice v Čechách 22:27No data—
Sun 1 NovTeplice v Čechách 22:27No data—
Sat 31 OctTeplice v Čechách 22:27No data—
Fri 30 OctTeplice v Čechách 22:27No data—
Thu 29 OctTeplice v Čechách 22:27No data—
Wed 28 OctTeplice v Čechách 22:27No data—
Tue 27 OctTeplice v Čechách 22:28No data—
Mon 26 OctTeplice v Čechách 22:27No data—
Sun 25 OctTeplice v Čechách 22:27No data—
Sat 24 OctTeplice v Čechách 22:27No data—
Fri 23 OctTeplice v Čechách 22:27No data—
Thu 22 OctTeplice v Čechách 22:27No data—
Wed 21 OctTeplice v Čechách 22:27No data—
Tue 20 OctTeplice v Čechách 22:27No data—
Mon 19 OctTeplice v Čechách 22:28No data—
Sun 18 OctTeplice v Čechách 22:27No data—
Sat 17 OctTeplice v Čechách 22:27No data—
Fri 16 OctTeplice v Čechách 22:27No data—
Thu 15 OctTeplice v Čechách 22:27No data—
Wed 14 OctTeplice v Čechách 22:27No data—
Tue 13 OctTeplice v Čechách 22:27No data—
Mon 12 OctTeplice v Čechách 22:27No data—
Sun 11 OctTeplice v Čechách 22:27No data—
Sat 10 OctTeplice v Čechách 22:27No data—
Fri 9 OctTeplice v Čechách 22:27No data—
Thu 8 OctTeplice v Čechách 22:28No data—
Wed 7 OctTeplice v Čechách 22:27No data—
Tue 6 OctTeplice v Čechách 22:27No data—