Completed Match 100% chance. Wuhan Tennis Open: Kimberly Birrell vs Katie Volynets — live odds, $427K volume, resolves 2026-10-20. Trade on PredyX.
| Outcome | Probability | 24h change | Volume |
|---|---|---|---|
| Completed Match | 100% | 0.0% | — |
| Wuhan Tennis Open: Kimberly Birrell vs Katie Volynets Total Sets: O/U 2.5 | 100% | 0.0% | — |
| Wuhan Tennis Open: Kimberly Birrell vs Katie Volynets Game Spread +/-2.5 | 100% | 0.0% | — |
| Wuhan Tennis Open: Kimberly Birrell vs Katie Volynets Match O/U 22.5 | 100% | 0.0% | — |
| Wuhan Tennis Open: Kimberly Birrell vs Katie Volynets Set 2 O/U 8.5 | 91% | 0.0% | — |
| Wuhan Tennis Open: Kimberly Birrell vs Katie Volynets Set 2 O/U 9.5 | 91% | 0.0% | — |
| Wuhan Tennis Open: Kimberly Birrell vs Katie Volynets Set 2 O/U 10.5 | 91% | 0.0% | — |
| Wuhan Tennis Open: Kimberly Birrell vs Katie Volynets Set Handicap +/-1.5 | 0% | 0.0% | — |
| Wuhan Tennis Open: Kimberly Birrell vs Katie Volynets Set 2 Winner | 0% | 0.0% | — |
This market refers to the tennis match between Kimberly Birrell and Katie Volynets in the Wuhan Tennis Open, originally scheduled for October 12, 2026 at 10:00PM ET. This market will resolve to "Yes" if all games and sets required to determine a match winner under governing body or event organizer rules are played to completion through normal play. Otherwise, if the match is not completed for any reason, it will resolve to "No." If a forfeit of any kind occurs, including but not limited to a walkover or retirement, this market will resolve "No." If the match is canceled (not played at all), ends in a tie, or a winner has not been determined by October 26, 2026, 11:59 PM ET (14 days after the scheduled start), this market will resolve to "No." 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.