1
Open the verified entry
Open the operator's verified APK page. Check the URL bar, the certificate and the domain spelling.
APK download
Verify the APK before the first install.
File size, SHA-256 checksum and publisher certificate. The reading desk walks through seven install steps and three trouble patterns on first run.
Verification desk
Three checks before the first install.
- File size: the published APK file size is in the 60-90 MB band. A file outside that band may be a tampered build.
- SHA-256 checksum: the operator publishes a checksum on the download page. Match it against the downloaded file before installing.
- Publisher certificate: the publisher name on the certificate matches the registered company on the about page.
Install steps
Seven moves the desk walks through.
2
Read the file size
Confirm the published file size is in the 60-90 MB band. A file outside that band may be a tampered build.
3
Match the checksum
Compute the SHA-256 of the downloaded file. Match it against the operator's published checksum.
4
Enable unknown apps
Enable "install unknown apps" for the verified browser only. Do not enable it system-wide.
5
Run the install
Confirm the install prompt. Read each requested permission before granting.
6
Disable unknown apps
Disable "install unknown apps" for the verified browser after the install completes.
7
First launch
Sign in through the verified entry. Verify the certificate inside the app matches the about page.
Permissions
What the APK asks for and why.
| Permission | Used for | Read before granting |
|---|---|---|
| Camera | KYC document capture | The app does not store camera frames outside the verification flow. |
| Storage | KYC uploads, contest statements | The app does not request access to contacts or media files outside the verification flow. |
| Notifications | Contest alerts, deposit confirmations | Notifications can be turned off in app settings. |
| Network | Contests, withdrawals, KYC | The app needs network for contests and withdrawals. |
Trouble on first install
Three errors and the desk's first response.
Install blocked: enable "install unknown apps" for the verified browser, retry, then disable the setting. Checksum mismatch: do not install. Re-download from the verified entry and recompute. Permission denied: the app will prompt again at first KYC upload. Read the prompt before granting.
Open the support deskWhen the APK is the right path
Three situations where the APK wins.
- Google Play is unavailable in the user's region.
- The device runs Android 8.0 to Android 11 and needs lock-screen push notifications.
- The user prefers a standalone install with offline access to the cached fixture list.
APK versus PWA
When the PWA path is enough.
The PWA path is enough for users with a verified account and a stable network. The APK path is needed when Google Play is unavailable, when the device runs an older Android version, or when push notifications must reach the lock screen.
Source
Where the desk sourced the verification rows.
File size band, permission list and publisher name are taken from the operator's published download page, captured 2026-08-17, marked subject to confirmation. The reading desk updates these rows when the operator publishes a change.
Related reading
Three routes the desk opens after the APK install.
APK versus PWA
When the PWA path is enough.
The PWA path is enough for users who already have a verified account and a stable network. The APK path is needed when Google Play is unavailable in a region, when the device runs an older Android version, or when push notifications must reach the lock screen on Android 11 and below.
First-run checklist
Six items the desk opens before the first launch.
- Verify the source: install only from the operator's verified entry.
- Read the permissions: camera, storage, notifications. A real-money app does not need contacts or microphone.
- Set a deposit limit: the responsible-play tools are in account settings.
- Confirm state eligibility: six states currently restrict paid contests.
- Complete KYC: PAN, identity proof, address proof and bank proof.
- Bookmark the support route: save the customer-care channel inside the app.
What the desk will not print
Two columns the desk refuses to print.
The desk does not publish a "guaranteed safe APK" verdict. A checksum match is a soft signal, not a guarantee. The desk also does not publish a "fastest install" path. Install speed depends on the device and the network.
How the desk reads the APK
Reading the APK as a verification chain.
The APK is a verification chain, not a single download. File size, SHA-256 checksum and publisher certificate. Each link is a row the desk can verify. A mismatch in any link is a phishing signal.
Three checks the desk runs
- File size: the published APK file size is in the 60-90 MB band. A file outside that band may be a tampered build.
- SHA-256 checksum: the operator publishes a checksum on the download page. Match it against the downloaded file before installing.
- Publisher certificate: the publisher name on the certificate matches the registered company on the about page.
Seven install steps
- Open the verified entry.
- Read the file size.
- Match the checksum.
- Enable unknown apps for the verified browser only.
- Run the install.
- Disable unknown apps after the install completes.
- First launch with the verified entry.
Permissions in plain English
- Camera: used only for KYC document capture. The operator does not store camera frames outside the verification flow.
- Storage: used for KYC uploads and contest statements. The app does not request access to contacts or media files outside the verification flow.
- Notifications: used for contest alerts, deposit confirmations and KYC status. Notifications can be turned off in app settings.
- Network: the app needs network for contests, withdrawals and KYC.
FAQ
Five questions about the APK download.
How do I verify the APK?
Check the file size (60-90 MB band), match the SHA-256 checksum against the operator's published value, and confirm the publisher certificate matches the registered company on the about page.
Why is "install unknown apps" needed?
Android blocks APKs from sources other than Google Play. Enable "install unknown apps" for the verified browser only, then disable it after the install completes.
What if the checksum mismatches?
Do not install. Re-download from the verified entry and recompute the SHA-256. A mismatch indicates a tampered build.
Which Android versions are supported?
The APK supports Android 8.0 and above. Devices below 8.0 fall back to the mobile-web path.
Why does the APK request camera access?
The APK uses the camera for KYC document capture. The operator does not store camera frames outside the verification flow.
Reading-list appendix
Three articles from the news desk that deepen this route.
The news desk publishes dated and sourced explainers on contest decisions, scoring rows, withdrawal cycles, state rules and captain math. Each article is names myteam11in.com as the publisher and cited to the operator's published page.
The 100-credit draft article covers the lobby label, the cap, the carry-over rule and the expiry window. The UPI withdrawal cycle article covers the cycle in nine steps, with a redacted screenshot checklist. The state-rules article covers the federal framework, the six restricted states and the MeitY PROG Act 2025 reporting requirements.
The captain-slot article covers two clocks: the captain slot lock and the toss time. The captain pick is a multiplier, not a reputation. The scoring-edge-cases article covers run-outs, stumpings, the duck rule and the maiden over. Each article is read in five minutes.
Glossary
Six terms the desk uses across all routes.
- Captain multiplier: 2× the player's points. Locked at team creation. Cannot be edited after the contest closes for entries.
- Vice-captain multiplier: 1.5× the player's points. Becomes captain if the captain is absent or did not bat or bowl.
- Gullak-Cash variants: two bonus variants the operator publishes on the rewards page: 80/250/400 INR and 82/252/402 INR.
- KYC: know-your-customer. The operator's verification step. PAN, identity proof, address proof and bank proof. Required before the first withdrawal.
- Restricted states: Andhra Pradesh, Assam, Odisha, Telangana, Sikkim and Nagaland. Paid skill contests are restricted. Free contests may be available.
- Self-exclusion: a published window during which the operator does not allow contest entry, deposit or withdrawal request.
Primary action
Install only from the operator's verified entry.
Match the checksum before installing. Disable "install unknown apps" after the install completes.
Play Now