Rummy Bash is backed by a Rummytrove first-hand Android 14 test record. One test session during 20 July–1 September 2026 reached registration, the welcome-offer step, deposit and withdrawal-request initiation. The same path recorded Approx. ₹101 welcome offer and ₹400+. These are Rummytrove observations; current amounts and rules inside the App take precedence if they change.
Rummy Bash test path and evidence
| Checkpoint | Recorded result | Interpretation |
|---|---|---|
| Platform and window | Android 14 · 20 July–1 September 2026 | Dated Rummytrove session context |
| Registration | Completed | The account-entry stage was reached |
| Welcome offer | Approx. ₹101 welcome offer | Amount displayed in the tested path |
| Deposit | Completed | The session progressed through the deposit step |
| Withdrawal | Initiated at ₹400+ | Request screen reached; settlement not recorded |
| Missing reproduction fields | Package, version/build, device model and session screen | The evidence remains attached to the product-name record |
The four reached stages document a usable funnel, but they do not all prove the same thing. Registration and deposit show progression through the interface. Withdrawal “initiated” means the request stage was reached; it does not mean a bank or UPI account received funds. Rummy Bash therefore has a stronger record than a marketing-only page, while final settlement remains an open result.
Why large Rummy Bash download claims were not imported
Rummy Bash appears across guide indexes and promotional collections, but the reviewed material does not connect a developer, package, version and signer on one build. Large counters therefore remain marketing claims rather than Rummytrove reach data.
No package-bound official source is assigned to this record. Rummy Bash appears in guide indexes and promotional download collections, but the reviewed pages did not connect a package, developer, version and signer on one build. Large promotional download figures were not accepted as public download evidence. Source scope: Guide and directory references use the Rummy Bash name, but no package-bound developer, signer or operator source was accepted on 2026-09-01.
Rummy Bash offer-to-withdrawal calculation
In the Rummy Bash record, ₹101 amount equals 25.3% of the ₹400 threshold, leaving ₹299 between them. This is a transparent calculation of the two Rummytrove fields, not a claim that welcome credit is directly withdrawable. Wagering, eligible-game, account and KYC conditions may still apply inside the App.
For Rummy Bash, the 55-page Rummytrove comparison measured on 8 September 2026 places ₹101 is ₹8 below the ₹109 offer median, while ₹400 is ₹100 above the ₹300 withdrawal median. That comparison describes dated amounts only; it does not rank legality, safety or payment reliability.
India-use evidence recorded for Rummy Bash
The session used rupee-denominated amounts on Android 14; state-level availability and location restrictions were not checked. For Rummy Bash, 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.
Because Rummy Bash displayed rupee values, the session has a meaningful India-use signal, but the test does not establish current state eligibility. India Code records the Promotion and Regulation of Online Gaming Act, 2025, and MeitY lists 2026 rules and enforcement-related material. A Rummy Bash user should check current official eligibility and the latest in-App terms before depositing.
Amount neighbours for Rummy Bash
For Rummy Bash, the nearby entries below are selected by numerical distance between the recorded welcome and withdrawal amounts. They are comparison points, not identity matches or recommendations.
- Gogo Rummy: Approx. ₹101 welcome offer with ₹400+.
- Rummy Glee: Approx. ₹100 welcome offer with ₹400+.
- Rummy Loot: Approx. ₹119 welcome offer (Rummytrove test) with ₹400+ displayed in Rummytrove test.
When weighing Rummy Bash against those records, look beyond the two rupee figures: compare package identity, workflow depth, KYC visibility and whether withdrawal stopped at request initiation or continued to settlement.
What this Rummy Bash record supports
- Supported: one Android 14 path reached registration, offer, deposit and withdrawal-request initiation.
- Supported: Approx. ₹101 welcome offer and ₹400+ appeared in that Rummytrove record.
- Not claimed: completed payout, a specific receiving rail, KYC approval or a guaranteed bonus.
- Identity still needed: package name, signer fingerprint, version code, device model and dated session screens.
Next evidence target for Rummy Bash
The next Rummy Bash retest should capture the Android App info screen before login, then retain the package, version code, signer, requested permissions and device model. If money movement is tested, the deposit rail, KYC prompt, withdrawal destination, request time and final status should be logged separately. That would connect the strong workflow record to a reproducible build without erasing the earlier Rummytrove evidence.
Rummy Bash appears in indexes but lacks release lineage
Guide indexes and promotional download collections repeatedly mention Rummy Bash, yet the reviewed pages never connect package, developer, version and signer on one build. Repetition across directories can make a listing seem established even when every page ultimately copies the same unsupported profile. Rummytrove excludes the large promotional download figures because no package-level counter or publisher source anchors them.
The dated Android session is a different kind of evidence. It recorded approximately ₹101 with a ₹400+ display and reached withdrawal-request initiation after deposit. That supports a usable path under the Rummy Bash name. It does not convert directory counters into genuine reach, and it does not prove final settlement.
Building a release lineage for Rummy Bash
A release lineage needs at least three linked points: a publisher-controlled origin, an Android package with version code and a matching signing certificate. The filename can be noted, but filenames are easily changed and should not be the primary key. A SHA-256 hash would make the dated file reproducible even if a later download uses the same title.
On the account side, the next session should identify what the ₹101 represents, capture any turnover condition and record the ₹400+ request status through completion or rejection. If the package changes between sessions, the results should stay separate. That approach gives Rummy Bash evidence continuity without relying on how many guide pages repeat the brand.
