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

View line Os 16937

Litvínov 10:27 → Teplice v Čechách 10:47 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 10:27 from Litvínov · Sat 7 Nov

Next departure 10:27 tomorrow · Litvínov
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
94%
17/18 runs under 3 min
RT coverage: 18 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
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 26 Sept Max en route +9 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 88% S n=8
  • 100% 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
Litvínov
10:27on time on time
Louka u Litvínova
10:29≈ on time ≈ on time
Lom u Mostu
10:32≈ on time ≈ on time
Osek
10:36≈ on time ≈ on time
Háj u Duchcova
10:38≈ on time ≈ on time
Jeníkov-Oldřichov
10:40≈ on time ≈ on time
Řetenice
10:43 / 10:44≈ on time ≈ on time
Teplice v Čechách
10:47on time on time

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 NovTeplice v Čechách 10:48No data—
Sat 31 OctTeplice v Čechách 10:48No data—
Wed 28 OctTeplice v Čechách 10:48No data—
Sun 25 OctTeplice v Čechách 10:48No data—
Sat 24 OctTeplice v Čechách 10:48No data—
Sun 18 OctTeplice v Čechách 10:48No data—
Sat 17 OctTeplice v Čechách 10:48No data—
Sun 11 OctTeplice v Čechách 10:48No data—
Sat 10 OctTeplice v Čechách 10:48No data—
Sun 4 Oct— 11:00−1 min—
Sat 3 Oct— 11:010 min—
Mon 28 Sept— 11:010 min+1 min
Sun 27 Sept— 11:00−1 min—
Sat 26 Sept— 11:09+7 min+9 min
Sun 20 Sept— 11:010 min+2 min
Sat 19 Sept— 11:020 min+2 min
Sun 13 Sept— 11:010 min+1 min
Sat 12 Sept— 11:020 min+1 min
Sun 6 Sept— 11:010 min+2 min
Sat 5 Sept— 11:020 min—
Sun 30 Aug— 11:01−1 min—
Sat 29 Aug— 11:01−1 min+1 min
Sun 23 Aug— 11:00−1 min—
Sat 22 Aug— 11:00−1 min—
Sun 16 Aug— 11:010 min—
Sat 15 Aug— 11:010 min+1 min
Sun 9 Aug— 11:02+1 min+2 min