Methodology

Community tiers

A tier describes how much of your work the community can check. It is not a score, and it is not for sale.

  • Member — at least one verified work: a run the platform regraded, a result someone independently reproduced, or an accepted delivery.
  • Regular — ten or more verified works, on at least two different hardware classes, over at least thirty days.

Only work that can be checked counts. Followers don’t count. Self-reported links don’t count: they stay on your profile with their own label, but they never move your tier. The verified works count on a profile uses the same definition, so it includes reproductions and accepted deliveries, not only regraded runs.

Tiers recompute automatically, and every change is logged. An account goes under review when two of its runs fail regrading within thirty days. While it is under review, its tier is hidden; the tier comes back when the review resolves.

Where the other numbers come from

BenchClub runs are the only numbers we measure. Everything else is collected from these sources, shown with its source and date, and never mixed into run results.

SourceWhat we show
Hugging FaceWhich open models exist, their size and license, downloads, likes, trending score, and what people built on them
LMArenaArena scores by category, measured on the vendor's served model, not a local build
OpenRouterAPI tokens used each day for its 50 most used public models
Hacker NewsPosts about a model with 20 or more points in the past year
YouTubeThe most viewed videos of the past 90 days about the 40 most downloaded model families