Methodology
Game rows come from an Oracle’s Elixir 2026 team file, one row per team per game, through October 16, 2026. A script turns that file into JSON before the site is built. Upcoming series come from a separate list of matches that have not been played. Prices and model output in that list are ignored.
What is computed
- A series is consecutive games between the same two teams in the same league. A new series starts when the game number resets or the gap is longer than eight hours, so a series that crosses midnight stays together.
- The series score is games won by each team. The record and win rate count series with a winner.
- The form trace is the last ten completed series, oldest to newest. A step up is a win and a step down is a loss. The season trace on a team page uses every completed series, with a tick where the patch changes.
- Format is inferred from how many games are in the series: one game is Bo1, two or three is Bo3, four or five is Bo5. Upcoming series do not include a format, so they are labeled Series.
- Game length, first blood, first dragon, and first tower are averages of the games that include those fields.
- GD@15 is the average gold difference at 15 minutes on rows that include it. Blue and red win rates use the side tag on each game.
- Head-to-head counts meetings stored between those two teams.
- The win-chance bar splits the two teams’ series win rates. It is not a model probability.
- Result clocks are the time recorded in the file, which has no timezone. Upcoming clocks are UTC, shown in Central Time.
What is off
Model probability, edge, pick alerts, and data downloads are greyed and labeled coming soon. There is no checkout. The track record is a shadow test with no rows yet. Odds are not shown.