This market refers to the table tennis match between Lutsyshyn Oleh and Pytsko Ivan in Setka Cup Ukraine Men, scheduled for August 21 at 4:15PM ET.
This market will resolve to 'Lutsyshyn Oleh' if Lutsyshyn Oleh wins against Pytsko Ivan.
This market will resolve to 'Pytsko Ivan' if Pytsko Ivan wins against Lutsyshyn Oleh.
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.
Lutsyshyn Oleh vs. Pytsko Ivan
Game context
Ivan Pytsko holds the edge in trader sentiment for this Setka Cup men's singles clash due to stronger recent results in the Ukrainian domestic circuit and a favorable head-to-head record against Oleh Lutsyshyn. Pytsko has secured multiple straight-set victories in the tournament while showing resilience in extended rallies and service games, though a recent five-set loss highlights vulnerability to consistent opponents. Lutsyshyn has posted competitive wins, including a 3-1 result over Ihor Kvak, but trails in direct matchups that often hinge on narrow point margins. Both players compete in a fast-paced format where set totals and momentum shifts from early breaks frequently decide outcomes, with the upcoming encounter featuring no reported injuries or withdrawals. Historical patterns in similar Setka Cup fixtures underscore how home-table familiarity and recent match volume can influenc
