Answer a stats question without opening a spreadsheet

Club administrators can pull cross-league participation, financial and roster reports and download each as a CSV.

Gated on the CLUB_VIEW_REPORTS capability — available to platform staff, the organization's league admins and owner, or a holder of a custom club role carrying that capability. Read-only.

A season-stats grid shows every player against every metric their sport publishes, sortable by any column and filterable by team, division, games played and player name.

The page lives inside the signed-in per-sport section (/s/:slug/explorer) — there is no public fan-page route for it. Metric values and columns are withheld unless the LEADERBOARDS module is on (backend/src/handlers/standingsHandler.ts:180-190). The grid reads at most 500 players in one request (backend/src/services/leaderboardService.ts:384) and sorts, filters and exports in the browser; there is no pagination and no server-side query.

Two to four players, or two to four teams, can be compared side by side on their season stat lines, with home/away split selection.

Hard-limited to between 2 and 4 entities per comparison (backend/src/handlers/standingsHandler.ts:219-220). Signed-in per-sport section only (/s/:slug/compare); no public fan route. Numbers are withheld when the LEADERBOARDS module is off.

Standings, leaderboards, the stat grid, comparisons, box scores, player game logs and advanced-stats tables each have a CSV export button.

CSV is the only export format — there is no PDF or Excel export anywhere in this domain. Exports are generated in the browser from the rows currently on screen (frontend/src/lib/csv.ts:13); there is no server-side export endpoint and no scheduled or emailed export.

Every match has a box score built by its sport's own projection of the recorded scoring events, and each of the supported sports ships its own box-score table layout in the app.

Anonymous access is allowed only when the league is public and ACTIVE or COMPLETED, when the match has streaming enabled, or when the viewer follows the league (backend/src/handlers/matchHandler.ts:277-318). Per-player minutes are derived, not directly recorded: they are reconciled from SUBSTITUTION events plus clock progression, only for sports with a real countdown clock, and a side whose opening lineup cannot be established keeps zero minutes flagged minutesReliable false.

A player page shows that player's season stat line and a per-game log with opponent, result and sport-specific per-game stats, with overall/home/away splits.

Returns an empty stat line unless the league has the LEADERBOARDS module enabled (backend/src/handlers/playerStatsHandler.ts:317-319). Minutes in the game log are an explicit estimate derived from which periods a player recorded an event in, flagged minutesEstimated on every row until SUBSTITUTION reconciliation lands, and rendered with a leading ≈.

Leagues can publish leaderboards that rank players by the metrics their sport defines — points and rebounds for basketball, runs and wickets for cricket, goals and assists for soccer.

The LEADERBOARDS feature module ships DISABLED by default (infrastructure/lambdas/db-init/platform-features.sql:1355, :1697) — a league admin must turn it on before any player numbers are served; until then the endpoint returns an empty list. A single leaderboard ranks by ONE metric at a time, capped at 100 rows and defaulting to 25; an omitted or unsupported metric falls back to that sport's first published metric.

For basketball, the platform derives advanced metrics — TENDEX, plus/minus, lineup efficiency, true-shooting and effective field-goal percentage, usage and offensive/defensive rating — on demand from the recorded event stream.

Basketball is the only sport with this layer: supportsAdvancedStats is true only in backend/src/sports/basketball/index.ts:119 and every other plugin sets it false, in which case the endpoints return typed-empty results. The MODULE_ADVANCED_STATS feature module also ships disabled and is seeded as a PRO-plan module (infrastructure/lambdas/db-init/platform-features.sql:2660); with it off the endpoints return an empty shape rather than an error.

Most sports declare their own advanced-metric definitions, which the platform derives from recorded events and shows on the match page and in league leaderboards.

20 of the 23 sport plugins declare the generic advancedStats capability; curling and pool declare none, and basketball uses its separate basketball-only path. Gated behind MODULE_ADVANCED_STATS, which is disabled by default per league.

Advanced per-match, per-player and per-lineup statistics, plus sport-specific advanced metrics, are available through the platform's analytics module.

Gated behind the MODULE_ADVANCED_STATS feature module, which ships disabled by default and is marked as requiring the Pro plan, so the entitlement check runs in addition to the per-league toggle. Basic standings, leaderboards, season stat grids and comparisons sit on the separate free STANDINGS / LEADERBOARDS modules and are unaffected. With the advanced module off these endpoints return an empty payload rather than an error.

For baseball and softball, pitching lines are derived from the scored event stream, attributing each outcome to the pitcher on the mound.

Only baseball and softball declare a pitching capability; every other sport returns an empty shape (backend/src/services/pitchingStatsService.ts:18-20). Gated on the LEADERBOARDS module, which defaults off (backend/src/handlers/pitchingStatsHandler.ts:82).

Each standings row carries a computed strength-of-schedule rating, and the table shows a recent-form streak for each team.

Strength of schedule is a derived rating from opponents' records within the same league; it is not an external or cross-league rating system.

Standings can be filtered to overall, home or away records, scoped to a single division or tournament pool, and scoped to a chosen season.

Pool scoping counts only games where both teams are in that pool. Season scoping requires the league to have Season rows; with no season selected the table is all-time for that league.

Organizations get a ticketing insights view with totals for tickets sold, gross sales, net after the platform fee, tickets redeemed, sold-out event count, sell-through percentage, a per-event breakdown and a daily sales series for the last thirty days.

Scoped to the signed-in user's own organization from their token, entitlement-gated, and the sales series window is fixed at thirty days in code.

A league-wide ticketing tab rolls up printed, sold and redeemed ticket counts plus revenue across every ticket type in that league.

League-admin authorization plus the Ticketing entitlement.

A league's public fan page can show a standings tab and a stats tab, with the standings columns coming from that league's sport.

Both tabs are module-gated — standings on STANDINGS, stats on LEADERBOARDS (which defaults off). The league must be marked public and be ACTIVE or COMPLETED, or the viewer must be a signed-in follower via a join code or invite (backend/src/handlers/standingsHandler.ts:34-53); an anonymous reader additionally needs PUBLIC_STATS left on, or both tabs come back empty.