TT Lossbeater/Setka Cup
Setka CupMatch #13067490
Played Sep 4Finished
Vitalii Khamurda
Home
2.50
At publish
Lost last 1Form at publish
4–6Last 10Lost last 1
Final
3 – 1
Set by set
119118811115––
Spartak Abalmaz
Away
1.50
At publish
Won last 2Form at publish
8–2Last 10Won last 2
The read, and what happenedsealed at 21:58 and never touched — 63.7% is still 63.7%
Graded at full timeSpartak Abalmaz to win
63.7%
63.7%
Sealed before the first serve and never touched. The record is only checkable because of that.
Read
Wrongno pick shipped
How it is goingVitalii Khamurda above · Spartak Abalmaz below
Set 1 · 11-9
Set 2 · 11-8
Set 3 · 8-11
Set 4 · 11-5
Point 74 set 4, 11-5 — our read held Spartak Abalmaz at 63.7%
74 points played in total.
H2H Vitalii Khamurda 23–47 Spartak Abalmaz Vitalii Khamurda has won 23 of their 70 meetings.
The pickNo pick published
Sealed 21:58What took a side5 for · 0 against · 1 silent
SignalWhat it readSideVerdictWhy it voted that way
Market
1.50 (63%)
Abalmaz
Wrong
no bar to clear — a priced side always votes
H2H
23-47 in 70
Abalmaz
Wrong
gap of 24 in 70, over the gap of 2
Rating (G2)
Khamurda 1560 vs Abalmaz 1614
Abalmaz
Wrong
both rated, 54 points apart — no bar to clear
Form (L5)
Khamurda 40% vs Abalmaz 60%
Abalmaz
Wrong
20pp gap, over the 15pp bar
Form (L10)
Khamurda 40% vs Abalmaz 80%
Abalmaz
Wrong
40pp gap, over the 15pp bar
Streak
Khamurda -1 · Abalmaz +2
—
Too close
neither holds a run of 3 on their own
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.
5 for, 1 silent — and still no pick. The gate cuts it all the same.
Signal confidence: 64% — Clear lean (leans Abalmaz)
Decision Summary
Market vs Signals
Market oddsKhamurda 2.50 / Abalmaz 1.50
Signal prob.36% / 64%
Edge (Abalmaz)+1.2pp
Setka Cup · #13067490
Khamurda2.50
40%won 4 of 10 · last 10
oldest → newest
30%takes the first set · 3 of 10
As underdog45% won 74 of 166
Down 0–1, comes back28% 28 of 101
Down 0–2, comes back6% 3 of 54
Abalmaz1.50
80%won 8 of 10 · last 10
Won last 2
oldest → newest70%takes the first set · 7 of 10
As favourite60% won 176 of 296
Up 2–0, closes it94% 80 of 85
Up 1–0, closes it77% 130 of 170
Head to head
H2H window
The recordacross 10 meetings
HomeKhamurda4wins
AwayAbalmaz6wins
2 of 10 to a deciderAbalmaz leads 6–4, and 2 of those 10 went to a fifth set.
First set to match win · in this matchup
HomeKhamurdan = 0, below the 3 needed
AwayAbalmaz60%6 of 10
Set by set, in these 10 meetingsevery set carries its own n — a fifth set only exists when the match reaches one
S1Khamurda0Abalmaz10n = 10Abalmaz took 10 of 10
S2Khamurda7Abalmaz3n = 10Khamurda took 7 of 10
S3Khamurda3Abalmaz7n = 10Abalmaz took 7 of 10
S4Khamurda3Abalmaz4n = 7Abalmaz took 4 of 7
S5
Only 2 matches reached it — below the 3 needed to publish a rate
How those 10 finishedcounts, and the six add up to 10 — a scoreline is a name, not a code
3–0Straight, home00%
3–1Four sets, home220%
3–2Decider, home220%
2–3Decider, away00%
1–3Four sets, away330%
0–3Straight, away330%
These 10 meetings
MetricKhamurdaAbalmazK − ABasisWins46−2in 10 meetingsFirst set010−10of 10Avg pointsper match36.339.5−3.2per matchSweeps03−33–0 or 0–3
Career, not this matchup
MetricKhamurdaAbalmazBasisWin rate · lifetime461 / 878 vs 425 / 83352.5%51%461 / 878 vs 425 / 833Avg sets wonper match2.02.0per matchAvg pointsper match37.038.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
AbalmazKhamurda 2.50/Abalmaz 1.50
Read onlywould have missed
What we said
63.7%
Abalmaz · sealed before the serve
What happened
3–1
Khamurda won
Recent Results
H2H · no odds on record10
LSep 1 · 24:25V. Khamurda—8111091S. Abalmaz—11512113
WAug 31 · 02:25V. Khamurda—91111113S. Abalmaz—117981
WAug 28 · 15:05V. Khamurda—3111114133S. Abalmaz—1191312112
LAug 27 · 21:55V. Khamurda—1011781S. Abalmaz—12911113
LAug 25 · 21:05V. Khamurda—9890S. Abalmaz—1111113
WAug 24 · 23:55V. Khamurda—1011119113S. Abalmaz—12541192
LAug 20 · 21:55V. Khamurda—5690S. Abalmaz—1111113
LAug 18 · 21:05V. Khamurda—711481S. Abalmaz—11811113
WAug 18 · 02:25V. Khamurda—121112123S. Abalmaz—14710101
LAug 14 · 24:25V. Khamurda—4880S. Abalmaz—1111113
V. Khamurda10
WSep 4 · 03:25V. Khamurda1.61117111113R. Gnoevoy2.2091131182WSep 4 · 01:55V. Khamurda2.001311113O. Naida1.7311830LSep 3 · 22:55V. Khamurda1.91117681D. Derevynskyi1.8081111113WSep 3 · 21:25V. Khamurda1.8391111113T. Ponomarenko1.83118261WSep 2 · 03:25V. Khamurda3.4011114113V. Panasenko1.30771161LSep 2 · 01:55V. Khamurda1.7341270R. Gnoevoy2.001114113LSep 2 · 24:25V. Khamurda2.509990S. Abalmaz1.501111113LSep 1 · 22:55V. Khamurda1.73711691T. Ponomarenko2.0011911113LSep 1 · 21:25V. Khamurda1.805101171S. Skachenko1.9111126113WSep 1 · 03:25V. Khamurda1.73691111113T. Ponomarenko2.0011117782
S. Abalmaz10
LSep 4 · 04:25S. Abalmaz2.108760D. Derevynskyi1.671111113WSep 4 · 02:25R. Gnoevoy1.91121191172S. Abalmaz1.801051113113WSep 3 · 23:25S. Abalmaz1.571111143T. Ponomarenko2.2555120WSep 3 · 22:25O. Naida2.757660S. Abalmaz1.401111113LSep 2 · 04:25S. Abalmaz1.4471180T. Ponomarenko2.631113113LSep 2 · 02:25V. Panasenko1.801111113S. Abalmaz1.917180WSep 2 · 24:25V. Khamurda2.509990S. Abalmaz1.501111113WSep 1 · 23:25S. Abalmaz1.911011116113S. Skachenko1.8012951192WSep 1 · 22:25R. Gnoevoy1.915670S. Abalmaz1.801111113WSep 1 · 04:25S. Abalmaz2.2011811123D. Derevynskyi1.617118101
Upcoming Matches
V. Khamurda
S. Abalmaz
Event Chatroom
This room is closed. Messages clear 24 hours after they are sent.