How We Rate
What a score cannot tell you
A single number collapses six axes into one, and anything collapsed loses information. A 4.3 out of 5 on this site does not mean the operator will be a 4.3 for every reader: a slot player who deposits in PKR with EasyPaisa will experience Zentra Bet very differently from a sports bettor using Neteller. We publish the score, but we also publish the six axis sub-scores next to it, and we invite the reader to weight them according to what matters to that reader. The score is a summary, not a verdict.
The six axes
The six axes are: bonus value (headline match, free spins, wagering, maximum bet, expiry), payments (PKR support, deposit speed, withdrawal speed, fees, limits), game library (slot count, provider mix, live tables, jackpot pool), mobile (Android app, iOS app, mobile web parity), support (channels, response times, local-language cover), and licensing (authority, dispute mechanism, responsible-play tools). Each axis is scored out of 5, each is weighted equally, and the final figure is the arithmetic mean rounded to one decimal.
A walked-through example
Take payments. A 5.0 requires PKR deposits in under five minutes, PKR withdrawals in under 30 minutes, zero fees, at least four methods including both Jazz Cash and EasyPaisa, and no documented currency conversion losses. A 3.0 means PKR is supported but withdrawals take a day on average and only two methods are available. A 1.0 means PKR is accepted but every deposit converts through USD with a loss. The sub-scores are not negotiated — the writer fills a short checklist, and the number falls out of the checklist.
What a test visit looks like
A test visit is a real session with a real deposit. The writer registers an account, deposits the minimum (20 PKR) through the method under review, plays a token amount, requests a withdrawal, and times every step. The screenshots and the timings are archived on an internal server and are the basis for the sub-score. A visit lasts anywhere from an hour (if the withdrawal clears quickly) to three days (if the operator asks for KYC documents). We do not accept comp accounts or promotional balances for test visits; the test has to represent what a real reader would experience.
When we re-check
The main review is re-run every 90 days. Payment pages are re-checked every 30 days because methods move the fastest. Bonus pages are re-checked whenever the headline offer changes — the writer watches a short list of brand terms URLs and gets a notification on any change. The responsible play page is re-checked every 90 days against the current responsible-play tools inside the account. Each re-check updates the "last reviewed" date under the H1 and, if anything changed, leaves a short note in the Corrections section at the bottom of the page.
What drives each axis
Bonus value is driven first by the ratio of headline match to wagering, second by the maximum bet during the bonus, third by the free-spin count and the games they open. Payments is driven first by PKR support, second by speed, third by fees. Game library is driven first by the live-casino quality (because mediocre slots are easy to find and good live tables are not), second by the slot count, third by the jackpot pool. Mobile is driven first by app presence, second by mobile-web parity, third by push notifications. Support is driven first by channel coverage, second by the response time we measured, third by Urdu-language cover. Licensing is driven first by the authority (a serious regulator counts for more than a flag of convenience), second by the dispute mechanism.