Polymarket trader data per wallet, built from the order fills and market results we decode from Polygon. Each fill is counted once, under the wallet whose order it was, and rolled up by day and by resolved market. The PnL table marks every position to the market's result, so you get profit or loss per wallet without rebuilding positions from 2 billion fills.
Most buyers start with a leaderboard: sum Volume_Usd or Realized_Pnl_Usd by Wallet. Volume and profit point at different wallets, as the busiest ones are often market makers. All amounts are valued at $1 per unit of collateral, and parlays appear in the daily table from 10 November 2026.
Use cases
Leaderboards of Polymarket wallets by volume, fills or fees paid
Picking wallets to follow for a copy-trading bot, ranked by profit across many markets
Profit and loss per wallet on one market or one event, such as an election
Maker and taker behaviour, Up or Down bots and parlay activity per wallet
2 tables
45 columns · free sample for each table
polymarket_wallet_daily
24 columns
One row per wallet per UTC day with an order filled: fills, volume, fees, parlay and Up or Down share, and the day's biggest market.
matic/polymarket-traders/polymarket_wallet_daily<YYYY-MM-DD>.parquetone file per day
polymarket_wallet_daily24 columnsOne row per wallet per UTC day with an order filled: fills, volume, fees, parlay and Up or Down share, and the day's biggest market.
ColumnTypeDescription
Block1
Block_DateDateUTC day of the fills.
Other3
WalletStringPolymarket wallet (the proxy wallet that holds positions) that placed the orders, 0x-hex.
FillsUInt64Order fills this wallet's own orders received that day, makers and takers counted once each.
MarketsUInt64Distinct markets (condition ids) the wallet traded that day.
Taker2
Taker_FillsUInt64Fills where this wallet's order took liquidity.
Taker_Volume_UsdFloat64Part of Volume_Usd from the wallet's taker fills.
Maker1
Maker_FillsUInt64Fills where this wallet's order rested on the book.
Buy2
Buy_FillsUInt64Fills where the wallet bought outcome shares.
Buy_Volume_UsdFloat64Cash the wallet paid for shares it bought, in USD at $1 per collateral unit.
Sell2
Sell_FillsUInt64Fills where the wallet sold outcome shares.
Sell_Volume_UsdFloat64Cash the wallet received for shares it sold, in USD at $1 per collateral unit.
Volume1
Volume_UsdFloat64Cash value of all the wallet's fills, valued at $1 per unit of collateral (USDC.e or pUSD), no market price applied.
Shares2
Shares_BoughtFloat64Outcome shares bought, all markets together.
Shares_SoldFloat64Outcome shares sold, all markets together.
Fees1
Fees_Paid_UsdFloat64Trading fees this wallet paid, in the collateral token at $1 per unit; 0 before January 2026.
Avg1
Avg_Fill_PriceFloat64Volume_Usd divided by shares traded: the average price per share, between 0 and 1.
Parlay2
Parlay_FillsUInt64Fills on Polymarket's parlay exchange; 0 before 10 November 2026, when parlays went live.
Parlay_Volume_UsdFloat64Part of Volume_Usd from parlay fills.
UpDown1
UpDown_Volume_UsdFloat64Part of Volume_Usd on crypto Up or Down markets (title starts with a coin name and 'Up or Down').
First1
First_Fill_TimeDateTimeFirst fill of the day, UTC (Parquet timestamp in milliseconds).
Last1
Last_Fill_TimeDateTimeLast fill of the day, UTC (Parquet timestamp in milliseconds).
Top3
Top_Market_Condition_IdStringCondition id of the market where the wallet traded the most USD that day.
Top_Market_TitleStringQuestion of that market; empty when our index has no title for it.
Top_Market_Volume_UsdFloat64USD the wallet traded in that market that day.
polymarket_wallet_market_pnl21 columnsOne row per wallet per resolved market: its fills since September 2025 rolled up, the winning outcome and the profit or loss at the result.
ColumnTypeDescription
Resolved1
Resolved_TimeDateTimeWhen the market was resolved on chain, UTC (Parquet timestamp in milliseconds).
Condition1
Condition_IdStringCondition id of the market; joins to the Polymarket dataset's tables.
Market2
Market_TitleStringThe market question.
Market_Created_AtDateTimeWhen the market was created, UTC (Parquet timestamp in milliseconds).
Event1
Event_TitleStringTitle of the event that groups related markets, such as one election; empty when the market stands alone.
Other3
OutcomesStringOutcome names in index order, as text in the form ['Yes', 'No'].
WalletStringPolymarket wallet (the proxy wallet that holds positions) that placed the orders, 0x-hex.
FillsUInt64Fills of this wallet's own orders in this market since 1 September 2025.
Winning3
Winning_Outcome_IndexInt32Index of the winning outcome, from 0, as the resolution names it.
Winning_Outcome_LabelStringName of the winning outcome.
Winning_Shares_NetFloat64Winning-outcome shares bought minus sold. Negative when the wallet sold shares it got outside the exchange, for example by splitting cash.
Taker1
Taker_FillsUInt64Fills where this wallet's order took liquidity.
First1
First_Fill_TimeDateTimeFirst fill in this market, UTC (Parquet timestamp in milliseconds).
Last1
Last_Fill_TimeDateTimeLast fill in this market, UTC (Parquet timestamp in milliseconds).
Buy1
Buy_Volume_UsdFloat64Cash paid for shares of any outcome, valued at $1 per unit of collateral (USDC.e or pUSD), no market price applied.
Sell1
Sell_Volume_UsdFloat64Cash received for shares sold, in USD at $1 per collateral unit.
Fees1
Fees_Paid_UsdFloat64Trading fees paid in this market, in the collateral token at $1 per unit.
Other1
Other_Shares_NetFloat64Losing-outcome shares bought minus sold; worth 0 at the result.
Resolution1
Resolution_Value_UsdFloat64What the net winning shares paid at the result: 1 per share, whether or not the wallet redeemed.
Realized1
Realized_Pnl_UsdFloat64Sell_Volume_Usd minus Buy_Volume_Usd minus Fees_Paid_Usd plus Resolution_Value_Usd.
History1
History_CompleteBoolFalse when the market was created before 1 September 2025, so earlier fills are missing and the PnL is partial.
Send this dataset’s full schema to an assistant and ask it anything. It reads the plain-text brief ↗ first, so the answer comes from the real column list rather than a guess.
Opens a new chat with the question filled in. Nothing about you is sent to Bitquery, and the assistant sees only the public brief.
Delivery
Parquet files in a Requester Pays S3 bucket or a Cloudflare R2 bucket, chosen at checkout. On S3 you download with your own AWS account and AWS bills the transfer; on R2 you download with a read-only API key and pay no egress. Layout:
# polymarket_wallet_daily: one file per day
matic/polymarket-traders/polymarket_wallet_daily<YYYY-MM-DD>.parquet# polymarket_wallet_market_pnl: one file per resolution day
matic/polymarket-traders/polymarket_wallet_market_pnl<YYYY-MM-DD>.parquet
Download a free sampleNo email needed.
Pay nowName, work email and licence check.
Pay the invoiceBy card or bank transfer.
Download from S3 or R2The team prepares the export and emails the bucket path, plus a read-only API key for R2 orders.
Need new data after your purchase?
Kafka Streams sends new Polymarket data in real time, so your copy can stay current after the files end. It is sold on an Enterprise plan.
Two Parquet tables built from Polymarket's order fills and market results on Polygon. The daily table has one row per wallet per day with fills, volume, fees and the day's biggest market. The PnL table has one row per wallet per resolved market, with what it bought, sold and paid in fees, the winning outcome and the profit or loss at the result.
How big is it?
About 36 million wallet-days from 1 September 2025 to mid-November 2026, and up to about 340 million wallet-market rows, roughly 22 GB as ZSTD Parquet. These are estimates from distinct wallet counts and a full-day export of each table; exact figures arrive with the delivery manifest.
How do I find Polymarket's biggest traders?
Sum Volume_Usd, Fills or Fees_Paid_Usd by Wallet in the daily table over the dates you want and sort. Volume is not profit: a market maker can top the volume list and lose money. Rank by Realized_Pnl_Usd in the PnL table for results.
How is each fill counted?
Once, under the wallet whose order was filled. A match puts a maker's order and a taker's order on chain, and each wallet gets its own fill, so summing every wallet's Volume_Usd gives about twice the market's traded volume. Volume_Usd minus Taker_Volume_Usd, summed over wallets, is the market volume: $70.3 million on 13 November 2026.
How is profit or loss worked out?
Realized_Pnl_Usd is cash from sales, minus cash paid for buys, minus fees, plus 1 for each net winning share held at the result. Shares are valued at the result whether or not the wallet redeemed them, because since May 2026 most payouts go through relayer contracts that name themselves as the holder. Markets that are still open have no row until they resolve.
How did you check the numbers?
Every fill has a buyer and a seller, so profit across all wallets in a market should equal minus the fees paid. For markets resolved on 13 November 2026 it was off by $91 on $104 million bought, on 20 January 2026 by $0, and on 15 June 2026 by $23,604 on $281 million. The daily table for 13 November 2026 matched the source: 3,437,824 fills, 45,067 wallets and $1,051,943 in fees.
How are amounts valued in USD?
At $1 per unit of collateral. Polymarket settles in USDC.e until April 2026 and in pUSD after, and both are counted at par with no market price applied. The Polymarket dataset prices the same cash at the hourly USDC.e rate, so its USD columns can differ by a fraction of a cent per dollar.
Are parlays included?
Yes, in the daily table, from 10 November 2026 when Polymarket's parlay exchange went live: Parlay_Fills and Parlay_Volume_Usd. Parlays have no on-chain result row of their own, so they are not in the PnL table.
What should I watch out for?
Markets created before 1 September 2025 have History_Complete false: fills before that date are missing and their PnL is partial. Shares moved by plain token transfers or NegRisk conversions are not seen, and a tied market that pays 50-50 is read with the single winner its result names. Wallets are Polymarket proxy wallets, not the signer's own address.
How do I follow one wallet, for a copy-trading bot?
Filter Wallet in the daily table for its activity and in the PnL table for its results per market, then pick wallets by Realized_Pnl_Usd over many markets rather than one lucky call. For each fill's price and time, match the address against the buyer and seller columns of the Polymarket dataset's trades table.
How do I load it?
One line in DuckDB: SELECT Wallet, sum(Volume_Usd) FROM read_parquet('polymarket_wallet_daily/*.parquet') GROUP BY Wallet ORDER BY 2 DESC LIMIT 20. Pandas works too: pandas.read_parquet(path). The sample files open without a login.
How current is it, and how is it delivered?
Built at purchase with T+1 latency, so an order made today covers everything to yesterday. Delivered as Parquet, one file per day, with a JSON manifest listing every file and its sha256. We prepare the files within 7 business days of purchase and email you the location: a Requester Pays S3 bucket or a Cloudflare R2 bucket with a read-only key. Files stay available for 7 days from delivery.