BETCRYPTO
Ended

Makienko Mykhailo vs Kovalchuk Oleksandr

Starts:Aug 24, 2026, 4:25 AMEnds:Aug 31, 2026, 4:25 AM
AZRGMIKSHLMTNVGPLYPMU
AbandonedNo venue reported a result for this event, so it was closed without one. Paper positions were refunded at cost.
Sports favorite hit rate72.3% (140,236)
Total volume
—
Largest spread
—
Outcomes
2
Platforms
2
Markets
1

Markets

Every market on this event, moneyline first. Select one to compare it across platforms in the side panel.

Makienko Mykhailo
PolymarketNo liquidity50.0%
Kovalchuk Oleksandr
PolymarketNo liquidity50.0%

Dimmed prices were last confirmed too long ago for the state of this event (in play, before the game, or long-dated) and are left out of consensus, best price and spread.

Description from Polymarket. A cross-platform summary is generated once this event is matched across platforms.

This market refers to the table tennis match between Makienko Mykhailo and Kovalchuk Oleksandr in Setka Cup Ukraine Men, scheduled for August 24 at 12:25AM ET. This market will resolve to 'Makienko Mykhailo' if Makienko Mykhailo wins against Kovalchuk Oleksandr. This market will resolve to 'Kovalchuk Oleksandr' if Kovalchuk Oleksandr wins against Makienko Mykhailo. If the match is canceled (not played at all), ends in a tie, or is delayed beyond 7 days from the scheduled date without a winner determined, this market will resolve to 50-50. If the match begins but is not completed, and one player advances due to the opponent's retirement, default, or disqualification, this market will resolve to the player who advances. If the match ends in a walkover (player withdraws before the start and the other advances automatically), this market will resolve to 50-50. The primary resolution source for this market is the official statistics of the event as recognized by the governing body or event organizers. However, if the governing body or event organizers have not published final match statistics within 2 hours after the event's conclusion, a consensus of credible reporting may be used instead.

Discussion (0)

Log in to join the discussion.

No comments yet — start the discussion.