Os 19763 19763 Noutonice – Hostivice

View line Os 19763

Noutonice 18:57 → Hostivice 19:18 Daily 0 h 21 min · 8 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Hostivice at 19:18 0 min

  1. Noutonice18:57
  2. Tuchoměřice19:01
  3. Středokluky19:03
  4. Dobrovíz-Amazon19:08
  5. Hostouň u Prahy19:09
  6. Jeneč zastávka19:12
  7. Hostivice19:18

Next service: tomorrow 18:57 from Noutonice · Tue 10 Nov

Next departure 18:57 tomorrow · Noutonice
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 25 full · 0 partial · 5 no data
On-time · 90 days
92%
72/78 runs under 3 min
RT coverage: 78 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

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

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

Worst days

  • Sat 24 Oct Max en route +22 min · last fix heading to Hostivice +20 min
  • Wed 23 Sept Max en route +13 min · last fix heading to — +10 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Hostivice +5 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Hostivice +3 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Hostivice +3 min

Distribution · 90 days

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

  • Early 13% · 10
  • On time 79% · 62
  • 3–10 min 5% · 4
  • 10–30 min 3% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=10
  • 82% W n=11
  • 91% T n=11
  • 91% F n=11
  • 83% S n=12
  • 100% S n=12

Stops and timetable

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

Last 90 days, 78 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
18:57on time +2 min
19:01≈ on time ≈ +2 min
19:03 / 19:04≈ on time ≈ +2 min
19:07≈ on time ≈ +2 min
19:08≈ on time ≈ +2 min
19:09≈ on time ≈ +1 min
19:12≈ on time ≈ +1 min
19:18on 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
Mon 9 NovHostivice 19:220 min+1 min
Sun 8 NovHostivice 19:24+1 min+3 min
Sat 7 NovHostivice 19:23+1 min+3 min
Fri 6 NovHostivice 19:19−1 min—
Thu 5 NovHostivice 19:23+1 min+1 min
Wed 4 NovHostivice 19:230 min+1 min
Tue 3 NovHostivice 19:220 min+1 min
Mon 2 NovHostivice 19:220 min+1 min
Sun 1 NovHostivice 19:19−1 min+1 min
Sat 31 OctHostivice 19:220 min+2 min
Fri 30 OctHostivice 19:19No data—
Thu 29 OctHostivice 19:19No data—
Wed 28 OctHostivice 19:19No data—
Tue 27 OctHostivice 19:20No data—
Mon 26 OctHostivice 19:19No data—
Sun 25 OctHostivice 19:22−1 min+1 min
Sat 24 OctHostivice 19:43+20 min+22 min
Fri 23 OctHostivice 19:26+3 min+4 min
Thu 22 OctHostivice 19:22−1 min+1 min
Wed 21 OctHostivice 19:22−1 min—
Tue 20 OctHostivice 19:230 min+1 min
Mon 19 OctHostivice 19:23+1 min+1 min
Sun 18 OctHostivice 19:190 min—
Sat 17 OctHostivice 19:19+1 min+1 min
Fri 16 OctHostivice 19:230 min+1 min
Thu 15 OctHostivice 19:230 min+1 min
Wed 14 OctHostivice 19:23+1 min+2 min
Tue 13 OctHostivice 19:22−1 min+1 min
Mon 12 OctHostivice 19:230 min+1 min
Sun 11 OctHostivice 19:230 min+2 min