TOTAL VOLUME:
$134.1b
24H VOL:
$133,388,117
24H TRANSACTIONS:
2,388,728,490
OPEN INTEREST:
$1,436,095,462
405,232
Markets across
30,526
events
MATCHED EVENTS:
2,693
PLATFORM COVERAGE:
5
Polymarket:
39%
VS.
Kalshi:
61%
Closed: Jul 19, 5:30 AM EST
Polymarket
This market refers to which team's player records the highest individual run total in the cricket match between Derbyshire and Leicestershire scheduled for 2026-07-12 in T20 Blast. This market resolves according to the finalized match statistics as published by https://www.espncricinfo.com/. The outcome corresponding to Derbyshire will be considered correct if the highest individual score in the match is recorded exclusively by a player from Derbyshire. The outcome corresponding to Leicestershire will be considered correct if the highest individual score is recorded exclusively by a player from Leicestershire. If the highest individual score is shared by at least one player from each team, the market will resolve to Draw. The market will resolve according to which team's player records the highest individual run total regardless of if the match is not competed (e.g. Due to weather conditions). DLS/DRS adjustments and any other on-field rulings affecting batting statistics are treated as ordinary data. If the match is permanently canceled, abandoned, or otherwise completed without official batting statistics being recorded, the market will resolve Draw. If the match is postponed or rescheduled, the market remains open until the listed fixture is completed and official statistics are available.
This market refers to which team's player records the highest individual run total in the cricket match between Derbyshire and Leicestershire scheduled for 2026-07-12 in T20 Blast. This market resolves according to the finalized match statistics as published by https://www.espncricinfo.com/. The outcome corresponding to Derbyshire will be considered correct if the highest individual score in the match is recorded exclusively by a player from Derbyshire. The outcome corresponding to Leicestershire will be considered correct if the highest individual score is recorded exclusively by a player from Leicestershire. If the highest individual score is shared by at least one player from each team, the market will resolve to Draw. The market will resolve according to which team's player records the highest individual run total regardless of if the match is not competed (e.g. Due to weather conditions). DLS/DRS adjustments and any other on-field rulings affecting batting statistics are treated as ordinary data. If the match is permanently canceled, abandoned, or otherwise completed without official batting statistics being recorded, the market will resolve Draw. If the match is postponed or rescheduled, the market remains open until the listed fixture is completed and official statistics are available.
On Polymarket, this market is priced through an automated market maker that adjusts odds based on trader activity and order flow. On Polymarket, prices reflect that venue's order book, liquidity, and how traders price the outcome right now. Each batter outcome is represented as a separate contract, and the combined probability of all outcomes sums to 100 percent. As traders buy or sell shares in a particular player, the price moves inversely to reflect changing conviction. This continuous pricing mechanism ensures that odds remain responsive to new information and participant demand throughout the trading window.
This market resolves around Jul 19, 2026, once the Derbyshire versus Leicestershire T20 Blast match concludes and the final statistics are verified. The outcome is determined by identifying which eligible batter accumulated the highest individual run total during the match. Resolution is confirmed once the result is verifiable from credible public sources, including official match records and league reporting. Early or abandoned matches may trigger alternative resolution rules specific to the platform's policy.
Several factors can shift odds in this market before play begins. Team lineup announcements, injury reports, or late roster changes will immediately reprice batter probabilities based on availability and batting order. Weather forecasts and pitch conditions may favor certain playing styles or aggressive batters. Recent form, head-to-head statistics, and venue-specific performance data also influence trader positioning. Once the match starts, early runs or dismissals of top-ranked batters will trigger rapid repricing as the field of contenders narrows and remaining players' odds increase.