Os 15807 15807 Poříčany – Nymburk hl. n.

View line Os 15807

Poříčany 05:33 → Nymburk hl. n. 05:56 Mon, Tue, Wed, Thu, Fri 0 h 23 min · 7 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Nymburk hl. n. at 05:56 0 min

  1. Poříčany05:33
  2. Třebestovice05:36
  3. Třebestovice05:37
  4. Sadská05:40
  5. Hořátev05:46
  6. Nymburk město05:51
  7. Nymburk hl. n.05:56

Next service: tomorrow 05:33 from Poříčany · Tue 10 Nov

Next departure 05:33 tomorrow · Poříčany
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
98%
60/61 runs under 3 min
RT coverage: 61 full · 0 partial · 0 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 Nymburk hl. n., in minutes. One bar per run.

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

Worst days

  • Mon 21 Sept Max en route +10 min · last fix heading to — +9 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 61 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
05:33on time on time
05:36≈ on time ≈ on time
05:37≈ on time ≈ on time
05:40 / 05:42≈ on time ≈ on time
05:46≈ on time ≈ +1 min
05:51 / 05:52≈ on time ≈ +1 min
05:56on 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 NovNymburk hl. n. 05:590 min+1 min
Fri 6 NovNymburk hl. n. 05:58+1 min+1 min
Thu 5 NovNymburk hl. n. 05:59+1 min+1 min
Wed 4 NovNymburk hl. n. 05:590 min+1 min
Tue 3 NovNymburk hl. n. 06:00+1 min+1 min
Mon 2 NovNymburk hl. n. 05:590 min+1 min
Fri 30 OctNymburk hl. n. 06:01+1 min+2 min
Thu 29 OctNymburk hl. n. 05:57+1 min+1 min
Tue 27 OctNymburk hl. n. 05:59−1 min—
Mon 26 OctNymburk hl. n. 06:000 min—
Fri 23 OctNymburk hl. n. 06:000 min+1 min
Thu 22 OctNymburk hl. n. 05:57−1 min—
Wed 21 OctNymburk hl. n. 06:000 min+1 min
Tue 20 OctNymburk hl. n. 05:59−1 min+1 min
Mon 19 OctNymburk hl. n. 05:580 min+1 min
Fri 16 OctNymburk hl. n. 05:570 min—
Thu 15 OctNymburk hl. n. 05:58+1 min+1 min
Wed 14 OctNymburk hl. n. 06:010 min+1 min
Tue 13 OctNymburk hl. n. 06:010 min—
Mon 12 OctNymburk hl. n. 06:000 min+2 min
Fri 9 OctNymburk hl. n. 06:00−1 min—
Thu 8 OctNymburk hl. n. 06:000 min+2 min
Wed 7 OctNymburk hl. n. 06:000 min+1 min
Tue 6 OctNymburk hl. n. 05:580 min—
Mon 5 Oct— 06:12+1 min+1 min
Fri 2 Oct— 06:100 min+1 min
Thu 1 Oct— 06:09−1 min—
Wed 30 Sept— 06:09−1 min—
Tue 29 Sept— 06:100 min+2 min
Fri 25 Sept— 06:100 min—