This week, the World Series of Poker revealed its new page dedicated to the 2022 WSOP Player of the Year leaderboard.
Let’s remember last year’s WSOP POY race. It won’t be that tough, since it wrapped less than six months ago. It was the post-pandemic 2021 WSOP, and it was different than in pre-pandemic times. The Player of the Year leaderboard did not include WSOP Europe or WSOP online events.
It was also different in that it created two POY categories. One represented the entirety of the Las Vegas WSOP and found Josh Arieh as the winner. (He won $15K.) The other was the No Limits Velo leaderboard, one that calculated points only for No Limit Hold’em events. Scott Ball won that event for the overall prize of $15K.
This year, there are more changes.
One POY Leaderboard
The 2022 WSOP Player of the Year race will consist of one single leaderboard. Here’s what it will not include:
-WSOP Europe bracelet event results-WSOP.com bracelet event results in Michigan-WSOP.com bracelet event results in Pennsylvania-Casino Employees event results-Tag Team event results-Ladies event results-Seniors and Super Seniors event results
It will include the other WSOP live bracelet events happening at Bally’s and Paris. It will also figure in points for wins on WSOP.com but only for players competing in the shared Nevada/New Jersey events.
Another change is that the cash put up for last year’s top three finishes on both leaderboards is gone. The prize this year is reserved for the winner only, and it is:
-2023 WSOP Main Event seat ($10K value)-Unique trophy-Player of the Year banner at Paris/Bally’s
The rules for the points to be awarded are here.
To calculate the points to be awarded in any particular WSOP event, simply go to this WSOP POY page and use the points calculator.
At this point, there is no word on a possible WSOP Europe leaderboard or if non-US events will be included again in the future. For now, the WSOP POY will be a United States-based awards system.
https://twitter.com/Kevmath/status/1529209738084376585?s=20&t=D7hME_cLL4yXZXFA7VBbnQ
Comments