Disclosure

How this site is made.

Who publishes BloxToolbox, how the pages are made, and how the numbers on them are checked.

Last updated November 18, 2026

Who publishes it

BloxToolbox is published under its own name. It is not affiliated with Roblox Corporation or with any game developer, and no page on BloxToolbox is paid for by anyone it writes about.

Editor

C. B. Zakarian (a pen name) is the owner and editor of BloxToolbox.

C. B. Zakarian decides what BloxToolbox publishes and when, and the figures on each page are checked against the sources it names before publication. Errors are corrected when they are found, and each correction is dated in the corrections log.

How the pages are made

The tool writeups, the limiteds and player-count pages and the blog posts are produced from public data and the sources named on each page, under the owner's direction. The owner decides what is published and when. Where a page says "we", it means the site. No page describes anyone's own trades or play.

How the numbers are checked

  • Limiteds. Prices, RAP and sales counts come from Roblox's own resale records for each item and are read when the site's data is refreshed, which is not on every build, with a second Roblox source checked for the items both report; the limiteds page gives the date they were last read. An item with no sale in the last 90 days gets no estimate. The limiteds page writes out how its estimate, trend and activity columns are computed.
  • Player counts. Each tracked game's concurrent players are read from Roblox's public game data on each day the snapshot runs, which has not been every day, and kept in the site's own archive. A missed day is shown as a gap and never filled in.
  • Calculators. Every calculator runs in your browser, and its page explains the formula with a worked example. The rates and fees they use (DevEx, the marketplace fee, Robux prices) come from Roblox's own pages, which each calculator links next to the date they were last checked.
  • Articles. Figures come from the site's own published data files or from a named source.

If a figure cannot be verified, it is left out and the page says so. Every correction is dated and listed in the corrections log, and the page it changed links to its entry. How the calculators and lookups work, and what they never do with what you type, is on how our tools work.

The limiteds read, step by step

  1. Which items. The tracker follows the classic limiteds that Roblox’s catalog search returns, ranked by RAP, and keeps their IDs and names in a cached list so that every read covers the same items. The read of October 9, 2026 covered 172 of them.
  2. The read. For each item, the build asks Roblox’s current resale service (apis.roblox.com/marketplace-sales) for its RAP, its dated sale prices and its dated sale volumes. Requests go out one every 1.25 seconds to stay inside Roblox’s rate limit.
  3. The cross-check. The same run reads a public inventory through a second Roblox service (inventory.roblox.com), which reports Roblox’s current RAP for each item it holds. Every tracked item found there must match within 1% after a second read; one that still disagrees is held out of the rankings with a dated note. On October 9, 2026, 14 items overlapped and all 14 agreed.
  4. The stop rules. If fewer than 90% of the overlapping items agree, or fewer than 60% of the tracked items get a price, the run publishes nothing and the previous file stays up. An item whose request fails keeps its last reading, with that reading’s own date. Two sources are never averaged, and no missing value is filled in.

Until September 11, 2026 the tracker read an older Roblox resale address that had stopped recording sales on February 4, 2025, so its prices were about 19 months old and the site wrongly said the market had not moved. The switch to the current service and the correction are in the corrections log. How the estimate, trend and activity columns are computed from these records is written out on the limiteds page.

The player-count read

Each tracked game is matched from its name to a Roblox universe ID, and the name Roblox returns is checked against the one searched for, so a bad search result cannot attach one game’s numbers to another. The read then asks Roblox’s public games service for the number of people playing each game at that moment. A game needs 14 days of readings before it is charted, and a series that resolved to the wrong game is left out. The readings run from June 28, 2026; in the export of October 16, 2026, the copy on this site, 108 games had charts and readings existed for 53 of the 111 calendar days, with none after October 16. The hour of the reading has varied, so small day-to-day moves are within the noise; the player-count history marks every missed day as a gap.

From data to page

The site is a set of static files. A build reads the data files, writes the tables and figures into each page’s HTML, and copies the data files to /data/, so the numbers on a page can be read without running any script and checked against the file behind them. The web server only hands out files: there is no account system and no server code, and the database that keeps the daily readings stays on the machine that runs the build. Each page’s “Last updated” date, and its date in the sitemap, move only when its title, description or main text changes; a rebuild that changes nothing moves no date.

Publication dates

A blog post carries the date it was written and, after a substantive change, the date of that change. No page is dated earlier than the day it was first built. On September 25, 2026 twenty guides and posts that carried earlier dates were re-dated; the details are in the corrections log.

Advertising and contact

The site’s pages load Google AdSense’s Auto ads code; as of October 29, 2026 BloxToolbox has not been approved by AdSense, so no ads appear yet, and the privacy policy describes how advertising would work. There are no affiliate links and no sponsored pages. Corrections and questions go to contact@bloxtoolbox.com.