Airavat is in Private Alpha. Request early access at airavat.xyz
PolymarketSliced Metrics

Sliced Metrics

Every trader stat in Airavat (PnL, Win Rate, Sharpe, Trader Score, all of them) is computed for the trader’s trailing 180 days by default, and again for narrower slices of recent activity. A slice is a combination of a market category and a time window, for example, “Politics over the last 30 days” or “Crypto over the last week”.

The slice you choose decides which numbers you’re looking at. The default 180-day numbers tell you who someone has been over the last six months; slices tell you who they are right now.

Why this matters

A whale who was a god at sports markets in 2023 no longer dominates the default view — the trailing 180-day window has already dropped that record. But inside that window a trader can still be coasting: someone who was hot four months ago and has gone cold this quarter looks strong on the 180-day default and mediocre on a 30-day slice. If you copy-trade them on the default alone, you may be trading someone who has already turned. Slicing lets you condition on recent form, not just the last six months.

Common reasons to reach for a slice:

  • Recent form: “Show me traders whose 30-day Sharpe is still > 2, old stars don’t count”
  • Domain expertise: “Show me 90-day Win Rate within Politics only, global Win Rate hides their politics edge”
  • Hot streaks: “24-hour Total PnL ranking, biggest movers right now”
  • Cooling off: filter your existing whitelist by sliced score to drop traders who are slipping

How slicing works

A slice is (category, timeWindow):

  • Category is a market tag the trader has been active in: Politics, Crypto, Sports, Entertainment, etc. The default ALL means “any market”.
  • Time Window is one of 24h / 7d / 30d / 90d / 180d. The default is 180d — the trailing 180 days.

The default slice (ALL, 180d) is the trader’s trailing-180-day stats across all markets. Every other combination is a sliced view that filters the underlying positions before computing the metrics.

SliceWhat it represents
(ALL, 180d)The trailing 180 days, all markets — the default everywhere
(ALL, 30d)Recent form, all markets
(Politics, 180d)The trailing 180 days, politics markets only
(Crypto, 7d)Recent form within crypto only

Where slicing appears in the UI

Traders tab (top filters)

Two dropdowns above the table: Filter by category and Filter by time. Whichever combination you pick, every column in the table reflects that slice. So the “PnL” you see on the trader table is the trader’s PnL for that category and that window — by default the trailing 180 days across all markets.

Trader detail page (per-page slicing)

The same two dropdowns sit at the top of every trader’s profile. Switching them re-slices the trader’s metric cards and the equity curve to that slice. The Open Positions, Closed Positions, and Trade History tabs always show the trader’s full activity (positions don’t move into or out of slices), but the headline counts in the metric cards reflect the slice. The URL preserves your selection so the back button restores your view.

Advanced mode (Traders tab)

The Advanced mode criteria panel within the Traders tab matches traders against their sliced metrics, using the same category and time-window selectors. Set the slice first, then the criteria; results show traders who meet the threshold within that slice.

Filter Builder (Trader Criteria)

The Trader Criteria component has a Market Categories picker. Selecting tags here matches traders who are active in any of those categories (OR logic). The thresholds (Win Rate, Sharpe, etc.) on a saved filter are evaluated against the trader’s trailing-180-day stats by default, not the per-category slice. (If you want a slice-aware filter, use the Trader Whitelist with traders you’ve validated in Advanced mode using a slice.)

Eligibility: why some metrics show no value

Every slice has a minimum-trades threshold. Traders with too few closed positions in (category, timeWindow) aren’t ranked there. Their sliced metrics show a placeholder instead of a noisy estimate.

The threshold for receiving a Trader Score is currently 20 closed positions. Individual metrics (Sharpe, Sortino, Profit Factor, etc.) may also be null in a slice when the underlying sample is too thin to be stable; they render as a placeholder the same way.

This is why a hot trader who’s only closed a handful of positions in the last 24 hours will show a placeholder on a 24h slice. There isn’t enough data to compute meaningful values.

The 180-day default vs a narrower slice: when to use which

Use the 180-day default when…Use a narrower slice when…
You want the fullest track record Airavat computesYou want to filter for current form
Comparing risk-adjusted returns over the last six monthsCatching a cooling trader before they hurt your PnL
A deeper closed-position count is the signalRecent regime or category-specific edge is the signal
The trader has a small closed-position count in the windowA slice would be even thinner — the default aggregates more

A common workflow: the 180-day default to find candidates, a narrower slice to validate they’re still on. Build a list of traders with strong trailing-180-day Sharpe + Win Rate + Trader Score, then switch to Advanced mode in the Traders tab, select the same criteria with a (ALL, 30d) slice, and see who survives.

Data freshness

Sliced metrics are recomputed on the same cadence as the default 180-day stats. Metrics are recalculated continuously in the background, with each trader processed at most once every 24 hours. The Last column on the Traders tab is trade freshness; the metrics behind a slice may be slightly stale relative to the very latest fill but converge within hours.

For a sliced view of a trader who hasn’t traded in the slice’s window, you’ll see placeholders everywhere even if their 180-day stats are healthy. That’s working as designed: no signal in that slice means no metric.