Core reward
$70.00House-edge rakeback using the entered rate and contribution.
CRYPTO CASINORAKEBACKRun the numbersCombine documented core rewards with cashback and credits observed in the account—without counting the same value twice.
Deep VIP ladder with weekly, monthly and higher-tier reload rewards.
House-edge rakeback using the entered rate and contribution.
No stable lossback layer is recorded for this operator.
Enter the combined cash value actually credited during the month.
Do not add a reward already counted in the core formula.
Use cash-equivalent value after any wagering cost, not the banner amount.
Private VIP credits belong here only after they have been received.
0.140% of turnover · 3.5% of theoretical house cost
Avoid double counting: some “weekly” or “monthly” bonuses are already funded from the same reward pool. Only add separate credits that can be verified in the account ledger.
Two operators with the same rakeback percentage can produce different usable value when one adds weekly cash and the other delays half the reward. The stack separates calculated, delayed and manually verified amounts.
Unknown private bonuses stay unknown until the player enters an observed credit.
Only economically separate credits: base rakeback, separate loss cashback, weekly or monthly payments, reload value and one-off VIP credits that were actually received.
The documented core formula is calculated once. Other fields are labelled observed and should include only credits that do not come from that same reward pool.
Private reloads, host bonuses and milestone values cannot be estimated honestly before they appear in the account. Entering observed cash value avoids inventing an average.
The core layer displays Unknown. The tool can still total verified credits from the player’s ledger without pretending the hidden formula is zero.
It shows how much of the game’s expected cost the rewards offset. It does not predict actual gambling results or make negative-expectation play profitable.
Yes, when our database contains a documented lossback range. It remains off by default because not every player qualifies and combining it with other layers can cause double counting.