Os 19749 19749 Noutonice – Hostivice

View line Os 19749

Noutonice 09:52 → Hostivice 10:16 Sat, Sun 0 h 24 min · 8 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Hostivice at 10:16 −3 min

  1. Noutonice09:52
  2. Tuchoměřice09:55
  3. Středokluky09:58
  4. Dobrovíz-Amazon10:06
  5. Hostouň u Prahy10:08
  6. Jeneč zastávka10:11
  7. Hostivice10:16

Next service: Saturday 09:52 from Noutonice · Sat 14 Nov

Next departure 09:52 Saturday · Noutonice
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 10 full · 0 partial · 1 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 25 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sun 1 Nov Max en route +11 min · last fix heading to Hostivice +10 min
  • Sat 3 Oct Max en route +7 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 4% · 1
  • On time 88% · 22
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 92% S n=12
  • 92% S n=12

Stops and timetable

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

Last 90 days, 25 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
09:52on time +1 min
09:55≈ on time ≈ +1 min
09:58 / 10:01≈ on time ≈ +1 min
10:05≈ on time ≈ +1 min
10:06≈ on time ≈ +1 min
10:08≈ on time ≈ +1 min
10:11≈ on time ≈ +1 min
10:16on 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
Sun 8 NovHostivice 10:19−3 min+2 min
Sat 7 NovHostivice 10:190 min—
Sun 1 NovHostivice 10:30+10 min+11 min
Sat 31 OctHostivice 10:23+2 min+2 min
Wed 28 OctHostivice 10:18No data—
Sun 25 OctHostivice 10:210 min+3 min
Sat 24 OctHostivice 10:200 min+2 min
Sun 18 OctHostivice 10:20−1 min+2 min
Sat 17 OctHostivice 10:210 min+1 min
Sun 11 OctHostivice 10:200 min+1 min
Sat 10 OctHostivice 10:21+1 min+2 min
Sun 4 Oct— 10:30−1 min—
Sat 3 Oct— 10:37+7 min+7 min
Mon 28 Sept— 10:310 min—
Sun 27 Sept— 10:30−1 min+1 min
Sat 26 Sept— 10:310 min+1 min
Sun 20 Sept— 10:300 min+1 min
Sat 19 Sept— 10:310 min—
Sun 13 Sept— 10:310 min+1 min
Sat 12 Sept— 10:310 min+2 min
Sun 6 Sept— 10:300 min—
Sat 5 Sept— 10:310 min+2 min
Sun 30 Aug— 10:310 min+1 min
Sat 29 Aug— 10:310 min+1 min
Sun 16 Aug— 10:310 min—
Sat 15 Aug— 10:310 min—