Methodology
On this page
SteamGamer.com separates official facts, reporting, community signals, reviews, and analysis so readers can see what is known, what is inferred, and what is still unknown.
The tracker uses no-account reports submitted to SteamGamer.com. Reports are submissions, not verified people. Partial reports help when a chart needs one date or milestone. Optional reminder signups privately link email to reports. See Privacy.
Progress charts count later milestones toward earlier stages: a shipped report also counts as a purchase. Reported totals automatically fill remaining stages through delivery after 14 full days without a saved milestone advancement following an invite, purchase, or shipment. Saving a later milestone restarts the clock; confirmations and date corrections do not. Reported dates stay unchanged. Weekly counts, Activity, timing results, and queue ranges use their own recorded evidence.
Steam Machine and Steam Frame default to a Controller-based adjustment for missing updates. Patterned extensions apply Controller reporting rates once on top of Reported totals. Machine uses the full uplift; Frame currently uses 25%. These estimates assume similar reporting behavior. We hide the extension when evidence is too weak.
Small samples can distort averages. The tracker favors medians and typical ranges, labels any fallback to a broader country result, and withholds ranges for very thin samples.
Tracker trends are not Valve data, sales totals, delivery guarantees, or counts of unique people.
Run Scores describe how a game runs on one device, using the same 1-to-5 scale: Broken, Poor, Playable, Good, and Excellent.
Steam Machine, Steam Deck, and Steam Frame results can include publicly anonymous community observations and cited external tests. Each numeric score included in an aggregate has equal weight, and the evidence counts stay visible. Missing settings stay missing. We do not turn an unanswered field into a hardware claim.
Community observations include reports submitted here and reviewed community evidence. Reviewed evidence keeps its exact source URL and identity private. Cited tests show a safe source link. Reviewed and cited evidence do not create a contributor-owned report or account.
Steam Machine, Steam Deck, and Steam Frame evidence stays separate. Frame standalone and streamed results also stay in their own matching groups.
Reports are submitted one game at a time without Steam sign-in. A score is required; settings are optional. My Reports uses saved browser access or one private collection link to manage your reports.
Steam sign-in, personal library filters, and batch reporting have been retired. Historical Steam-linked reports keep their existing visibility and equal aggregate weight. An account link never verified hardware or performance.
External evidence needs useful device-specific detail, such as an FPS target, graphics preset, or output resolution. Official compatibility badges remain a separate signal. If a source no longer meets our standard, it can be withdrawn from public results without deleting the audit history.
Medians may describe different tests. Without an FPS target median, the page may show a separately labelled reported FPS value rounded to a whole number. A reported range uses its rounded midpoint; differing observations use a rounded median of one prioritized representative per observation. Source qualifiers, frame-generation state, and scene context remain in the evidence details. This display does not fill the FPS target median. Custom identifies mixed graphics when no preset median exists. Unknowns stay blank. A source-backed recipe keeps one tested setup and its result with high, medium, or limited confidence.
Run Scores are observations, not controlled benchmarks or performance guarantees. Updates and settings can change results.
You can read and contribute reports without an account. Run Scores uses one private link for each anonymous collection. These links do not unlock historical Steam-linked reports. Browsing stays public.
SteamGamer.com does not ask for Steam credentials. Do not include credentials or account identifiers in reports. The forms do not ask for Steam IDs, usernames, emails, order numbers, reservation identifiers, tracking numbers, street addresses, ZIP codes, screenshots, documents, account handles, payment data, or government identifiers.
Public reports show only the details needed to understand the result. Private edit links and tokens are not included in public pages or APIs. Run Scores may have an optional anonymous public profile, but hardware tracker reports are never linked to it.
There is no public download of individual tracker reports. Public summaries may be cited with attribution to SteamGamer.com. Do not use them to identify contributors, combine them with private account data, bypass public limits, or imply that the data came from Valve.
Read the full Privacy policy. If a public report exposes something private, contact SteamGamer.com.
If something looks wrong, contact SteamGamer.com with the page or public report link and the strongest source you have. Do not send a private update link, token, or personal information.
We update pages when evidence changes or we find an error. A correction should say what changed and why. It should not hide uncertainty or imply Valve confirmed something it did not.
Editorial images may use original non-generative artwork, licensed or official assets, screenshots for source context, or existing source photos with the site's standard treatment. We do not use AI-generated artwork for article covers, heroes, thumbnails, or social images. Images must not invent test results, interfaces, product details, packaging, or availability.