Os 16312 16312 Bílý Potok p.Sm. – Raspenava

View line Os 16312

Bílý Potok p.Sm. 10:41 → Raspenava 10:53 Daily 0 h 12 min · 5 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Raspenava at 10:54 No data

  1. Bílý Potok p.Sm.10:41
  2. Hejnice10:44
  3. Lužec pod Smrkem10:47
  4. Luh pod Smrkem10:49
  5. Raspenava10:53

Next service: tomorrow 10:41 from Bílý Potok p.Sm. · Thu 12 Nov

Next departure 10:41 tomorrow · Bílý Potok p.Sm.
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
100%
52/52 runs under 3 min
RT coverage: 52 full · 0 partial · 37 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 Raspenava, 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

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

  • Early 2% · 1
  • On time 98% · 51
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 100% W n=6
  • 100% T n=7
  • 100% F n=8
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 52 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
10:41on time +1 min
10:44≈ on time ≈ +1 min
10:47≈ on time ≈ +1 min
10:49≈ on time ≈ +1 min
10:53on 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
Wed 11 NovRaspenava 10:54No data—
Tue 10 NovRaspenava 10:54No data—
Mon 9 NovRaspenava 10:54No data—
Sun 8 NovRaspenava 10:54No data—
Sat 7 NovRaspenava 10:54No data—
Fri 6 NovRaspenava 10:54No data—
Thu 5 NovRaspenava 10:54No data—
Wed 4 NovRaspenava 10:54No data—
Tue 3 NovRaspenava 10:54No data—
Mon 2 NovRaspenava 10:54No data—
Sun 1 NovRaspenava 10:54No data—
Sat 31 OctRaspenava 10:54No data—
Fri 30 OctRaspenava 10:54No data—
Thu 29 OctRaspenava 10:54No data—
Wed 28 OctRaspenava 10:54No data—
Tue 27 OctRaspenava 10:54No data—
Mon 26 OctRaspenava 10:54No data—
Sun 25 OctRaspenava 10:54No data—
Sat 24 OctRaspenava 10:54No data—
Fri 23 OctRaspenava 10:54No data—
Thu 22 OctRaspenava 10:54No data—
Wed 21 OctRaspenava 10:54No data—
Tue 20 OctRaspenava 10:54No data—
Mon 19 OctRaspenava 10:54No data—
Sun 18 OctRaspenava 10:54No data—
Sat 17 OctRaspenava 10:54No data—
Fri 16 OctRaspenava 10:54No data—
Thu 15 OctRaspenava 10:54No data—
Wed 14 OctRaspenava 10:54No data—
Tue 13 OctRaspenava 10:54No data—