Methodologies
How aggrgtr collects, stores, summarizes, and displays the data behind each dashboard. This page is meant for RuneScape community members who want to understand what the numbers represent and how to replicate the metrics I've built.
aggrgtr is independent and is not affiliated with, endorsed by, or sponsored by Jagex Ltd. The site uses public data sources, public APIs, public web pages, and stored snapshots.
The population tracker uses frequent snapshots from official RuneScape sources to show live counts, recent movement, and long-term population patterns.
Where the live numbers come from
Live totals come from two public Jagex sources.-Combined RuneScape and Old School RuneScape total count uses Jagex's player_count.js endpoint, following the approach documented by the RuneScape Wiki API page.-Old School RuneScape count comes from the official OSRS world-select page.Snapshots are collected about every 3 minutes.RuneScape 3 counts are calculated as the combined total minus Old School RuneScape.
Steam counts
Steam counts use Valve's public Steam Web API.-Current player counts use the ISteamUserStats/GetNumberOfCurrentPlayers endpoint for the RS3, OSRS, and Dragonwilds Steam app IDs where shown.-Steam values refresh about every 15 minutes.Steam is shown separately because those players are already included in the official RuneScape totals.
KPI cards
The large cards at the top of the page summarize population snapshots.-Latest snapshots are the newest observed OSRS, RS3, and Total Online counts.-Recent averages are the 30-day and 1-year average player counts for OSRS and RS3.-Historical peaks are the highest stored OSRS and RS3 counts, with the dates they occurred.The KPIs give a quick look at the numbers without needing to read the full chart.
Time-of-day chart
The time-of-day chart groups population snapshots by hour in Central time.-30 Day compares today with the average hourly pattern from the last 30 days.-3 Month compares today with the average hourly pattern from the last 3 months.-Day of Week compares today with the same weekday over the last 30 days or 3 months.
Historical data
Historical population data was assembled from aggrgtr snapshots and public data.-aggrgtr snapshots began on December 26, 2025 at about a 3-minute interval.-misplaceditems.com supplied most archived history back to February 2013.-PlayerCount.dev filled some later gaps after MisplacedItems stopped updating.-Wayback Machine captures added some pre-2013 points.Most archived data used roughly 15-minute intervals; Wayback captures were point-in-time.-Pre-2013 Wayback captures often fall between 8 a.m. and 8 p.m. Central, so treat them as active-hour snapshots, not full-day averages.-Some gaps remain where no usable source coverage exists.
The trends page shows RS3 and OSRS population history separately across comparable days, months, and years. It shows year-over-year movement, long-term direction, recent highs and lows, and RS3 hiscores activity.
Year-over-year views
Year-over-year views compare like periods across years.-Daily compares the same calendar dates across years.-Day of Week compares the same weekday across years, such as Monday to Monday.-Monthly compares monthly averages across years.
Trendlines
Population trendlines are fitted from the selected chart window.-The model accounts for weekly rhythm.-Longer ranges can also account for annual seasonality.-Short windows can still move quickly around updates, holidays, and Double XP.Read the line as directional, not definitive.
Peaks and lows
Peaks and troughs summarize the extremes in a selected range.-Peaks are the highest stored counts in the selected range.-Troughs are the lowest stored counts after filtering fake lows from game outages.-These charts show whether highs and lows are moving higher or lower over time.
Hiscores context
The hiscores charts use the same RS3 hiscores activity data as the Hiscores Tracker.-Weekly and monthly charts compare comparable periods year over year instead of one continuous line.-Rows count accounts that appear on the weekly or monthly XP-gain rankings after gaining at least 1,000 XP in the relevant period.They are not concurrent player counts; they count total accounts active during the selected weekly or monthly period.
Regression analysis
Regression estimates the direction of player counts or activity over the selected window.-Population trendlines use Fourier regression with ordinary least squares.-The model fits the trend while accounting for weekly rhythm and, on longer windows, annual seasonality.-Shorter windows use weekly rhythm only, because annual seasonality can overfit when the range is less than a full year.-The slope is shown as players per year, month, or day, depending on the chart range.-Hiscores trendlines use Theil-Sen median regression, which is less affected by unusual weeks or months.Positive slopes mean player counts or activity are rising; negative slopes mean they are falling. Use these slopes directionally, not as exact predictions or counts of specific players who left or returned.
The hiscores tracker pulls the last ranked account count from the public RS3 weekly and monthly hiscores pages over time. This page shows how many total active accounts appeared on the hiscores during the most recent weekly or monthly period.
Where the data comes from
Hiscores counts come from the public RS3 Overall hiscores pages.-Weekly counts use the weekly hiscores view.-Monthly counts use the monthly hiscores view.-Past periods are obtained by adding the URL's millisecond timestamp. For example, the weekly table for Wednesday, June 3, 2026 at 00:00 UTC uses date=1780444800000.-The scraper finds the last page, reads the last ranked account, and records that rank as the account count for the period.Accounts need at least 1,000 XP in the relevant period to appear on weekly or monthly hiscores tables.
Weekly and monthly updates
Current counts and finalized weekly or monthly totals update on different schedules.-Current-week snapshots are collected about every 3 minutes.-Monthly figures refresh about every 15 minutes.-Weekly total checks run around the Tuesday evening reset in Central time.-Monthly totals are collected at the first of the month using a similar script.After a week or month ends, the script checks that same week or month again. Final weekly or monthly numbers can update if Jagex changes the count after the first pull.
Chart views
The chart views show different slices of the hiscores data.-The live chart shows the current running period.-The 7-day and 30-day views show recent snapshots from the running count.-The all-time weekly and monthly views show weekly and monthly totals over time.-Those all-time series include older historical rows imported from a Reddit post with data going back to 2014.
The Maxed page estimates how many accounts have reached major hiscores milestones. It covers RS3 and OSRS regular accounts, Ironman account types, and an RS3 Hardcore Ironman RuneScore view.
Where the data comes from
The Maxed scripts use public hiscores ranking endpoints.-Regular RS3 uses the public RS3 hiscores endpoint: https://secure.runescape.com/m=hiscore/a=600/ranking.-Regular OSRS uses the public OSRS hiscores endpoint: https://secure.runescape.com/m=hiscore_oldschool/a=600/overall.-RS3 Ironman and Hardcore Ironman use m=hiscore_ironman/ranking and m=hiscore_hardcore_ironman/ranking.-OSRS Ironman, Hardcore Ironman, and Ultimate Ironman use m=hiscore_oldschool_ironman/overall, m=hiscore_oldschool_hardcore_ironman/overall, and m=hiscore_oldschool_ultimate/overall.
Method
Maxed totals are boundary estimates from hiscores ranks.-For Overall, the script finds the last ranked account still showing the current max level.-For skills, the script finds the last rank still meeting each milestone.-Skill milestones include level 99, RS3 level 110 and 120 where shown, and 200M XP.-The same boundary method is used for regular and Ironman views.
Members and non-members
The member split is only shown for regular RS3 Overall.-Member and non-member counts are estimates from public hiscores pages.They are not official membership or subscriber numbers.-Very low-level accounts may not appear if they are not ranked.OSRS and Ironman views do not show membership splits.
RuneScore
The RuneScore view uses public hiscores endpoints for RS3 Hardcore Ironman.-The main list comes from m=hiscore_hardcore_ironman/a=600/ranking.-Validation uses Ironman and regular RuneScore lookups for the same player.-Those checks use m=hiscore_ironman/a=600/compare, m=hiscore/a=600/compare, and matching ranking lookups when needed.-The page marks rows as Alive, Dead, Bugged, or Lookup issue based on those endpoint checks.
Views and timing
The page updates different views on different schedules.-Regular RS3 Maxed counts are scheduled at 12 a.m., 6 a.m., 12 p.m., and 6 p.m. Central. The page checks for new results during the first 45 minutes after each scheduled run.-Regular OSRS Maxed uses the same four scheduled run times. The page checks for new results about 35 to 75 minutes after each normal Maxed scheduled run.-Ironman Maxed views use the same four scheduled run times. The page checks for new results about 40 to 85 minutes after each normal Maxed scheduled run.-RS3 Hardcore Ironman RuneScore checks for new results from 5:05 to 5:30 a.m., 10:05 to 10:30 a.m., 3:05 to 3:30 p.m., and 8:05 to 8:30 p.m. Central.The custom chart can show latest run, daily average, or daily max for the selected period.Scrapes take time, so the newest page may reflect the latest available run rather than the exact current hiscores state.All counts depend on what public hiscores show, so they can be affected by inactivity, bans, hiscores bugs, or source changes.
The OSRS Worlds page tracks public OSRS world population counts. It shows the latest world list, region and world type filters, activity summaries, and history for individual worlds or grouped views.
Where the data comes from
World data comes from the official OSRS world-select page.-The page shows the current OSRS total and a table of worlds.-Each world row includes player count, region, world type, and activity label.-aggrgtr snapshots this data about every 15 minutes.
Region and type filters
Filters use the latest world list.-Region uses the location listed for each world.-Type uses the world type listed for each world, including free-to-play and members worlds.-Changing filters recalculates player totals and world counts from matching worlds.
Activity summaries
Activity summaries use the activity labels shown on the world-select page.-Blank or dash activity labels are grouped as General.-The page totals players by activity label, such as trade worlds, minigames, PvM, skill-total worlds, and temporary modes.-Activity filters can be combined with region and type filters.
World history
History views use previous OSRS world snapshots.-Selecting a world shows that world's player count over time.-Selecting an activity, region, or type shows combined history for matching worlds.-History ranges include day, week, month, quarter, and year.-The chart shows population movement across the selected range.
The anti-cheat page organizes Jagex Player Support and Anti-Cheating Statistics into a monthly dashboard and table for OSRS and RS3.
Where the data comes from
Anti-cheat data comes from Jagex's public Player Support and Anti-Cheating Statistics page.-Jagex releases these figures monthly, but not on a consistent day or time.-The methodology page links to the current public page, and monthly rows keep the source URL used for that row.
Monthly metrics
The monthly table tracks the fields Jagex reports.-Anti-cheat fields include macro bans, RWT bans, and GP removed.-Support fields include chat-spam mutes, support queries, live chat queries, support-center views, and report action messages.-Service fields include average response time and ticket satisfaction where Jagex reports them.
OSRS and RS3 comparisons
The dashboard compares game versions only where the source supports it.-Where Jagex reports both games, OSRS and RS3 are shown side by side.-F2P and P2P splits are shown where they are available in the source data.
Archive and timing
New anti-cheat figures are handled as monthly source updates.-A scheduled check looks for changes multiple times per day.-When new figures are found, the source page is saved to the Wayback Machine.-The Wayback snapshot is used as the source record for that month.
Source limits
This page depends on Jagex's public reporting.-If Jagex delays or skips a monthly update, aggrgtr has no independent source for that month.-Fields can change because Jagex may add or remove reported categories.-Missing values stay blank unless a public source supports filling them.
These are the closest public RuneScape player count reference sites I have reviewed. The sites are ranked by my current grade.
URL: https://osrsplayercount.com/
Strengths
- Preserved historical population data from misplaceditems.com before that source became unreliable.
- Covers live OSRS counts, historical views, world lists, locations, world types, F2P and Members filters, and world level population views.
- Highlights peaks and collects and uses world level data.
Limitations
- The filter area is visually heavy, and the design reads as older and niche.
- The page can feel a little laggy, likely because it appears to pull directly from backend data without much obvious caching.
- World activity context would make the world level views more useful.
- The site is OSRS-focused, so it does not provide RS3 counts.
URL: https://playercount.dev/
Strengths
- Tracks RuneScape player count data on a 15-minute interval.
- Provides downloadable RuneScape trend data going back to October 2025.
- Keeps the experience simple and became a useful replacement source after misplaceditems.com stopped being reliable.
Limitations
- It does not have a tooltip, which makes the chart harder to read precisely.
- The visual presentation could be stronger.
- The design echoes misplaceditems.com without fully landing a distinctive or polished look.
URL: https://rsplayercount.com/
Strengths
- Simple to understand, with light and dark modes, clear KPIs, multiple granularities, and a responsive tooltip.
- The displayed RuneScape player counts appear accurate.
- Includes an about page that explains hosting, privacy, and computation choices.
Limitations
- The public data history appears to start on February 28, 2026.
- Snapshots appear to be collected about every 30 minutes, which is useful but less current than 15-minute trackers.
- The text is small, and the page could use a little more visual emphasis without becoming flashy.
URL: https://runepixels.com/
Strengths
- The day-by-day comparison concept is useful.
- The current player count appears plausibly accurate.
- The tooltip includes max and min values, and the data appears to refresh on roughly a 15-minute interval.
Limitations
- The default day comparison can be misleading when it compares yesterday against today rather than equivalent weekdays.
- Weekday-to-weekday comparisons or default KPIs would make the chart easier to interpret.
- Some filters appear available even when no data exists for the selected period, and the live count can look delayed or unclear.
URL: https://lawrune.com/
Strengths
- This site functions mostly as an Ironman tracker, not as a player count tracker.
- The visuals are appealing, the graph options are useful, and the player count numbers appear accurate.
- Shows stored snapshot counts and useful peak views for Dragonwilds, OSRS, RS3, and total players.
Limitations
- The page is spread out, with too much spacing, scrolling, and some redundant KPI text.
- Several definitions are missing or unclear, including the help icon, recent activity, and typical activity.
- The player count history appears limited compared with older population sources.
URL: https://activeplayer.io/runescape/
Strengths
- More polished visually than several other player count pages.
- Steam player counts can still provide some directional context because they correlate loosely with total activity.
Limitations
- Appears to track Steam data only rather than official live RuneScape player counts.
- The page has many ads and a large amount of extra content that is not player count analysis.
- The same underlying data can be obtained directly from Steam.
URL: https://tracker.gg/population/steam/1343400
Strengths
- Provides Steam metrics such as 24-hour peak, all-time peak, monthly averages, weekday averages, and tracking duration.
- Useful for Steam-specific population context.
Limitations
- Does not provide official RuneScape live player counts.
- Only tracks Steam players and includes premium/ad framing.
URL: https://playercount.gg/runescape
Strengths
- The monthly Steam table is easy to scan.
- The layout is clean and approachable.
Limitations
- Uses Steam-only data rather than official live RuneScape counts.
- Does not provide much analysis beyond the Steam table.
URL: https://www.ely.gg/rs_playercounts
Strengths
- Clean, easy to understand, and useful for a high-level monthly view.
- The history goes back to February 2013, likely using misplaceditems.com as a historical source.
Limitations
- Monthly presentation is not useful for live or interval level player count analysis.
- The page stopped working in July 2025, which prevents it from being a current source.
URL: https://www.misplaceditems.com/rs_tools/graph/
Strengths
- Was the leading RuneScape population tracker for more than a decade.
- Tracked RS3 and OSRS population data at roughly 15-minute intervals.
- The design was plain, but the site was simple, accurate, and valuable.
Limitations
- Had outages and data gaps, ranging from small gaps to multi-month gaps.
- Went down sometime in October 2025.
- As of May 17, 2026, the page appears to generate fake data using the meme seed 42069, so it is no longer reliable as a current source.
URL: https://showmyitems.com/runescape-player-counts
Strengths
- Shows current Steam players, 24-hour peak, all-time peak, and Steam rank in a simple layout.
- The layout and color scheme are clear.
Limitations
- Uses Steam-only data rather than official live RuneScape counts.
- The page is heavily ad-supported.
URL: https://playercounter.com/runescape
Strengths
- Attempts to present RuneScape player counts in table form.
Limitations
- Reported a current live player count around 35,000 without a clear source.
- The numbers appear inaccurate or mixed between different data sources.
- The page is mostly tables and is not useful for reliable player count analysis.
URL: https://mmo-population.com/
Strengths
- No material strengths for RuneScape player count analysis.
Limitations
- Uses indirect estimates based on signals such as social media, Reddit, or other proxy sources.
- Does not use actual live data points from the OSRS website or the main RuneScape website.
- For RuneScape, this is one of the least reliable approaches to population information.
URL: https://igitems.com/runescape/charts
Strengths
- Contains a large amount of information, and the player count section appears to use Steam data.
Limitations
- Appears connected to real-world trading activity.
- Because of that context, it is not a source I would recommend for RuneScape population analysis.
URL: https://www.playerauctions.com/player-count/runescape/
Strengths
- Uses Steam data and separates it from Google Trends.
Limitations
- Operates in a real-world trading marketplace context.
- Because of that context, it is not a source I would recommend for RuneScape population analysis.