About StatsLedger
StatsLedger publishes NFL player, team and season statistics since 2000 and ranks every quarterback, running back, wide receiver and tight end season by percentile against qualified players at the same position.
Who runs StatsLedger
StatsLedger is an independent site built and maintained by an avid Giants and NFL fan. The site is run as a small business and is not affiliated with the NFL or any team. You can reach a person at support@statsledger.co.
What the site covers
3,607 players, 32 teams and 26 completed regular seasons from 2000 to 2025, plus the 2026 season in progress, with a page for every player and team and a page for each season. Stats are real NFL stats such as yards and touchdowns. The site does not publish fantasy points or advanced models.
What makes it different
Raw totals are available in many places. StatsLedger adds context: every qualified player season gets a percentile and a rank among players at the same position that season, so a 1,000-yard season can be compared fairly across different eras. Each page also has a short summary, key insights and answers to common questions, all calculated from the data, plus insights articles and a player comparison tool.
Where the data comes from and how often it updates
Stats come from the public nflverse data project. The site rebuilds every Tuesday, so pages include the latest games after each week. Totals are calculated from nflverse game-by-game data and can differ slightly from official NFL totals, especially in earlier seasons. The method page explains each calculation with real examples.
How pages are written
Player, team and season pages are generated by software from the numbers, so wording follows the data and updates automatically. Pages with too little data are kept out of search engines (players with fewer than 16 career games and seasons with fewer than 4 games). The insights articles analyze the same data with written explanations.
Corrections
If a number looks wrong, contact us with the page address and what looks off. We check it against the source data and fix confirmed errors, usually in the next Tuesday update.