RoTrades Methodology

Primary sources

RoTrades pages can combine several data sources depending on the page:

• Roblox resale and public profile data when available.
• Tracked item snapshots stored over time for history charts and change views.
• Cached inventory records and collector snapshots for player pages and leaderboards.
• Tracked owner-list or UAID-based records where ownership detail is available.

Observed data vs derived data

Not every field on the site has the same certainty. Directly observed fields such as current RAP, cached best price, or a stored inventory row are different from derived metrics such as hoard percentage, owner counts from partial visibility, or sale-rate estimates. RoTrades aims to label those cases clearly on the page itself.

How item pages are built

Item pages combine the latest tracked item record with historical snapshots and ownership metadata where available. Some pages may also show notes about premium copies, visible copies, owner counts, estimated sale activity, or confidence levels when ownership tracking is incomplete.

How inventory pages are built

Inventory pages use tracked inventory snapshots and cached item metadata to estimate total value, RAP, and collectible counts. If an inventory is private or still syncing, RoTrades may show stored profile history without claiming that the live inventory is currently visible.

Limits and caveats

• Values and availability can move faster than a cached snapshot refresh.
• Owner visibility is only as complete as the tracked data available for that item.
• Private inventories, terminated accounts, and missing owner records reduce certainty.
• RoTrades is a research aid and should not be treated as a guarantee of fair value.