Rummy Mate 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. ₹149 welcome offer and ₹400+. These are Rummytrove observations; current amounts and rules inside the App take precedence if they change.
Rummy Mate 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. ₹149 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 Mate therefore has a stronger record than a marketing-only page, while final settlement remains an open result.
What the Rummy Mate name alone cannot establish
Current search records contain generic rummy pages and social posts but no dependable chain from operator to package, signer and build. The tested interface record remains useful even though the Android identity fields are still open.
No package-bound official source is assigned to this record. Current searches did not produce a package-bound Rummy Mate record strong enough to establish a developer, version, APK size or update date. Generic rummy pages and a social post were excluded from the technical fields. Source scope: No package-bound public source accepted
Rummy Mate offer-to-withdrawal calculation
In the Rummy Mate record, ₹149 amount equals 37.3% of the ₹400 threshold, leaving ₹251 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 Mate, the 55-page Rummytrove comparison measured on 8 September 2026 places ₹149 is ₹40 above 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 Mate
The session used rupee-denominated amounts on Android 14; state-level availability and location restrictions were not checked. For Rummy Mate, 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 Mate 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 Mate user should check current official eligibility and the latest in-App terms before depositing.
Amount neighbours for Rummy Mate
For Rummy Mate, 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.
- 334 Rummy: Approx. ₹149 welcome offer with ₹400+.
- Rummy Hero: Approx. ₹149 welcome offer with ₹400+.
- Holy Rummy: Approx. ₹150 welcome offer with ₹400+.
When weighing Rummy Mate 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 Mate record supports
- Supported: one Android 14 path reached registration, offer, deposit and withdrawal-request initiation.
- Supported: Approx. ₹149 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 Mate
The next Rummy Mate 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 Mate name search is unusually broad
“Mate” is a generic relationship word, so searches for Rummy Mate return social posts, general rummy articles and unrelated products. None of those results supplies a package-bound developer, version, file size and signer that can be connected to Rummytrove’s Android 14 path. Leaving the technical fields blank is therefore a positive data-quality decision: it prevents a plausible-looking search result from becoming false App identity.
The first-hand record still has value. It places approximately ₹149 beside a displayed ₹400+ threshold and documents four reached stages. What it does not contain is a device model, installer source or final payout. A reader can use the record to understand the observed funnel while refusing to infer ownership from the word “Mate.”
What would resolve the Rummy Mate identity gap
The shortest reliable bridge would be a publisher-controlled page that names an Android package, followed by a certificate match from the installed file. A version number alone is insufficient because generic APK pages can rename the title without changing the underlying binary. Rummytrove’s next capture should retain the package label before registration, the signer fingerprint, version code, requested permissions and a SHA-256 hash.
During the money-flow retest, the ₹149 display should be classified as cash, bonus or locked credit. The ₹400+ request screen should then be recorded with KYC status, receiving rail and processing outcome. These Rummy Mate-specific gaps matter more than adding another generic feature list: they determine whether the existing workflow can be reproduced on the same build.
