Os 6373 6373 Jindřichovice p.Sm. – Liberec

View line Os 6373

Jindřichovice p.Sm. 14:07 → Liberec 15:23 Sat, Sun 1 h 16 min · 17 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 1 November No data

Next service: Saturday 14:07 from Jindřichovice p.Sm. · Sat 7 Nov

Next departure 14:07 Saturday · Jindřichovice p.Sm.
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
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 9 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Liberec, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 21% · 4
  • On time 79% · 15
  • 3–10 min 0% · 0
  • 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
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 19 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:07on time on time
14:09≈ on time ≈ on time
14:13≈ on time ≈ on time
14:20 / 14:21≈ on time ≈ on time
14:24≈ on time ≈ on time
14:28≈ on time ≈ on time
14:31≈ on time ≈ on time
14:34≈ on time ≈ on time
14:37≈ on time ≈ on time
14:41≈ on time ≈ on time
14:46 / 14:48≈ 1 min early ≈ on time
14:54 / 14:59≈ 1 min early ≈ on time
15:06≈ 1 min early ≈ on time
15:10≈ 1 min early ≈ on time
15:14≈ 1 min early ≈ on time
15:16≈ 1 min early ≈ on time
15:231 min early 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 NovLiberec 15:24No data—
Sat 31 OctLiberec 15:24No data—
Wed 28 OctLiberec 15:24No data—
Sun 25 OctLiberec 15:24No data—
Sat 24 OctLiberec 15:24No data—
Sun 18 OctLiberec 15:24No data—
Sat 17 OctLiberec 15:24No data—
Sun 11 OctLiberec 15:24No data—
Sat 10 OctLiberec 15:24No data—
Sun 4 Oct— 15:36−2 min—
Sat 3 Oct— 15:370 min—
Mon 28 Sept— 15:370 min+3 min
Sun 27 Sept— 15:37−1 min+1 min
Sat 26 Sept— 15:37−1 min—
Sun 20 Sept— 15:370 min—
Sat 19 Sept— 15:380 min+2 min
Sun 13 Sept— 15:36−1 min+2 min
Sat 12 Sept— 15:380 min+1 min
Sun 6 Sept— 15:36−1 min—
Sat 5 Sept— 15:37−1 min—
Sun 30 Aug— 15:36−1 min—
Sat 29 Aug— 15:36−2 min—
Sun 23 Aug— 15:35−2 min+1 min
Sat 22 Aug— 15:36−1 min—
Sun 16 Aug— 15:36−1 min—
Sat 15 Aug— 15:36−1 min—
Sun 9 Aug— 15:370 min+1 min
Sat 8 Aug— 15:35−2 min—