Signature asset
The cashout clock
One figure per operator: the median number of hours between a submitted withdrawal request and money a player can spend. Here is how that figure is built, what it deliberately ignores, and when it gets thrown out.
Where the clock starts
It starts when the request is submitted in the cashier. Not when the operator marks it approved, not when the transaction is broadcast.
That choice is the whole argument. Operators quote from the approval point because it flatters them. A brand with a 48 hour review queue and a two minute Litecoin payout will describe itself, accurately and uselessly, as paying in two minutes. Measured from submission, the same brand takes two days.
Alongside the median, every entry carries a 90th percentile figure. That is the bad day: the tail where a manual review, a weekend or a document request lands. A casino with a 20 minute median and a 60 hour tail is a very different proposition from one sitting flat at 90 minutes, and averaging them into a single friendly number hides exactly the thing a player needs to know.
The three legs
Approval. The operator holds the request while risk rules run. Published windows range from zero, meaning automated release, up to 72 hours. Wording matters here: up to 24 hours and within 24 hours behave identically on a bad day, while subject to review with no stated ceiling is treated as unbounded and disqualifies the operator outright.
Processing. The payment leaves the operator's account and hits the rail. On crypto this is usually minutes. On fiat it depends on batch runs, which is why an operator with a single daily payout run at 10am can never beat a competitor that releases continuously, whatever the marketing says.
Settlement. Ten minutes per Bitcoin block, 2.5 minutes for Litecoin, roughly three seconds for USDT on Tron, twelve to fifteen seconds for the same token on Ethereum, one to five business days for a wire. Settlement is the only leg that is independently verifiable, and it is almost never the problem.
Sources, in order of weight
The operator's published terms and cashier pages. These set the ceiling: whatever a brand commits to in writing is the best case it has agreed to be held to.
Timings reported across the market by player accounts, gathered from public complaint threads, forum posts and reader submissions. Each record carries a date, an amount band, a rail, a country and whether the account was already verified.
Chain data. Settlement times are checked against block explorers rather than accepted on trust, because a transaction hash either exists at a given timestamp or it does not.
Payment provider documentation for fiat rails, which publishes its own settlement windows and cut off times.
An operator needs at least 30 usable records inside a rolling 90 day window before a number is published. Below that threshold it stays unrated, and unrated means unlisted. No entry is ever built from published terms alone.
Median, not average
A single disputed payout that drags on for fourteen days will pull an average past anything useful, and the same event pulls it back the moment it drops out of the window. The median absorbs it. The 90th percentile still shows it.
Records are banded by amount, because a 200 withdrawal and a 20,000 withdrawal do not travel the same road. Anything above an operator's stated manual review threshold is recorded separately and never blended into the headline figure. Where an operator publishes no threshold, the band above 5,000 is reported on its own.
Rails are also kept apart. One number per rail, then the fastest supported rail sets the sort position, with the slowest also printed on the entry so nobody deposits on a card and then wonders.
Business days, converted
The most durable piece of misdirection in this industry is the phrase one to three business days.
Submitted Monday at 9am, that is Thursday. Submitted Friday at 6pm, that is Wednesday: five calendar days for the identical promise. Add a public holiday in the operator's jurisdiction and it stretches again, and the jurisdiction is rarely the player's.
Every figure on this site is in calendar hours. Business day language is converted using the operator's stated processing hours and time zone, and weekend submissions are modelled at the Friday evening worst case rather than the Monday morning best case.
Voided readings, rechecks and delisting
A record is discarded when bonus wagering was still outstanding, when the account was unverified at an operator that verifies late, when the amount sat above the manual review threshold, or when the operator had a documented outage or platform migration running.
Payouts withheld for an alleged terms breach are not timing data and never enter the calculation. Repeated cases feed a separate note on the operator entry instead, because a fast payout that never arrives is not fast.
Rechecks run monthly. Two consecutive cycles above 24 hours and the operator is delisted with a dated note. That rule applies identically to brands that pay this site and brands that pay it nothing, which is explained without euphemism on method and funding. The current roster is at fast payout casinos.