Rating

Open BoosterX → Benchmark → Rating. The rating shows published results accepted by the server. Scores are calculated according to the current methodology; after it is updated, scores and places may change without a new test run.

Comparison scopes

The following options are available in the rating mode list:

Mode	What it shows
Global	Overall rating by PC Score
Global CPU	Rating by CPU Score
Global GPU	Rating by GPU Score
Same CPU	PC Score among systems with the same detected CPU model
Same GPU	PC Score among systems with the same detected GPU model
Same CPU + GPU	PC Score among systems with a matching CPU and GPU pair
My rating	Positions of your own published result
By filters	Results of the selected advanced search, when it is available

“Same CPU” and “Global CPU” solve different tasks. The first limits the set of systems but keeps the overall PC Score. The second sorts by CPU Score without limiting to one model. A similar distinction applies to GPU.

A matching model does not mean identical memory, overclocking, cooling, power limits, drivers or background processes. Therefore two identical processors may receive different scores. To compare before/after, use a series of your own runs.

Filters

Click “Filters” next to the mode list. Clicking again collapses the block. In it you can select CPU, GPU, RAM capacity, enter a nickname and refine the search with the available toggles. The value “Any” does not restrict the corresponding component. The “Apply” button starts the search, “Reset” removes the selected restrictions.

Search availability and the PRO requirement are set by the server. If the feature is disabled, the filters button is hidden. When PRO is required, the parameters can be viewed, but applying requires a valid license. This is a search limitation, not a condition for displaying all badges or the regular rating.

Badge search parameters are shown only when the server permits their display. The absence of these toggles is not in itself a client error.

Position and percentile

Position is the place in the selected table: the smaller the number, the higher the result. Percentile characterizes the standing relative to its participants. Switching between the overall, CPU and GPU rating changes the sorting metric, so the places of one PC may differ noticeably.

An empty sample means that there are currently no suitable available results. It does not prove that such computers do not exist at all. Check the selected mode and reset the filters; if the program reports a connection error or a temporary restriction, rely on that message.

Ranking rule

For regular publication, a completed eligible Candidate run is intended. Quick, Extended and custom shortened runs remain local. A cancellation or an incomplete test does not turn into a rating result after score recalculation.

The server may send a publication for additional review, hide the result or restrict its display. A high score by itself does not guarantee publication, and waiting for review does not automatically mean that the user violated the rules. The rating displays the participant’s current publication, not their entire local history.

Table row composition

A row contains the place, nickname, main PC components and the score of the selected table. Expand the row with the arrow next to the nickname to view the available details: component scores, source metrics and system information. Not all fields are mandatory: information that is missing or hidden by the server is not shown.

To understand the result, see CPU Score, GPU Score and Latency. A similar overall score may be composed of different strengths and weaknesses of the system.

What is sent along with the result

Before publishing, expand the list of data being sent. In addition to metrics, it may include the CPU model, graphics card and driver, memory capacity and details, Windows, BIOS and power mode. The public set of information is regulated by the server and may be reduced by moderation.

Publication is voluntary. Do not enter personal data in the nickname or other public fields. Sending a result, applying for a badge and consenting to show contacts are separate actions.

Badges and contacts

Badges are displayed next to the nickname if their display is permitted by the server. The set, names and icons may change. PRO status is taken into account at the time the result is published; a license expiring later does not by itself remove this mark from an already published result. PRO does not mean identity verification or an advantage in score calculation.

For the other available badges, in the “Get badge” block select the desired options and click “Submit application”. After submission, a code appears. Pass it to support for confirmation: choose an available contact method in the program and write from the corresponding account.

• Discord BoosterX: contact community support.
• Support Telegram.
• support@boosterx.org.

If the offer of public contacts is available, enter the links as a single text up to 500 characters. Contacts are shown after review. The “Remove my contacts” button allows you to remove their display. An application by itself does not grant a badge and does not publish unreviewed contacts.

Result compatibility

For accepted publications, a single rating is used without separate division by methodology version. Old entries may be retained and recalculated as long as the server permits their display. The presence of an old result in the table does not mean that its measurement scenario has become identical to the new one.

A change in weights can be applied to saved measurements. Fixing the workload itself requires a new test: an arithmetic recalculation does not reproduce the work that the old engine did not perform. If a component score is unavailable, it must not be interpreted as a zero result.

How to read the table

1. Choose the metric: overall PC Score, CPU Score or GPU Score.
2. For similar configurations, use “Same CPU”, “Same GPU” or filters.
3. Compare the source metrics, memory, driver and conditions, not just the place.
4. Remember that a synthetic workload does not predict the exact FPS or 1% Low of a specific game.

If there is a temporary viewing restriction, wait for the specified time and repeat the request. Frequent refreshes do not speed up the removal of the restriction. Local measurements and already saved results do not disappear because of a rating read restriction.

Before publishing

1. Run Candidate and wait for it to complete.
2. Review the result and the messages about run quality.
3. Check the nickname and the list of information being sent in the “Publish result” block.
4. Send the result and wait for the server response. If review is needed, use the displayed status and support.

Updated: 2026-10-02. Available features depend on the client version and server settings.