Rummy Go combines a Rummytrove first-hand test path with a separately labelled Android/source record. One test session on Android 14 during 20 July–1 September 2026 reached registration, offer, deposit and withdrawal-request initiation. It recorded approximately ₹111 and a displayed ₹500+ minimum. Current in-App values take precedence when they change.
Rummytrove evidence ledger for Rummy Go
| Checkpoint | Recorded result | Evidence meaning |
|---|---|---|
| Platform and window | Android 14 · 20 July–1 September 2026 | Dated Rummytrove session |
| Registration | Completed | Account-entry stage reached |
| Welcome offer | Completed · approximately ₹111 | Offer appeared in the tested path |
| Deposit | Completed | Deposit stage passed |
| Withdrawal | Initiated · ₹500+ displayed | Request stage reached; settlement separate |
For Rummy Go, registration → offer → deposit → withdrawal request is more useful than a promotional slogan. “Initiated” records the request stage, not money received by a bank or UPI destination. For Rummy Go, a single Android 14 session in 20 July–1 September reached registration, offer, deposit and withdrawal-request screens. It is not settlement proof; missing fields are device model, session screen.
How the Rummy Go amounts relate
In Rummy Go, ₹111 is 22.2% of ₹500 and leaves ₹389. This is a calculation of Rummytrove fields, not a promise that welcome credit is directly withdrawable; play-through, eligible-game, account and KYC rules may still apply.
For Rummy Go, the 55-page Rummytrove set measured on 8 September 2026 shows that ₹111 is ₹2 above the ₹109 offer median and ₹500 is ₹200 above the ₹300 withdrawal median. That places the amounts in context without turning them into safety or payout scores.
Rummy Go Android identity and source trail
The source snapshot uses apkpure.net; package com.rummygo is recorded. Status: “Public source found.” Classification: “Multiple products share this name.” Source record checked 2026-09-01.
| Identity field | Rummy Go record |
|---|---|
| Developer | SHANKARAO PRAJAPATIYA TECHNOLOGY (public mirror) |
| Package name | com.rummygo |
| Version | 2.5 |
| APK size | 14.5 MB arm64 XAPK |
| Android requirement | Android 7.1+ |
| Source update | 2026-02-20 |
The selected mirror supplies a coherent version, package, signer, architecture, size and Android requirement for com.rummygo. Rummy Go 101 uses another developer, package and file profile and is retained only as a name-collision reference. Scope: Current package-matched public mirror for com.rummygo; a separate Rummy Go 101 product and the monetary session are not merged.
Amount-to-identity boundary: The approximately ₹111 offer and ₹500+ threshold are not attributed to com.rummygo because the Android 14 session did not capture the installer package.
India-use evidence for Rummy Go
The session used rupee-denominated amounts on Android 14; state-level availability and location restrictions were not checked. In the Rummy Go record, a deposit step was completed during the one Android 14 session; the specific UPI, bank, card or wallet rail was not recorded. A withdrawal request was initiated once; the receiving UPI ID or bank account and completed settlement were not checked. No completed KYC document submission or approval was recorded during the one-session path.
Rummy Go has rupee-denominated evidence, but that alone does not establish current state eligibility. India Code records the Promotion and Regulation of Online Gaming Act, 2025, while MeitY lists 2026 rules and enforcement material. Check current official requirements and the latest App terms before depositing.
Amount neighbours around Rummy Go
The three records below are numerically close to Rummy Go; Rummytrove does not treat them as shared operators, packages or payout outcomes.
- Rainbow Rummy records Approx. ₹99 welcome offer (Rummytrove test) and ₹500+ displayed in Rummytrove test.
- INR Rummy records Approx. ₹125 welcome offer and ₹500+.
- Rummy Bloc records Approx. ₹75 welcome offer (Rummytrove test) and ₹500+ displayed in Rummytrove test.
When comparing Rummy Go, examine amount, test depth, Android identity and current terms separately. A lower threshold cannot compensate for an unknown signer, and a package record cannot turn request initiation into settlement proof.
What the Rummy Go record supports
- Workflow: Rummy Go reached four recorded stages on Android 14.
- Amounts: Rummytrove retained ₹111 and ₹500+.
- Identity: Package
com.rummygois recorded; The source snapshot usesapkpure.net. - Open result: final settlement, receiving route and unrecorded KYC decisions remain separate.
Next verification target for Rummy Go
A future Rummy Go check should retain the App-info screen, package, version code, signer fingerprint, permissions, device model and dated screenshots together. Payment testing should record the deposit rail, KYC prompt, withdrawal destination, request timestamp and final status. That improves reproducibility without erasing Rummytrove’s earlier evidence.
Rummy Go has a coherent XAPK record with a narrower scope
The selected technical profile ties package com.rummygo to version 2.5, a 14.5 MB arm64 XAPK, Android 7.1+ and the developer label SHANKARAO PRAJAPATIYA TECHNOLOGY. This is stronger than a title-only page because the package, architecture, size and signer information describe one release family. It still remains separate from Rummytrove’s ₹111/₹500+ Android 14 session until the installed package and certificate are compared.
The XAPK format also matters: 14.5 MB describes the selected arm64 bundle, not necessarily the final installed footprint or a universal APK for every device. Rummytrove therefore avoids turning that file size into a broad compatibility promise.
Rummy Go 101 is not a version of this record
Rummy Go 101 uses another developer, package and file profile. The extra “101” is an identity boundary, not a minor keyword variation. A future Rummy Go retest should capture com.rummygo, the certificate and CPU architecture before connecting the observed offer or withdrawal screen to the XAPK record. That check will show whether the strong technical profile and the first-hand workflow describe the same product.
