How the Payout Speed Index is measured
This page is the audit trail behind every number in the Payout Speed Index. The short version: we publish only what we can timestamp, and where we have no measurement, the index shows a TODO instead of an estimate. No figure on this site comes from an operator’s marketing page.
Logged test protocol (primary data)
Each data point is one real withdrawal on a real, funded, fully verified player account:
- Deposit and play-through with our own money at the operator under test (licence of record stated on its review) .
- Request timestamp recorded at the second the withdrawal is submitted.
- Approval timestamp recorded when the operator releases the payment (cashier status or confirmation email, whichever is earlier).
- Arrival timestamp recorded when funds are spendable at the destination.
- Context captured per test: rail, amount band, weekday/weekend, time of day, whether KYC was pre-cleared, account age.
Each rail’s index figure is the mean of its logged tests; the sample size column shows exactly how much evidence sits behind the mean. Below logged tests, the cell stays TODO.
Crowdsourced reports (secondary data)
Reader-submitted timings are accepted once the submission includes screenshots of the request and arrival confirmations with visible timestamps . Crowd reports are stored separately, marked as such, and never mixed into the logged-test averages — they corroborate, they don’t substitute.
What we deliberately don’t do
- No extrapolation from one test to “typical” claims.
- No averaging across rails (a casino isn’t “fast” — a casino on Trustly on a weekday is).
- No paid placement in the index. Operators cannot buy a row, a rank, or a retest — commercial relationships are disclosed on the affiliate disclosure page and have no data pathway into the index.
Update cadence
Every rail is retested on a rolling cycle , and the index shows its last-updated date. Historic data points expire out of the average after so the index reflects current behaviour, not reputation. Verification-time measurements feed the KYC page; anomalies (stuck payouts, changed processing patterns) feed the troubleshooting guide.