Os 16100 16100 Radejčín – Teplice v Čechách

View line Os 16100

Radejčín 04:32 → Teplice v Čechách 05:20 Mon, Tue, Wed, Thu, Fri 0 h 48 min · 12 stops České dráhy, a.s.

✓ Today’s run finished

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

  1. Radejčín04:32
  2. Bořislav04:41
  3. Žalany04:46
  4. Úpořiny04:53
  5. Bystřany v Čechách05:05
  6. Teplice zámecká zahrada05:12
  7. Teplice v Čechách05:20

Next service: Monday 04:32 from Radejčín · Mon 9 Nov

Next departure 04:32 Monday · Radejčín
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
93%
37/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 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

  • Thu 20 Aug Max en route +13 min · last fix heading to — +11 min
  • Mon 14 Sept Max en route +7 min · last fix heading to — +5 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +3 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 93% · 37
  • 3–10 min 5% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 100% T n=8
  • 100% W n=8
  • 88% 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 (12 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
04:32on time on time
04:36≈ on time ≈ on time
04:41≈ on time ≈ on time
04:44≈ on time ≈ +1 min
04:46≈ on time ≈ +1 min
04:49≈ on time ≈ +1 min
04:53 / 05:01≈ on time ≈ +1 min
05:05≈ on time ≈ +1 min
05:07≈ on time ≈ +1 min
05:12≈ on time ≈ +2 min
05:16 / 05:17≈ on time ≈ +2 min
05:20on 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
Fri 6 NovTeplice v Čechách 05:19No data—
Thu 5 NovTeplice v Čechách 05:19No data—
Wed 4 NovTeplice v Čechách 05:19No data—
Tue 3 NovTeplice v Čechách 05:20No data—
Mon 2 NovTeplice v Čechách 05:19No data—
Fri 30 OctTeplice v Čechách 05:21No data—
Thu 29 OctTeplice v Čechách 05:21No data—
Tue 27 OctTeplice v Čechách 05:21No data—
Mon 26 OctTeplice v Čechách 05:21No data—
Fri 23 OctTeplice v Čechách 05:21No data—
Thu 22 OctTeplice v Čechách 05:21No data—
Wed 21 OctTeplice v Čechách 05:21No data—
Tue 20 OctTeplice v Čechách 05:21No data—
Mon 19 OctTeplice v Čechách 05:21No data—
Fri 16 OctTeplice v Čechách 05:21No data—
Thu 15 OctTeplice v Čechách 05:21No data—
Wed 14 OctTeplice v Čechách 05:21No data—
Tue 13 OctTeplice v Čechách 05:21No data—
Mon 12 OctTeplice v Čechách 05:21No data—
Fri 9 OctTeplice v Čechách 05:21No data—
Thu 8 OctTeplice v Čechách 05:21No data—
Wed 7 OctTeplice v Čechách 05:21No data—
Tue 6 OctTeplice v Čechách 05:21No data—
Mon 5 Oct— 05:38+3 min+3 min
Fri 2 Oct— 05:340 min—
Thu 1 Oct— 05:340 min—
Wed 30 Sept— 05:36+2 min+3 min
Tue 29 Sept— 05:340 min—
Fri 25 Sept— 05:350 min—
Thu 24 Sept— 05:35+1 min+2 min