# Live poker tournament chip counts and payouts, since 2025

**Train tournament equity models on live poker events as PokerNews reports them, from 2025 onward.** Every end-of-day chip count PokerNews publishes for the World Series of Poker, WSOP Europe, the European Poker Tour, RunGood and other live tours comes with the blind level, the event's payout list and each entry's final place and prize, flattened into one row per player per snapshot for machine l…

Live poker tournament chip counts and payouts, since 2025 is an open, machine-readable dataset published on Mostly Right as immutable Parquet versions, with a documented column schema, a JSON query API and a direct download. Its first rows are free to read and it is open to AI agents.

## Facts

- Slug: `live-poker-tournament-chip-counts-and-payouts-2025`
- Canonical page: https://mostlyright.md/datasets/live-poker-tournament-chip-counts-and-payouts-2025
- Publisher: mostlyrightmd (https://mostlyright.md/publishers/mostlyrightmd)
- Published: 2026-09-23T10:22:25.752Z
- Tables: 1
- Formats: Apache Parquet (download), JSON (query and sample)
- Cost: the first 500 rows of each table are free to everyone; querying and downloading need a free account and count against a monthly free allowance unless the workspace is subscribed
- Metadata API: `GET https://mostlyright.md/api/v2/public/datasets/live-poker-tournament-chip-counts-and-payouts-2025`
- Topics: poker, poker tournaments, independent chip model, chip counts, pokernews, live reporting

## How to use it

1. Read a table's schema — no account needed.
2. Fetch its published sample rows — no account needed.
   The first 500 rows of every table, in stored order, are free to everyone, with or without an account. Without an account you get that sample and nothing else: no filter, sort, search, download or page past row 500.
3. Sign in at https://mostlyright.md/login, connect this dataset to a workspace on its page, and create an `mr_use_` key.
4. Query bounded JSON, or download the complete Parquet snapshot and read it locally.
   A free workspace may read 100,000 rows and run 1,000 queries a UTC month past the sample. The allowance is shared by everyone in the workspace, and a free workspace may have any number of members. Reads count against the workspace whose data or key they use. A subscribed workspace is never counted, for anyone working in it.

Agents can do all of this over MCP at `https://mostlyright.md/api/mcp` — searching, reading schemas and sampling rows work with no credential at all.

## Table: live_tournament_snapshots

- Table id: `a5d62b87-0b3e-49eb-94a8-f80b2bbc5859`
- Slug: `live-tournament-snapshots`
- Immutable version: `ad098885-252a-5c53-9fd9-e6f92fb8c6b6`
- Schema: `GET https://mostlyright.md/api/v2/public/tables/a5d62b87-0b3e-49eb-94a8-f80b2bbc5859/schema`
- Sample rows, no key: `GET https://mostlyright.md/api/v2/public/tables/a5d62b87-0b3e-49eb-94a8-f80b2bbc5859/preview`
- Bounded JSON query: `POST https://mostlyright.md/api/v2/public/tables/a5d62b87-0b3e-49eb-94a8-f80b2bbc5859/query` with `x-api-key: mr_use_…`
- Full Parquet snapshot: `GET https://mostlyright.md/api/v2/public/tables/a5d62b87-0b3e-49eb-94a8-f80b2bbc5859/current` with `x-api-key: mr_use_…` (application/vnd.apache.parquet)

### Columns (71)

| Column | Type | Description |
| --- | --- | --- |
| `event_key` | string | The PokerNews event path: tour, festival and event slugs joined by slashes. |
| `day_slug` | string | The event day as PokerNews names it, such as day1a or day2abc. |
| `entry_id` | string | PokerNews's identifier for this player's entry in the event; the payout list uses the same identifier. |
| `tour` | string | The PokerNews tour slug, such as wsop, ept or rungood-poker-series. |
| `festival` | string | The festival slug within the tour. |
| `event_slug` | string | The event slug, which carries the buy-in and event name. |
| `series_year` | integer | The year the festival or event name states, taken from the event's page title where the slug states none; empty when neither does. |
| `day_number` | integer | The day number read from the day slug. |
| `profile_id` | string | PokerNews's global player profile identifier, when the player has one. |
| `player_name` | string | The player as PokerNews lists them. |
| `country_code` | string | The player's two-letter country code. |
| `chips` | integer | The player's stack at the end of the day, in tournament chips. |
| `stack_bb` | integer | The player's stack in big blinds as PokerNews reports it; empty when the page gives none. |
| `big_blind` | integer | The big blind at the end of the day, estimated as the median of chips divided by stack in big blinds. |
| `self_reported` | boolean | True when the player submitted the count through PokerNews's MyStack app rather than a reporter recording it. |
| `players_left` | integer | The number of players holding chips in this end-of-day snapshot. |
| `snapshot_chips_total` | integer | The total of every stack listed in this snapshot. |
| `event_chips_max` | integer | The largest chip total listed on any day of the event. |
| `chip_coverage` | decimal | The snapshot's chip total divided by the event's largest listed total. |
| `field_complete` | boolean | True when the snapshot lists at least 97 percent of the event's largest chip total. |
| `chip_share` | decimal | The player's chips divided by the snapshot's chip total. |
| `stack_rank` | integer | The player's position by stack within the snapshot, 1 being the chip leader. |
| `currency` | string | The currency of the event's payouts, as an ISO code where the symbol is unambiguous. |
| `places_paid` | integer | The number of places on the event's payout list. |
| `prize_pool` | integer | The sum of the event's listed payouts. For bounty events it leaves out the bounty share of the pool, so it can be well under printed_prize_pool. |
| `entries` | integer | Total entries, re-entries included, as the event's Event Info panel prints it; empty where the page prints none. |
| `buyin` | integer | The buy-in as a number, in the payout currency, from the Event Info panel. |
| `printed_prize_pool` | integer | The prize pool the Event Info panel prints, which includes any bounty share. |
| `ladder_pool_share` | decimal | prize_pool divided by printed_prize_pool: about 1 when the payout list is the whole pool, lower for bounty events or a partly listed ladder. |
| `paid_fraction` | decimal | places_paid divided by entries: the share of the field that gets paid. |
| `min_cash` | integer | The payout for the last paid place. |
| `first_prize` | integer | The payout for first place. |
| `prize_remaining` | integer | The total payout for places 1 through players_left. |
| `next_payout` | integer | The payout for finishing in place players_left, 0 before the money. |
| `in_the_money` | boolean | True when every player left is guaranteed a payout. |
| `final_place` | integer | The place this entry finished in, from the payout list. |
| `final_prize` | integer | The prize this entry won, from the payout list. |
| `label_status` | string | known when the entry is on the payout list, pending while the event has no named winner, assumed_zero when the finished event does not pay this entry and the s… |
| `final_prize_filled` | integer | The prize when known, 0 when assumed_zero, empty otherwise. |
| `final_prize_share` | decimal | final_prize_filled divided by prize_remaining. |
| `buyin_text` | string | The buy-in as the event's own page title prints it, currency symbol included. |
| `game` | string | The game: read from the event name where it states one, otherwise decided by a model from the event's printed title, and 'unknown' when neither is confident. |
| `game_source` | string | Where `game` came from: event_name, model, or unknown. |
| `game_confidence` | decimal | The model's score for `game`, present only on rows the model decided. |
| `served_model` | string | The dated model snapshot that answered, present only on rows the model decided. |
| `is_bounty` | boolean | True for bounty, mystery bounty, PKO and knockout events. |
| `is_turbo` | boolean | True for turbo events. |
| `is_team_event` | boolean | True for team events. |
| `is_heads_up_or_shootout` | boolean | True for heads-up and shootout events. |
| `is_restricted_field` | boolean | True for ladies, seniors and similar restricted fields. |
| `field_share_1` | decimal | Chip share of the number 1 stack in the snapshot. |
| `field_share_2` | decimal | Chip share of the number 2 stack in the snapshot. |
| `field_share_3` | decimal | Chip share of the number 3 stack in the snapshot. |
| `field_share_4` | decimal | Chip share of the number 4 stack in the snapshot. |
| `field_share_5` | decimal | Chip share of the number 5 stack in the snapshot. |
| `field_share_6` | decimal | Chip share of the number 6 stack in the snapshot. |
| `field_share_7` | decimal | Chip share of the number 7 stack in the snapshot. |
| `field_share_8` | decimal | Chip share of the number 8 stack in the snapshot. |
| `field_share_9` | decimal | Chip share of the number 9 stack in the snapshot. |
| `field_share_10` | decimal | Chip share of the number 10 stack in the snapshot. |
| `payout_share_1` | decimal | Prize for place 1 as a share of the prize pool. |
| `payout_share_2` | decimal | Prize for place 2 as a share of the prize pool. |
| `payout_share_3` | decimal | Prize for place 3 as a share of the prize pool. |
| `payout_share_4` | decimal | Prize for place 4 as a share of the prize pool. |
| `payout_share_5` | decimal | Prize for place 5 as a share of the prize pool. |
| `payout_share_6` | decimal | Prize for place 6 as a share of the prize pool. |
| `payout_share_7` | decimal | Prize for place 7 as a share of the prize pool. |
| `payout_share_8` | decimal | Prize for place 8 as a share of the prize pool. |
| `payout_share_9` | decimal | Prize for place 9 as a share of the prize pool. |
| `payout_share_10` | decimal | Prize for place 10 as a share of the prize pool. |
| `fetched_at` | timestamp_utc | When the page holding this row was fetched. |

## Citing this dataset

Cite the dataset by name and canonical URL (https://mostlyright.md/datasets/live-poker-tournament-chip-counts-and-payouts-2025), the table, and the immutable `version_id` the rows came from. A query response carries `table.version_id` and `table.content_digest`; a download carries a strong ETag and a `Content-Digest` header.