Use the source that establishes the claim
Provider page IDs and lobby game IDs are stored separately. We leave a field unfilled when the reviewed evidence does not establish it, rather than copying values from a similar title or guessing an active configuration.
| Claim | Preferred evidence | How it is described |
|---|---|---|
| App coins and progression | Bagelcode’s official site, support and app-store listings. | A rule or feature of the named social app. |
| Game RTP, volatility and maximum win | The named game provider’s product material. | Provider specifications, separate from active lobby settings. |
| Lobby availability | An inspected catalog card and its game identifier. | A title observed on the review date. |
| Promotion and payment details | The relevant rule screen, payment page or VIP table. | A field-specific observation with the screen location. |
| US state rules | The individual state regulator’s published material. | A legal context reference; no inference of this operator’s authorization. |
Label calculations and show what was inspected
Promotion examples use the published components and show whether a percentage includes the original deposit. Hypothetical wagering inputs are labeled as examples. A total turnover figure describes the amount to stake under the entered conditions; it does not predict profit.
Screenshots show the relevant lobby catalog or promotion rules. Captions describe the actual screen and capture context. We exclude account details, balances and transaction information from published image regions.
An advertised payout speed is described as an advertisement. Payment-brand logos record what is displayed and do not establish that each method supports deposits, withdrawals or a fixed delivery time.
Review dates and corrections
The review date states when the cited facts were checked. It does not imply continuous monitoring. When a source conflicts with another screen, we identify the relevant field and the basis for the value used. The withdrawal minimum follows the payment page as confirmed by the operator.
To report an error, send the page URL, the disputed statement and supporting source through the customer service route on our Contact page. If a source becomes inaccessible, we pause that verification and retain the limits of the last supported observation.
Articles are credited to the Club Vegas Bets editorial team. We disclose our shared operator with 876.GAME and do not present this coverage as an independent operator comparison.
Common questions
Editorial checks
Read the answers alongside the sources and review date listed in this guide.
Does a provider RTP verify the lobby’s current RTP?
No. A provider product page establishes the published specification. The active game configuration needs its own verification and is described separately.
Are the calculator defaults an operator offer?
No. Defaults are hypothetical inputs used to explain wagering arithmetic. Verified promotion components are sourced and labeled separately.
How can I report a factual error?
Use the Contact page’s Account → Customer Service route. Include the page URL, the statement to correct and a source that supports the change.
Sources and checks
- Club Vegas official game and FAQ pagesChecked
- PG Soft: Fortune Tiger product specificationsChecked
- 876.GAME first deposit promotionPromotion → Recharge Promotion → First DepositChecked
The operator confirmed that the inspected channel matches the production channel.
- 876.GAME payment pageDeposit → WithdrawChecked
The operator confirmed that the payment page minimum of $16 takes precedence over the older VIP prose.
- 876.GAME customer service menuAccount → Customer ServiceChecked