How We Rate Dice Sites
We rate CS GO (CS2) dice sites on six weighted criteria, each scored 0-10. The weighted total, shown to one decimal, decides the order. This page explains the rubric, the formulas, the labels and what we do and do not test. CS2DICE is an independent comparison site with no commercial relationship with any listed company.
What we rate and why
We rate the things that decide whether a dice site is fair to play and safe to use: proof that rolls are fair, evidence that the operator is licensed, the house edge on dice, how money moves in and out, player protection and public reputation. We do not rate bonuses, and welcome offers carry wagering terms, so they are not part of the score.
Rating rubric
| Criterion | Weight | What earns a high score |
|---|---|---|
| Fairness proof | 25% | Provably fair dice with a working seed verifier, seed rotation, client-seed control |
| Licence evidence | 20% | Licence number or registry entry we could check (Verified > Operator claim only > None stated) |
| House edge and dice quality | 20% | Published or derivable house edge on dice (lower is better), win-chance range, autobet, min bet |
| Deposits and withdrawals | 20% | Skins, crypto and card options; documented speeds; clear KYC and trade-hold rules |
| Player protection | 10% | Deposit limits, session limits, reality checks, self-exclusion, KYC policy, helplines |
| Reputation and support | 5% | Public track record, complaint handling, support channels; third-party review signals |
Scoring anchors: 0, 5 and 10
| Criterion | 0 means | 5 means | 10 means |
|---|---|---|---|
| Fairness proof | No fairness mechanism described | Provably fair claimed, but no seed verifier or documented algorithm | Provably fair dice with a working seed verifier, seed rotation and client-seed control |
| Licence evidence | No licence published | A licence is named, but no number or registry entry can be matched | A licence number or registry entry we could check and confirm |
| House edge and dice quality | House edge unknown or very high | Edge derivable but above the typical 1% for crypto-native dice, or little dice detail | Low published or derivable edge, wide win-chance range, autobet and a low minimum bet |
| Deposits and withdrawals | One method, no documented speeds or rules | Two methods or documented speeds without clear KYC and trade-hold rules | Skins, crypto and card, documented speeds, and clear KYC and trade-hold rules |
| Player protection | No tools described | Self-exclusion or one limit tool listed | Deposit limits, session limits, reality checks, self-exclusion, a KYC policy and helplines |
| Reputation and support | No public record or support channel | Some public record or one support channel; mixed third-party signals | Long public record, complaint handling, several support channels and positive third-party signals |
Total score formula
Total = 0.25 x Fairness + 0.20 x Licence + 0.20 x House edge + 0.20 x Payments + 0.10 x Protection + 0.05 x Reputation. Example: PLG.BET scores 8, 7, 8, 9, 8, 6, so 2.00 + 1.40 + 1.60 + 1.80 + 0.80 + 0.30 = 7.90, shown as 7.9. A total that ends in 5 at the second decimal is rounded up, so CSGORoll's 6.35 is shown as 6.4.
| Rank | Operator | Fairness proof | Licence evidence | House edge and dice quality | Deposits and withdrawals | Player protection | Reputation and support | Total |
|---|---|---|---|---|---|---|---|---|
| 1 | PLG.BET dice review | 8 | 7 | 8 | 9 | 8 | 6 | 7.9 |
| 2 | Duelbits dice review | 8 | 6 | 6 | 6 | 6 | 6 | 6.5 |
| 3 | CSGORoll dice review | 8 | 4 | 6 | 8 | 5 | 5 | 6.4 |
| 4 | CSGO500 dice review | 7 | 5 | 6 | 7 | 5 | 5 | 6.1 |
| 5 | Stake dice review | 6 | 5 | 6 | 7 | 6 | 6 | 6.0 |
See the same scores with evidence in the extended rating on the home page.
House edge derivation
When a dice game shows a multiplier and win chance, we derive its house edge from them: edge = 100 - (displayed multiplier x win chance). Example: 1.86x at 53.01% gives 100 - 98.6 = 1.4, so about 1.4%. Displayed numbers are rounded, so treat the result as approximate. A derived figure carries the label "Derived" and the date we recorded it. Where we have not derived an edge ourselves, we show the widely reported figure with the label "Reported".
Label definitions
| Label | Meaning |
|---|---|
| Derived | We calculated the value from numbers shown in the game itself, such as the house edge from a displayed multiplier and win chance, and recorded the date. |
| Reported | A widely reported figure or description that we have not measured ourselves, for example a payout time or a published RTP. |
| Verified | Confirmed by us directly, such as a licence number matched to a regulator registry. We do not use this label unless the check was completed. |
Licence and fairness details are shown as published by each operator. A licence listing is not proof of safety, and we treat licence information as unconfirmed until we have matched it to a registry entry.
Data sources and update policy
We combine public information about each operator, our own observation of its dice game, and independent reports and tests. Third-party figures are labelled "Reported", and figures we calculate ourselves are labelled "Derived".
We plan to recheck each operator at least every quarter and sooner when we hear of a change. The "Last verified" date on the home page and the "Checked" date on each review show the latest check.
What we do and do not test
- We do: collect public information, derive edges from displayed values, compare claims with documents, and review licence and fairness details.
- We do not: claim to have deposited, withdrawn or timed payouts unless a review says so. Withdrawal speeds shown are labelled "Reported" unless we tested them.
Independence
CS2DICE is an independent comparison site with no commercial relationship with any listed company. We take no payments for placement, no pay-for-rank and no commissions. Outbound links go to the operator's own URL with no tracking parameters. Read more about us.
Corrections
If you spot an error or an operator has updated its data, tell us through the contact page with a source link. We check the claim, update the page and add a line to the change log below.
Change log
- 2026-11-10