Criteria
Within each category we rate specific items. For bonuses: match percentage, cap, wagering, expiry. For payments: minimum, maximum, processing time, PKR support. For app: size, OS floor, crash rate over a week of testing. All numbers are logged in a shared sheet.
What lowers score
Immediate downgrades: wagering above x45, bonus expiry under 7 days, withdrawal processing above 72 hours, mandatory marketing opt-in, missing responsible-gambling tools. Each of these costs the brand a full point.
Scoring
Each brand is scored from 1 to 10 on a weighted scale: bonuses (20%), payments (20%), game library (20%), app (15%), support (15%), licensing (10%). A single zero in licensing drops the whole score to zero — we do not list operators without a visible license.
Why the weights sit where they do. Bonuses and payments get 20% each because for a new account they are the first thing you touch — a bad bonus or a slow payout is felt on day one. Game library gets 20% because it is the actual product. App and support take 15% because they shape the daily experience, not the first click. Licensing is capped at 10% because every brand we list clears a base threshold — the detail inside that threshold matters, but not as much as what you can see yourself.
How we test the app. For a week we open Tucan Bit on both platforms (Android 13 on a Pixel 7a, iOS 17 on an iPhone 13) and log every crash, every forced update, and every delay longer than two seconds. The raw log goes into the shared sheet; the summary goes into the review.
How we test support. We open three tickets of different kinds (a benign question, a bonus query, a payout query) and time the first human response as well as the first substantive answer. Both times go into the score — a fast reply with no content is worth less than a slow one that solves the problem.
Rescoring cadence. Reviews are rechecked each quarter against the live operator page. If the operator has changed a term since our last check, we update the page before the end of the quarter and date-stamp the change. Historical scores are not rewritten; the current page always shows the latest number.
What we test the game lobby against. For slots we sample fifty titles across the library, note the advertised RTP, and spot-check that the game loads cleanly on both desktop and mobile. Studios missing from the lobby in the past year — a dropped supplier contract usually shows up as a thinner shelf for that studio — get flagged in the review. For live dealer rooms we open each category once to confirm it is staffed and streaming at the time of the test.
What we test the cashier against. Deposits go in from each supported method in the smallest allowed amount; withdrawals come out via the same path. The clock starts when we press the button and stops when the balance moves on the opposite side. Any method that cannot complete a round trip inside the operator's stated window loses points, and if the method is advertised as instant and comes in on second-day timing, the whole payments score drops.
How we treat negative evidence. A single reader complaint does not change a score — one bad experience can happen anywhere. A pattern across multiple readers, or a confirmed regulator action, does. The threshold is three independent reports of the same issue inside a quarter; at that point we open a ticket on the operator side and log the response before updating the score.
Why we publish the methodology at all. A scoring system that lives in a drawer is a scoring system nobody can argue with. Publishing the weights, the criteria, and the triggers means a reader can check whether the number on the review page follows from the rules on this one — and tell us when it does not.