Sp 2051 2051 Letovice – Brno hl. n.

View line Sp 2051

Letovice 05:30 → Brno hl. n. 06:13 Mon, Tue, Wed, Thu, Fri 0 h 43 min · 16 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Brno hl. n. at 06:14 No data

  1. Letovice05:30
  2. Svitávka05:35
  3. Doubravice nad Svitavou05:41
  4. Blansko město05:46
  5. Adamov zastávka05:56
  6. Bílovice nad Svitavou06:04
  7. Brno hl. n.06:13

Next service: tomorrow 05:30 from Letovice · Fri 6 Nov

Next departure 05:30 tomorrow · Letovice
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
83%
33/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Brno 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

  • Fri 18 Sept Max en route +27 min · last fix heading to — +27 min
  • Wed 12 Aug Max en route +21 min · last fix heading to — +21 min
  • Mon 17 Aug Max en route +12 min · last fix heading to — +9 min
  • Fri 4 Sept Max en route +12 min · last fix heading to — +8 min
  • Tue 15 Sept Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 20% · 8
  • On time 63% · 25
  • 3–10 min 13% · 5
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 75% T n=8
  • 88% W n=8
  • 100% T n=8
  • 75% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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:30+2 min +6 min
05:32≈ +2 min ≈ +6 min
05:33≈ +2 min ≈ +6 min
05:35≈ +2 min ≈ +6 min
05:37 / 05:38≈ +2 min ≈ +6 min
05:41≈ +1 min ≈ +6 min
05:43≈ +1 min ≈ +6 min
05:44≈ +1 min ≈ +6 min
05:46 / 05:47≈ +1 min ≈ +6 min
05:49 / 05:51≈ +1 min ≈ +6 min
05:56≈ on time ≈ +5 min
05:57 / 05:58≈ on time ≈ +5 min
06:00≈ on time ≈ +5 min
06:04≈ on time ≈ +4 min
06:08 / 06:09≈ on time ≈ +4 min
06:13on time +4 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
Thu 5 NovBrno hl. n. 06:14No data—
Wed 4 NovBrno hl. n. 06:14No data—
Tue 3 NovBrno hl. n. 06:14No data—
Mon 2 NovBrno hl. n. 06:14No data—
Fri 30 OctBrno hl. n. 06:14No data—
Thu 29 OctBrno hl. n. 06:14No data—
Tue 27 OctBrno hl. n. 06:14No data—
Mon 26 OctBrno hl. n. 06:14No data—
Fri 23 OctBrno hl. n. 06:14No data—
Thu 22 OctBrno hl. n. 06:14No data—
Wed 21 OctBrno hl. n. 06:14No data—
Tue 20 OctBrno hl. n. 06:14No data—
Mon 19 OctBrno hl. n. 06:14No data—
Fri 16 OctBrno hl. n. 06:14No data—
Thu 15 OctBrno hl. n. 06:14No data—
Wed 14 OctBrno hl. n. 06:14No data—
Tue 13 OctBrno hl. n. 06:14No data—
Mon 12 OctBrno hl. n. 06:14No data—
Fri 9 OctBrno hl. n. 06:14No data—
Thu 8 OctBrno hl. n. 06:14No data—
Wed 7 OctBrno hl. n. 06:14No data—
Tue 6 OctBrno hl. n. 06:15No data—
Mon 5 Oct— 06:25−2 min+2 min
Fri 2 Oct— 06:25−3 min+3 min
Thu 1 Oct— 06:30+2 min+6 min
Wed 30 Sept— 06:29+2 min+6 min
Tue 29 Sept— 06:25−2 min—
Fri 25 Sept— 06:27−1 min+2 min
Thu 24 Sept— 06:28+1 min+4 min
Wed 23 Sept— 06:26−1 min+2 min