Os 7246 7246 Bor – Tachov

View line Os 7246

Bor 14:59 → Tachov 15:26 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 7 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Tachov at 15:27 No data

  1. Bor14:59
  2. Doly15:03
  3. Staré Sedliště15:07
  4. Pernolec15:14
  5. Malý Rapotín15:18
  6. Tachov zastávka15:20
  7. Tachov15:26

Next service: tomorrow 14:59 from Bor · Fri 6 Nov

Next departure 14:59 tomorrow · Bor
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
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 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 Tachov, 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 28 Aug Max en route +6 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 18% · 7
  • On time 80% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 100% 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 (7 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
14:59on time on time
15:03≈ on time ≈ on time
15:07 / 15:08≈ on time ≈ on time
15:14≈ on time ≈ +1 min
15:18≈ on time ≈ +1 min
15:20≈ on time ≈ +1 min
15: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
Thu 5 NovTachov 15:27No data—
Wed 4 NovTachov 15:28No data—
Tue 3 NovTachov 15:27No data—
Mon 2 NovTachov 15:27No data—
Fri 30 OctTachov 15:27No data—
Thu 29 OctTachov 15:27No data—
Tue 27 OctTachov 15:27No data—
Mon 26 OctTachov 15:27No data—
Fri 23 OctTachov 15:27No data—
Thu 22 OctTachov 15:27No data—
Wed 21 OctTachov 15:27No data—
Tue 20 OctTachov 15:27No data—
Mon 19 OctTachov 15:27No data—
Fri 16 OctTachov 15:27No data—
Thu 15 OctTachov 15:27No data—
Wed 14 OctTachov 15:27No data—
Tue 13 OctTachov 15:27No data—
Mon 12 OctTachov 15:27No data—
Fri 9 OctTachov 15:27No data—
Thu 8 OctTachov 15:27No data—
Wed 7 OctTachov 15:27No data—
Tue 6 OctTachov 15:27No data—
Mon 5 Oct— 15:400 min—
Fri 2 Oct— 15:38−2 min—
Thu 1 Oct— 15:400 min—
Wed 30 Sept— 15:40−1 min—
Tue 29 Sept— 15:400 min—
Fri 25 Sept— 15:40−1 min—
Thu 24 Sept— 15:39−1 min—
Wed 23 Sept— 15:42+1 min+1 min