TOTAL VOLUME:

$134.2b

24H VOL:

$126,324,530

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,434,646,834

406,019

Markets across

30,401

events

MATCHED EVENTS:

2,689

PLATFORM COVERAGE:

5

Polymarket:

39%

VS.

Kalshi:

61%

BETA
Dashboards
Tour
All
Sports
WTT - Men's Singles: Sora Matsushima vs Felix Lebrun
polymarket

WTT - Men's Singles: Sora Matsushima vs Felix Lebrun

Volume:
N/A

WTT - Men's Singles: Sora Matsushima vs Felix Lebrun

 - Polymarket

WTT - Men's Singles: Sora Matsushima vs Felix Lebrun - Polymarket

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 18, 2026

Closed: Mar 21, 11:00 PM EST

polymarket

Polymarket

View
Outcome
Trade
Chance %
Price
Spread
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
polymarket

WTT - Men's Singles: Sora Matsushima vs Felix Lebrun

View
0%
Yes 0¢No 100¢
—
N/A
N/A
N/A
N/A
N/A
Settled
Yes
Total markets: 1

Description

This market refers to the table tennis match between Sora Matsushima and Felix Lebrun in a WTT event, scheduled for March 14 at 11:00PM ET. This market will resolve to 'Matsushima' if Sora Matsushima wins against Felix Lebrun. This market will resolve to 'Lebrun' if Felix Lebrun wins against Sora Matsushima. 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.