Os 6574 6574 Teplice v Čechách – Most

View line Os 6574

Teplice v Čechách 06:06 → Most 06:31 Mon, Tue, Wed, Thu, Fri 0 h 25 min · 10 stops RegioJet ÚK a.s.

✓ Today’s run finished

Today, last fix heading to Most at 06:32 No data

  1. Teplice v Čechách06:06
  2. Jeníkov-Oldřichov06:11
  3. Duchcov06:14
  4. Chotějovice06:17
  5. Bílina06:19
  6. Želenice nad Bílinou06:25
  7. Most06:31

Next service: tomorrow 06:06 from Teplice v Čechách · Fri 6 Nov

Next departure 06:06 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
63%
25/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+5min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Most, 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 25 Sept Max en route +103 min · last fix heading to — +102 min
  • Thu 20 Aug Max en route +25 min · last fix heading to — +24 min
  • Mon 14 Sept Max en route +10 min · last fix heading to — +9 min
  • Wed 30 Sept Max en route +5 min · last fix heading to — +5 min
  • Thu 24 Sept Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 63% · 25
  • 3–10 min 33% · 13
  • 10–30 min 3% · 1
  • 30+ min 3% · 1

On-time by weekday

  • 75% M n=8
  • 75% T n=8
  • 50% W n=8
  • 25% T n=8
  • 88% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
06:06on time +2 min
06:08≈ on time ≈ +5 min
06:11≈ on time ≈ +5 min
06:14≈ +1 min ≈ +5 min
06:15≈ +1 min ≈ +5 min
06:17≈ +1 min ≈ +5 min
06:19 / 06:20≈ +1 min ≈ +5 min
06:22≈ +1 min ≈ +4 min
06:25≈ +1 min ≈ +4 min
06:31+1 min +5 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
Thu 5 NovMost 06:32No data—
Wed 4 NovMost 06:32No data—
Tue 3 NovMost 06:33No data—
Mon 2 NovMost 06:32No data—
Fri 30 OctMost 06:32No data—
Thu 29 OctMost 06:32No data—
Tue 27 OctMost 06:32No data—
Mon 26 OctMost 06:32No data—
Fri 23 OctMost 06:32No data—
Thu 22 OctMost 06:32No data—
Wed 21 OctMost 06:32No data—
Tue 20 OctMost 06:32No data—
Mon 19 OctMost 06:32No data—
Fri 16 OctMost 06:32No data—
Thu 15 OctMost 06:32No data—
Wed 14 OctMost 06:32No data—
Tue 13 OctMost 06:32No data—
Mon 12 OctMost 06:32No data—
Fri 9 OctMost 06:32No data—
Thu 8 OctMost 06:32No data—
Wed 7 OctMost 06:32No data—
Tue 6 OctMost 06:32No data—
Mon 5 Oct— 06:48+2 min+2 min
Fri 2 Oct— 06:48+2 min+3 min
Thu 1 Oct— 06:49+3 min+3 min
Wed 30 Sept— 06:50+5 min+5 min
Tue 29 Sept— 06:46+1 min+2 min
Fri 25 Sept— 08:27+102 min+103 min
Thu 24 Sept— 06:50+5 min+6 min
Wed 23 Sept— 06:46+1 min+1 min