TT Lossbeater/Czech Liga Pro
Czech Liga ProMatch #12475603
Played Aug 23Finished
David Vavrecka
Home
1.80
At publish
Lost last 3Form at publish
2–8Last 10Lost last 3
Final
2 – 3
Set by set
7111181210711611
Zdenek Luksa
Away
1.91
At publish
Lost last 1Form at publish
3–7Last 10Lost last 1
The read, and what happenedsealed at 13:29 and never touched — 56.9% is still 56.9%
Graded at full timeZdenek Luksa to win
56.9%
56.9%
Sealed before the first serve and never touched. The record is only checkable because of that.
Read
Rightno pick shipped
«Right» is not «we won». No pick was shipped, so this is a read that turned out correct — not a call that won.
How it is going
Point-by-point unavailable
BetsAPI did not publish a timeline for this match.
94 points played in total.
Set by set
7111181210711611
H2H David Vavrecka 4–5 Zdenek Luksa David Vavrecka has won 4 of their 9 meetings.
The pickNo pick published
Sealed 13:29What took a side2 for · 2 against · 2 silent
SignalWhat it readSideVerdictWhy it voted that way
Market
1.80 (51%)
Vavrecka
Wrong
no bar to clear — a priced side always votes
H2H
4-5 in 9
—
Too close
gap of 1, under the gap of 2
Rating (G2)
Vavrecka 1185 vs Luksa 1221
Luksa
Correct
both rated, 36 points apart — no bar to clear
Form (L5)
Vavrecka 20% vs Luksa 40%
Luksa
Correct
20pp gap, over the 15pp bar
Form (L10)
Vavrecka 20% vs Luksa 30%
—
Too close
10pp gap, under the 15pp bar
Streak
Vavrecka -3 · Luksa -1
Vavrecka
Wrong
one crossed 3 in a row, the other did not
Not whether we were right, but which read failed. One match proves nothing — the calibration is the aggregate of rows like these, and that aggregate does not exist yet.
This table lists the interface catalogue — the one you already see in ALIGN / CONFLICT. The engine weighs its own subset, and they are not the same set. It says so here instead of hiding it.
2 for, 2 silent — and still no pick. The gate cuts it all the same.
Signal confidence: 54% — Coin-flip (leans Luksa) · live re-read · sealed at 57% before the first serve
Decision Summary
Why this prediction
- Luksa form (40%) is below what odds imply (52%)
Market vs Signals
Market oddsVavrecka 1.80 / Luksa 1.91
Signal prob.46% / 54%
Edge (Luksa)+5.5pp
Czech Liga Pro · #12475603
Vavrecka1.80
20%won 2 of 10 · last 10
Lost last 3
oldest → newest20%takes the first set · 2 of 10
As favourite61% won 17 of 28
Up 2–0, closes it90% 9 of 10
Up 1–0, closes it69% 11 of 16
Luksa1.91
30%won 3 of 10 · last 10
oldest → newest
20%takes the first set · 2 of 10
As underdog42% won 21 of 50
Down 0–1, comes back24% 8 of 34
Down 0–2, comes back5% 1 of 19
Head to head
H2H window
The recordacross 9 meetings
HomeVavrecka4wins
AwayLuksa5wins
3 of 9 to a deciderLuksa leads 5–4, and 3 of those 9 went to a fifth set.
First set to match win · in this matchup
HomeVavrecka75%3 of 4
AwayLuksa80%4 of 5
Set by set, in these 9 meetingsevery set carries its own n — a fifth set only exists when the match reaches one
S1Vavrecka4Luksa5n = 9Luksa took 5 of 9
S2Vavrecka4Luksa5n = 9Luksa took 5 of 9
S3Vavrecka5Luksa4n = 9Vavrecka took 5 of 9
S4Vavrecka4Luksa2n = 6Vavrecka took 4 of 6
S5Vavrecka1Luksa2n = 3Luksa took 2 of 3
How those 9 finishedcounts, and the six add up to 9 — a scoreline is a name, not a code
3–0Straight, home222%
3–1Four sets, home111%
3–2Decider, home111%
2–3Decider, away222%
1–3Four sets, away222%
0–3Straight, away111%
These 9 meetings
MetricVavreckaLuksaV − LBasisWins45−1in 9 meetingsFirst set45−1of 9Avg pointsper match39.138.4+0.7per matchSweeps21+13–0 or 0–3
Career, not this matchup
MetricVavreckaLuksaBasisWin rate · lifetime54 / 117 vs 44 / 9546.2%46.3%54 / 117 vs 44 / 95Avg sets wonper match1.91.9per matchAvg pointsper match35.537.2per match
Deep Dive by Market
Each market builds on the overview aboveForecast
History
Forecastthe model predicts this marketHistorythis is what the H2H did — no prediction
Match Winner
LuksaVavrecka 1.80/Luksa 1.91
Read onlywould have hit
What we said
54%
Luksa · sealed before the serve
What happened
2–3
Luksa won
Recent Results
H2H · no odds on record9
WAug 10 · 06:00D. Vavrecka—1112113Z. Luksa—81070
LAug 9 · 08:59D. Vavrecka—7101141Z. Luksa—11126113
LAug 9 · 06:30D. Vavrecka—11911101Z. Luksa—91113123
LMay 1 · 17:30D. Vavrecka—101080Z. Luksa—1212113
WMay 1 · 15:30D. Vavrecka—1111113Z. Luksa—8760
WApr 25 · 21:30D. Vavrecka—4111111113Z. Luksa—11713942
WApr 25 · 19:00D. Vavrecka—15149113Z. Luksa—13121161
LMar 7 · 19:00D. Vavrecka—98111162Z. Luksa—111187113
LMar 1 · 16:30D. Vavrecka—96111152Z. Luksa—111158113
D. Vavrecka10
LSep 6 · 13:00I. Kolenciak1.8311711113D. Vavrecka1.83411851LSep 6 · 12:00I. Kolenciak2.00412411113D. Vavrecka1.73111011892LSep 6 · 11:00A. Kanak1.6711711173D. Vavrecka2.108112151LSep 6 · 10:30D. Vavrecka1.8011971192I. Palmi1.91811117113LAug 29 · 20:59D. Vavrecka1.53111081122M. Stolba2.38612115113LAug 29 · 20:00M. Blaha2.00671111113D. Vavrecka1.7311116462WAug 29 · 19:00M. Stolba2.20571191D. Vavrecka1.6111115113LAug 29 · 18:30D. Vavrecka1.7311961342A. Kanak2.003111111113WAug 27 · 13:30Z. Luksa1.536880D. Vavrecka2.201111113WAug 27 · 12:30M. Stolba2.20151111762D. Vavrecka1.61177911113
Z. Luksa10
LAug 27 · 13:30Z. Luksa1.536880D. Vavrecka2.201111113LAug 27 · 12:00M. Blaha1.83911119113Z. Luksa1.8311971192WAug 27 · 11:00M. Stolba1.67611261Z. Luksa2.1011911113WAug 27 · 10:30Z. Luksa1.6712711113D. Vavrecka2.101011791WAug 23 · 09:30J. Toth2.63711331Z. Luksa1.4411711113WAug 23 · 07:00A. Kanak1.75121330Z. Luksa1.851415113LAug 23 · 06:30Z. Luksa1.4091171182J. Toth2.75115118113LAug 10 · 08:58J. Toth3.5091111113Z. Luksa1.28117941WAug 10 · 08:30Z. Luksa1.25751111113J. Toth3.7511118672LAug 10 · 07:00Z. Luksa1.80541261R. Adamczyk1.91111110113
Event Chatroom
This room is closed. Messages clear 24 hours after they are sent.