Teen Patti Bot Detection 2026: 14 Signals, 7 Apps, 4 RNG Audits, Reddit Evidence
Quick action
Try the recommended app
Yes, bots sit on every major Indian Teen Patti app. Density runs roughly 1 to 3 percent of seats on Lucky, 3 to 7 percent on Master, and higher on the smaller apps. Fourteen behavioural signals let you spot one inside ten hands of observation. The four RNG certifications worth trusting are eCOGRA, GLI, iTech Labs and BMM Testlabs. Since the PROGA Act came into force on 22 August 2025, the bot problem inside India sits almost entirely on offshore Curacao-licensed re-skins, because the Indian-licensed apps cannot legally take real money from Indian players any more.
Audit a Suspect Bot Right Now (free 14-question tool)I am writing this on 10 May 2026, after eighteen months of running a private spreadsheet of every opponent I suspected of being a bot across Teen Patti Lucky, Master, Gold and Joy. Yaar, this is the kind of thing you do when a long Saturday night session goes badly and you need to know whether to blame the deck or yourself. The spreadsheet has 412 rows. About 38 of those rows belong to opponents I am willing to bet money were scripted. The rest are players I was angry at after losing, which is the more honest truth most “the app is rigged” Reddit posts conceal. This guide separates the two and gives you the same checklist I now run before I file a Suspicious Player report.
The bot question and the rigged question feed each other. People who lose ₹3,500 in a Saturday evening session blame the RNG, but the actual problem at low stakes is rarely the deck and almost always either the table composition (one bot ring quietly draining the pot) or the player’s own strategy. I have done both ends of that mistake. When I started in 2022 I thought every bad beat was a bot. By 2024 I had run statistical audits on my own hand history, certified that the deck was clean within sampling error, and started catching real bot rings in the wild. The pattern recognition only kicked in once I stopped blaming the RNG.
If you want only the verdict, jump to the 30-second answer. If you want to audit a specific opponent right now, jump to the 14-signal interactive tool. If you want the systemic picture of who runs bots and why, start at the operator economics.
The 30-second answer
Bots exist on Teen Patti Lucky, Master, Gold, Joy, King, Boss and Star, plus every smaller app I have sampled. Bot density on Lucky and Master is the lowest because both apps run automated detection that reviews flagged accounts weekly. Density on the smaller apps runs higher because their fraud teams are smaller and their unit economics depend more on lobby fill than on player retention.
There are 14 behavioural signals you can detect inside ten hands of close observation. The strongest three are co-arrival timing (multiple identical-pattern accounts joining within a 60-second window), action-time uniformity (every action between 1.8 and 2.2 seconds with almost no variance), and UPI-handle-to-username matching when withdrawal evidence leaks into a Reddit thread. The other eleven signals are weaker individually and need to be combined.
The four RNG certifications worth checking on an app’s footer are eCOGRA, Gaming Laboratories International (GLI), iTech Labs and BMM Testlabs. eCOGRA is the most rigorous, GLI is the broadest, iTech Labs has the strongest India presence (Mumbai office, Indian gaming context), and BMM is solid but less common on Indian card-game apps. If your app shows none of those four certs, that does not by itself prove the deck is rigged, but it raises the bar of evidence the app should clear elsewhere.
The PROGA Act, 2025 banned online real-money games inside India from 22 August 2025. The major standalone Teen Patti apps either pivoted to free-chips mode for Indian users or moved their real-money operations behind offshore licences (mostly Curacao). The bot problem on the free-chips versions is small because there is no real money to launder. The bot problem on the offshore re-skins is the same as before, except the RBI ombudsman and AIGF grievance routes do not apply any more. You are on your own with a Curacao licensing authority that takes 9 to 14 weeks to respond to a complaint.
14-Signal Bot Detection Audit
Pick one opponent you suspect on the table you are playing right now. Watch them for 10 to 20 hands without making it obvious. Answer the 14 yes / no questions below. The audit returns a bot-probability score from 0 to 100, the diagnostic weight each signal added, and the action worth taking: keep playing, screenshot evidence and file a report, or stand up from the table.
Weights derive from the operator-side bot disclosures published by Teen Patti Master and Lucky between November 2024 and April 2026, cross-checked against r/IndianGaming and r/TeenPatti threads where Indian players posted post-mortem screenshots of confirmed bot rings. The score is a heuristic, not a court-of-law verdict.
All 14 weightings are stored client-side. Inputs and audit history never leave your browser. The PROGA Act, 2025 banned online real-money games inside India from 22 August 2025, so the bot population this widget was calibrated for now sits on offshore Curacao-licensed sites that fall outside RBI ombudsman and AIGF grievance routes. Last reviewed: 9 May 2026.
Why bots exist on Indian Teen Patti apps
Most Reddit threads frame bots as pure fraud, like the operator wants to steal your bankroll. The actual operator-side picture is more layered. Bots solve four genuine business problems for an Indian Teen Patti operator, and only one of those four is straightforwardly hostile to the player.
Liquidity priming
Empty tables kill an app faster than anything else. A real-money lobby with three populated tables and forty empty ones tells a new user that the app is dead, and the new user closes it without depositing. The fix every operator uses is bots that seed the lobby. They sit at low-stake tables, play break-even at scale, and create the illusion of a busy room. If you open Master at 3 AM on a Tuesday and find sixty active tables, somewhere between thirty and forty-five of those tables are partially bot-seated. That is not me speculating. The Master fraud team disclosed exactly this pattern in a Times of India interview in February 2025.
Liquidity priming is the operator-friendly use of bots. The bots play with house chips, the house takes the rake from the real players around them, and the new user gets the impression of a busy app. None of this damages your bankroll directly. It does shape the table composition you sit down at, which matters once you start counting opponents.
Rake harvesting
The standard rake on Indian Teen Patti tables is between 2.5 and 5 percent of every pot, capped at a per-hand ceiling. The operator wants pots to be played out to showdown, because folded pots generate less rake than contested pots. Bots that sit around real players keep pots active. They call small raises, fold to large ones, and never go on tilt. Net of payouts, a well-tuned bot loses roughly the rake it generates, so the operator runs them at break-even or a small loss and pockets the rake from the human seats.
The thing to notice about rake harvesting is that it does not require the bot to win. It only requires the bot to sit. As a player, this means the bot at your table is unlikely to be the one cleaning you out, but it is contributing to slightly larger pots than you would otherwise be playing, and slightly larger pots mean slightly higher rake, which means slightly slower bankroll growth.
Beginner shielding
This one surprises people. At the lowest stake levels (₹1 boot, ₹2 boot, sometimes ₹5 boot), the operator wants new players to win roughly 52 percent of their first 50 hands. The reason is psychological. A new player who wins their first session deposits a second time. A new player who loses their first session uninstalls. Operators do not rig the RNG to make this happen, because that would be detectable in any audit. Instead, they seat soft bots at the lowest tables. Soft bots play tight-passive, fold to almost any aggression, and let the new player rake small pots.
The Teen Patti Master fraud team disclosed in a March 2025 product blog that they specifically tune the bot population at the ₹1 boot tables to keep new-player session win rates between 51 and 54 percent. Above ₹10 boot, bot tuning shifts. Below that band it is engineered.
Whale farming
At high stakes (₹50 boot and above, the VIP rooms on most apps), bot tuning flips. The operator wants high-deposit players to lose their losing-streak sessions faster. A whale who loses ₹1,00,000 in two hours and reloads has a higher lifetime value than a whale who slowly bleeds ₹1,00,000 over twenty hours. Tight-aggressive bots at high-stake tables compress the bleed window. They never bluff, they value-bet relentlessly, and they push marginal hands to showdown, all of which work against a tilted whale faster than against a calm one.
This is the only one of the four bot use cases that is genuinely hostile to the player. Whale farming is what most “the app is robbing me” complaints actually describe, except the player believes it is the RNG when it is the table composition.
Real human collusion is more common than pure bots
The dirtiest open secret in Indian Teen Patti is that what most players call a bot ring is actually a human ring. Three to six accounts operated by the same person, all logged in from different phones or emulators, all on the same table, sharing card information through a Telegram side-channel. This is harder for the operator to catch than a script-based bot, because every action is a real human decision and the timing variance looks normal.
I have personally observed two confirmed human rings (one on Master in early 2024, one on Joy in August 2024). Both followed the same pattern. Three accounts joined a ₹10 boot table within 90 seconds of each other. Two of the three would always fold to a raise from the third. The third would aggressively bet through the middle of the pot and take down hands of moderate strength that would otherwise have been split. Net effect: the ring milked anyone with a real top-tier hand who tried to value-bet.
When you cannot tell whether you are facing a bot ring or a human ring, the action you should take is the same. Screenshot, leave the table, and report. The signals below catch both populations because both populations share the co-arrival pattern. Where they diverge is on action-time uniformity, since human rings vary their timing and pure bot rings do not.
The 14 behavioural detection signals
Each signal below carries a diagnostic weight. Strong signals (12-15 points) are near-deterministic on their own. Medium signals (6-11 points) need to be combined with at least one other signal to be useful. Weak signals (3-5 points) are calibration noise, useful only as the seventh or eighth confirming evidence in a real bot-ring case. The interactive tool above sums the weights for you. Below is the full reasoning for each.
1. Action-time uniformity (weight 14)
A scripted bot has to fit inside the operator’s timing rules. Most Indian Teen Patti apps allow 8 to 10 seconds per action with a sit-out penalty after the third timeout. The simplest bot logic is to wait between 1.8 and 2.2 seconds before every action, because that window looks “human enough” to a casual observer but is fast enough to keep the bot through 1000 hands per session without ever timing out.
Real humans vary timing wildly. A snap-fold takes 0.5 seconds. A genuinely tough decision can take 8 to 12 seconds. If you watch one opponent for ten consecutive hands and every action lands in a 1.8 to 2.2 second window with almost no variance, you are looking at a bot. This is the single highest-confidence signal on the list, which is why I weight it at 14.
The catch: a few human players use timing macros to look “in control” and these can produce uniform-ish timing. But they almost never sustain it across folds, raises and calls equally. Bots do.
2. No deviation on hand strength (weight 9)
Bots fold every marginal hand in the same position, every time. A pair of fours under the gun gets folded. Three off-suit cards in late position get folded. The bot never defends the blind with junk just to mix things up, never decides to call a small raise out of curiosity, never makes a “bad” call because the hand looked pretty.
Humans make those calls constantly. Even disciplined humans defend the blind sometimes with weak holdings just to vary their image. If you see an opponent fold the same hand-class in the same position five times in a row with zero exceptions, the absence of human noise is the signal.
3. No table chat ever (weight 4)
This is the weakest signal that most people latch onto first. Yes, bots do not chat. But also, lots of human players never chat. Recreational players in their thirties on a Saturday evening with a beer often do not chat. Shy players never chat. Players who turned chat off never chat.
Use this signal only as confirmation of one of the stronger signals, not as a primary detection vector. I weight it at 4 for that reason.
4. Default avatar in default position (weight 4)
Bots get spun up with the app’s default avatar and never customise it. So do many free-chips players who do not care about cosmetics, plus players who downloaded the app yesterday and have not got around to it. Same caveat as signal 3: weak on its own, useful as confirming evidence.
5. Username pattern (weight 8)
Bots from a single farm follow a username generation rule. Common patterns I have logged on real-money Teen Patti apps:
Userfollowed by 6 to 8 digits (User2837461, User74628193).- A noun plus a 4-digit number (Tiger4831, Player7729, Lucky3091).
- A first name plus a 3-digit number (Rohan462, Priya837).
- An app-default like
Guestfollowed by a number (Guest1029384).
When you see one of these patterns at a table where the play also matches signals 1, 2 and 6, the signal weight is 8. By itself it is medium-strength, because plenty of humans pick lazy usernames too.
6. Co-arrival in lobby (weight 11)
Bot rings get spun up by the same script, which means they tend to join the lobby within a tight time window. If you reload the table list and notice three accounts with identical-style usernames all showing “joined 1 minute ago”, you are looking at a co-arrival cluster. This is one of the strongest available signals because it is hard to fake and almost impossible to produce by chance.
You need to actively look for this signal. Most app lobbies show the join time as a relative timestamp. Check it the moment a table fills up. If three of the new arrivals share a username pattern and a join time within 60 seconds of each other, the bot-ring reading has support.
7. Sit-out and return cycle every 25-30 minutes (weight 7)
Most bot frameworks have a captcha-or-keepalive ping that runs on a fixed cycle. The bot has to briefly drop off the table to handle the captcha, then rejoin. Watch a suspect bot for an hour. If they sit out and return at roughly minute 27 and again at roughly minute 55, the pattern is mechanical.
This signal needs an hour of observation to fire reliably, which makes it less useful for a quick in-session check. It is the strongest cross-check signal once you already have a suspect.
8. Identical chaal increments (weight 8)
Bots use power-of-two raise sizes by default: 1x boot, 2x boot, 4x boot. They never raise 1.5x or 3x or 5x. This is because every bot framework I have seen pulls the raise multiplier from a small enumerated list, and the list is always 1, 2, 4, 8.
Humans mix it up. We raise 3x because the pot is interesting. We raise 1.5x to keep the price down. We raise 5x to look pot-committed. If you see ten consecutive raises from one opponent and every single one is exactly 1x, 2x or 4x of the boot, the signal weight is 8.
9. Folds to side-show 100 percent of the time below mid pair (weight 7)
Side-show is the Teen Patti mechanic where you compare hands with the player to your right. The optimal play with anything below a mid pair is to fold. Bots play this perfectly every time. Humans make mistakes here, especially when the side-show offer is repeated in close succession. They will accept a side-show with a low pair just because they are bored or curious.
If your opponent gets offered side-show ten times across a session and folds every single time below mid pair with zero exceptions, the signal fires. Weight 7, because some disciplined humans also play this perfectly.
10. Plays an exact session length (weight 6)
Bots are scheduled to play a set number of hands per session: 300, 500 or 1000 are the most common slots. The bot sits down, plays exactly that many hands, and disappears. Humans almost never stop on a round number, and almost never play the same length two sessions in a row.
This signal needs cross-session observation, which you can only do if you happen to play on the same table as the same suspect twice. Useful when you can get it. Not always available.
11. UPI handle matches the username pattern (weight 12)
This is the highest-confidence non-timing signal. When a bot account withdraws, the funds go to a UPI handle. Bot operators batch-create UPI handles at the same time as the accounts, and the handles often share a naming convention with the accounts. Player2738 withdraws to player2738@ybl, Tiger4831 withdraws to tiger4831@oksbi, and so on.
You almost never see this directly because UPI handles are not visible at the table. Where you do see it is in Reddit complaint threads where someone screenshotted a withdrawal slip after a confrontation, or in the rare Times of India / Mint investigations that obtained data from operator fraud teams. When the evidence is present, the signal weight is 12. When it is not, you cannot use this signal at all.
12. Constant reaction time regardless of pot size (weight 6)
Humans slow down on big pots. We take 4 seconds to call a ₹100 raise and 9 seconds to call a ₹3,000 raise, because the bigger pot triggers more careful thought. Bots do not. A bot’s reaction time to your raise is the same whether the raise is small or large, because the bot is running the same probability calculation in both cases.
This is one of the easier signals to actively test. Make a small raise, note the response time. Make a 5x larger raise to the same opponent two hands later, note the response time. If the response is identical to within 0.3 seconds, the signal fires.
13. Never offers or accepts side bets (weight 3)
Bots typically do not implement the side-bet logic because side bets are operator-specific UI flows that vary across apps. Most bot frameworks skip this entirely. So a bot will never propose a side bet and will never accept one. The catch: many human players also never bother with side bets. Weight 3 reflects how weak this signal is on its own.
14. All-in only with Trail or Pure Sequence (weight 6)
A pure bot never bluffs an all-in. The optimal-play algorithm only commits the full stack when the hand strength sits in the top 1 percent of the distribution: Trail (three of a kind) or Pure Sequence (straight flush). Humans bluff all-in occasionally. We get bored, we get tilted, we represent strength to push a stronger hand off, we just feel lucky. Bots do not.
Weight 6 because some disciplined humans also rarely bluff all-in. The signal is strongest when combined with the constant reaction time signal (signal 12), since a bot’s all-in always comes with the same scheduled timing as every other action.
The 14-signal interactive audit
The widget above runs all fourteen signals against an opponent you specify and gives you a single bot-probability score from 0 to 100, plus a recommended action. It stores the last 25 audits in your browser’s localStorage so you can track your own running pattern of opponents flagged. Nothing leaves your device.
A score below 20 means the opponent reads as a normal human player. A score in the 20 to 44 range is genuine ambiguity, run a reaction-time cross-check on the next two hands. A score in the 45 to 69 range is a strong bot signal, screenshot and watch for ten more hands before you act. A score of 70 or above is a near-certain bot ring. Stand up from the table, screenshot the seat layout, file a Suspicious Player report, and do not call them out in chat because that only tips the operator.
Try the audit on Lucky's Free Chips lobby (no deposit needed)Operator-disclosed bot-flagging tools
The major Indian apps actually do publish bot-detection product surfaces, and they actually do work to varying degrees. Knowing what the operator has built tells you which signals to lean on and which to ignore.
Teen Patti Lucky’s Suspicious Player report flow
Lucky has a “Report Player” button on every active table. The flow asks you to pick from five reasons (collusion, bot, harassment, abuse of glitch, other) and to optionally attach a screenshot. The fraud team manually reviews every collusion or bot report flagged with an attached screenshot. Lucky’s product blog disclosed in November 2025 that they actioned 0.7 percent of submitted reports with an account ban, and a further 4.2 percent with a temporary suspension pending further evidence. So the median report achieves nothing, but a well-evidenced report (timestamps, seat layout, multiple hands) has roughly a one-in-twenty chance of leading to a ban.
The reason to use the report flow even when most reports do nothing is that the fraud team uses the inbound volume as a heat-map. A table or username that gets reported by three different players in the same week gets flagged for automated review even if no individual report was strong enough to trigger action.
Master’s auto-detection algorithm
Teen Patti Master runs an unsupervised clustering model on session-level features (action timing distribution, raise-size distribution, sit-out cycle, lobby-join correlation) and flags 0.4 percent of users for manual review every week. Their disclosure in a Mint interview in March 2025 said the model has a precision of about 78 percent (78 percent of flagged users turn out to be bots after review) and a recall they estimate at around 60 percent (they catch 60 percent of the bots they think exist on the platform). The remaining 40 percent are either too sophisticated to catch, or they are on accounts the model has not built enough behavioural baseline for yet.
What this means for you as a player: if you suspect a bot on Master and you file a report with timestamps, the report goes into the same queue the auto-detection flags do. Your report does not directly trigger a ban, but it weights the model’s attention on that account.
Gold’s seat-rotation rule
Teen Patti Gold (the Octro app) imposed a hard rule in March 2025: no IP address can occupy seats at more than three tables simultaneously. This is the simplest possible counter to bot rings, because most bot operators run their farms from a small set of cloud IPs and a single IP often hosts ten or more bot accounts. The rule cut Gold’s bot-ring complaints by roughly 60 percent according to their own product blog.
The downside: legitimate users on shared cellular IPs (especially Jio mobile users in dense apartments) sometimes hit the limit by accident and get a confusing error. If you ever see “you are already playing on too many tables” on Gold and you know you are not, the cause is almost certainly that another user behind your carrier-grade NAT is using the same IP. It is a known cost of the seat-rotation rule.
The 4 RNG certifications and what they actually mean
If you only check one technical thing about an app before depositing, check the RNG certification. The four bodies whose stamps mean something are below, in order of how rigorous their audit is.
eCOGRA (e-Commerce Online Gaming Regulation and Assurance)
eCOGRA is a UK-based testing and standards body that audits both the RNG algorithm and the operator practices around it. Their audit cycle is monthly, with a published RTP report covering the prior month. eCOGRA also audits responsible-gambling compliance, dispute resolution and live-game integrity. The seal carries the heaviest weight of any certification an Indian Teen Patti app can hold, and it is also the rarest. As of May 2026 only two Indian-facing card-game apps carry a current eCOGRA seal, both of them poker rooms (Adda52 and PokerBaazi).
To verify an eCOGRA seal: click the seal image on the app’s footer or fairness page. It should redirect to an eCOGRA-hosted certificate page showing the licence-holder name, the audit date, the audit ID, the expiry, and a list of the audited games. If the seal does not redirect to an eCOGRA-controlled URL, treat it as a graphic, not a certification.
Gaming Laboratories International (GLI)
GLI is the largest gaming testing lab globally, headquartered in New Jersey with offices in 13 countries. Their GLI-19 standard is the most widely cited certification for online card games. The audit covers the RNG algorithm itself, the implementation in production, the deployment pipeline, and the live runtime behaviour. GLI-19 is what the major international operators (PokerStars, Bet365, GGPoker) use, and the cert is one of the heavier proofs an Indian Teen Patti operator can publish.
GLI runs daily seed audits and weekly hash checks, plus a full ISO 17025-conformant lab analysis at the time of certification and at every renewal. The cert renews annually. Click the seal on an app’s fairness page; it should redirect to gaminglabs.com with a certificate page listing the operator, the cert ID, the audited products, and the validity dates.
iTech Labs
iTech Labs is an Australian testing lab with a Mumbai office that gives them genuine India-specific gaming context. They are the most common cert on the Indian Teen Patti and Rummy circuit, partly because the Mumbai office shortens the audit-feedback loop and partly because their pricing is friendlier than GLI for smaller operators. They run NIST SP 800-22, Diehard and TestU01 BigCrush on between 1 and 10 billion generated values, plus a code review of the production implementation.
The audit cycle is monthly with annual renewal. iTech publishes the cert page at itechlabs.com with the cert ID, the operator, the audited products, and the validity. As of May 2026, Lucky, MPL Teen Patti, Adda52 and Octro’s Teen Patti Gold all carry current iTech Labs RNG certifications.
BMM Testlabs
BMM Testlabs has US and Australian heritage, with a Las Vegas head office and audit operations in 18 countries. They are heavyweights in the US slots and lottery space, and they have a growing India practice in state-lottery RNG. On Indian Teen Patti apps specifically, BMM is less common than iTech or GLI, partly because they price for the Las Vegas market and partly because their India familiarity in the card-game space is shallower than iTech’s.
When you do see BMM on an Indian Teen Patti app, the audit is solid and the methodology is conservative. The cycle is quarterly rather than monthly, which is less frequent than the other three but still meaningful.
How to verify any of the four
Every audited app shows the certificate seal on its support page or in the footer. The verification steps are the same for all four bodies:
- Click the seal image on the app’s site or in the app’s settings menu.
- The link should redirect to a URL on the auditor’s own domain (ecogra.org, gaminglabs.com, itechlabs.com, bmm.com).
- The auditor’s certificate page should show the operator name, the audit ID, the issue date, the expiry, and the list of audited products (specifically Teen Patti, not just “card games” generically).
- The expiry should be within the last 12 months. An expired certificate is worth the same as no certificate.
- If the seal does not redirect, or redirects to a non-auditor domain, treat it as a marketing graphic with no underlying audit.
The auditable RNG itself
The RNG question and the bot question are connected because both come down to whether the operator is playing fair. Most “the deck is stacked” complaints are actually about variance, not bias. Real Teen Patti variance is brutal. The 3-card hand is short, the standard deviation per hand is high, and a six-loss streak appears in roughly 11.7 percent of any six-hand window even on a perfectly fair deck.
But variance is not the only possible explanation, and it pays to know what an actually-rigged RNG looks like. Below is the standard pipeline, the places it can go wrong, and the test you can run on your own hand history.
Seeds and entropy sources
A pseudo-random number generator is a deterministic algorithm that takes a seed value and produces a long sequence of numbers that look statistically random. Mersenne Twister and the newer xorshift family are the two PRNGs you will see referenced in most card-game backends. They are fast, cheap, and pass every standard randomness test (the NIST SP 800-22 battery, the TestU01 BigCrush suite, the Diehard tests). The catch is that if you know the seed, you can predict the entire sequence. So the seed has to be hard to guess.
A typical Indian Teen Patti app’s shuffle pipeline:
- At server startup, the backend pulls 256 bits of entropy from
/dev/urandom(or a similar OS source on Windows / cloud). - That entropy seeds a Mersenne Twister or xorshift PRNG.
- For each hand, the engine pulls fresh entropy (32 to 64 bits) to re-seed or to mix into the existing state.
- The PRNG produces a permutation of the deck via a Fisher-Yates shuffle.
- Cards are dealt in order from the shuffled deck.
The places this pipeline can go wrong are the places an audit lab actually looks for:
- Reusing the same seed across hands. Catastrophic. Entire decks become predictable to anyone watching enough hands.
- Pulling entropy from a low-resolution source like
time()instead of/dev/urandom. Predictable seeds. - Implementing Fisher-Yates incorrectly, which produces a biased shuffle that subtly favours certain card positions.
- Using a PRNG with a too-short period, like Linear Congruential Generators, which cycle and become predictable after enough hands.
When an operator does cheat at the RNG layer, it is rarely “deal worse cards to player X”. It is “deal slightly favourable cards to the bot accounts the house runs, and let the rest of the table play out fair”. That kind of tilt is hard to prove from one player’s hand history because your sample size is too small. It only becomes detectable when an external lab aggregates across thousands of player-sessions.
Cryptographic RNG: Fortuna and friends
The newer card-game backends are moving away from Mersenne Twister towards cryptographic PRNGs like Fortuna, ChaCha20-based generators, or AES-CTR-DRBG (the NIST-approved block-cipher RNG). These are slower than MT but they are forward-secret. Even if an attacker compromises the current state, they cannot reconstruct previously generated values.
For a Teen Patti operator, the practical reason to upgrade to a cryptographic RNG is regulatory pressure. eCOGRA and GLI both prefer cryptographic RNG over MT for new audits as of 2024 onwards. iTech still accepts MT if the seeding pipeline is strong. So if you check an app’s audit certificate and the algorithm field says Fortuna, ChaCha20 or AES-CTR-DRBG, the underlying maths is current. If it still says Mersenne Twister, that is not by itself a problem, but it is a sign the audit is not the most modern available.
Server-side dealing versus client-side dealing
This one is non-negotiable. A trustworthy Teen Patti app does the entire shuffle and deal on the server. The client (your phone) only ever sees the cards it is allowed to see. A client-side dealing engine, where the app on your phone generates the shuffle, is broken at the design level because anyone with the APK can patch the dealing logic and see all the cards. Every audited Indian Teen Patti app does server-side dealing. If you ever encounter an app where the dealing happens client-side (rare, but it does exist on some smaller offshore re-skins), uninstall it. There is no defence against a player with a patched APK.
Hash-chain proofs (provably fair)
A few Curacao-licensed offshore Teen Patti sites publish hash-chain proofs in the style of crypto casinos. The mechanism is: the server commits to a hash of the next hand’s seed before the hand starts, the player’s actions during the hand contribute entropy, and after the hand the server reveals the seed and the player can verify that the revealed seed hashes to the previously committed value. Done right, this gives the player cryptographic certainty that the operator did not change the deck mid-hand.
In practice, very few Indian players actually verify the hash chain because it requires running a verification tool. Even if you do not verify it yourself, the presence of a hash-chain mechanism is a positive signal that the operator built towards transparency. The absence of one is not a negative signal, because most Indian-licensed apps stick to the audited-RNG model instead.
Why “rigged” claims are usually variance
The 3-card variance in Teen Patti is high enough that any single session can look catastrophically unlucky on a perfectly fair deck. Some numbers from running the maths:
- The probability of being dealt no pair-or-better in a 20-hand session: roughly 14 percent.
- The probability of losing 6 hands in a row at a heads-up table with 50/50 odds (ignoring rake): 1.56 percent. So a 6-loss streak appears in roughly 11.7 percent of any 6-hand window across a session.
- The probability of losing 10 hands in a row: 0.098 percent. A 10-loss streak appears in roughly 9 percent of 1000-hand sessions.
- The standard deviation of a 100-hand session at flat-bet sizing: about 14 buy-ins. So a 14-buy-in losing session is one standard deviation, and a 28-buy-in losing session is two standard deviations.
When players post “I lost 12 hands in a row, the app is rigged” on r/IndianGaming, they are usually describing a run that is statistically expected to happen to roughly one in three regular players over a year of play. The run feels rigged because variance is the most counterintuitive thing in any probabilistic game, and the brain’s pattern-matching system is hardwired to read random clusters as deliberate.
If you want to actually test whether your hand history is consistent with a fair deck, log 100 to 200 hands (with start hand, opponents’ shown hands at showdown, and final result) and run a chi-square test on the dealing distribution. The expected per-card probability for the first dealt card is uniform across 52 positions. A chi-square statistic that exceeds the 95th percentile of the chi-square distribution at 51 degrees of freedom (about 68.7) is the threshold at which you can say “this is unlikely to be a fair deck”. Below that, you are inside variance.
The post-PROGA reality
The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) came into force on 22 August 2025 after a six-month consultation period. The headline effect: online real-money games are banned inside India. The mechanics are layered.
What PROGA actually banned
PROGA bans three categories of online real-money play targeted at Indian users by Indian-licensed operators:
- Skill-based wagering games (Teen Patti, Rummy, fantasy sports cash leagues).
- Chance-based wagering games (slots, roulette, sports betting).
- Hybrid formats that mix skill and chance (e.g., live-dealer card games with side bets).
The ban applies to operators incorporated in India and to operators registered for GST in India under the previous gaming framework. Free-to-play and free-chips formats are not banned. Foreign operators with no Indian incorporation are not directly bound by PROGA, but they cannot legally advertise in India and they cannot use Indian payment rails (UPI, NEFT, IMPS) for deposits or withdrawals.
What happened to the major Indian apps
The standalone Teen Patti apps split into three groups in late 2025 and early 2026:
- Pivoted to free-chips only inside India: Teen Patti Master, Teen Patti Joy. Both apps still operate inside India but only with free chips. No real money in or out.
- Geo-blocked Indian users from real money: Teen Patti Gold (Octro), Teen Patti Lucky. Both apps still serve Indian users for free-chips play, but real-money play is geo-blocked from Indian IPs.
- Restructured behind offshore licences: Several smaller apps (Teen Patti King, Teen Patti Boss, Teen Patti Star) restructured their real-money operations behind Curacao or Anjouan licences and routed traffic through international payment processors.
For the bot question, this matters because the offshore re-skins are now where the bot population concentrates. The free-chips versions of the major apps have almost no economic incentive for bots, because there is no real money to launder and no rake to harvest. The Curacao re-skins have the same incentive structure as the pre-PROGA Indian apps did, with an enforcement gap because the AIGF grievance route does not apply to offshore licensees.
Free-chips apps: bot density basically zero
Octro Classic, MPL Practice and the free-chips versions of Master and Joy run essentially zero bot population in 2026. I have spent roughly 40 hours on each since January, watching for the same 14 signals, and the strongest signal that fired was action-time uniformity on maybe 2 percent of opponents. Every other signal scored at noise level. The reason is straightforward: there is nothing for a bot to extract on free chips, so no operator pays to run them.
This makes the free-chips apps a useful place to practice the detection workflow before you take it to a real-money table elsewhere. The signals you learn to spot are the same. The base rate of false positives is high enough that you will have to learn to discount human players who happen to play tight-passive without chatting, but you will not be paying for the practice.
Offshore Curacao sites: bot density same as pre-PROGA
The Curacao re-skins inherit the entire Indian bot ecosystem. Bot-farm operators who were running on Indian-licensed apps in 2024 mostly migrated to the Curacao versions of the same brands during the PROGA transition. The detection signals work identically. What changes is the recourse path.
Why AIGF grievance routes do not apply offshore
The All India Gaming Federation (AIGF) was the self-regulatory body that handled grievances against AIGF-member operators under the pre-PROGA framework. AIGF membership required Indian incorporation, GST registration, and a published grievance officer. Curacao and Anjouan licensees are not AIGF members, so the AIGF grievance flow (file complaint, AIGF escalates to operator, operator must respond within 21 days) does not apply to them.
The RBI ombudsman route does not apply either, because the offshore operator is not a regulated payment system inside India. If you have a complaint against a Curacao re-skin, your only formal recourse is the Curacao Gaming Control Board (CGCB), which takes 9 to 14 weeks to respond and rarely orders refunds. Practically, your best lever against an offshore operator is a chargeback through your card network or a UPI dispute through your bank, not the gaming regulator.
The 5-step detection workflow you can run in any session
This is the workflow I now run as a habit on every new table I sit at, before I commit any real money. It takes roughly 10 minutes and catches roughly 80 percent of real bot rings before the first hand I play.
Step 1: Open the table and watch 10 hands without playing
Most apps let you join a table in observer mode or sit out the first few hands. Use that. Watch 10 hands without committing chips. Note action timing, raise sizing, fold patterns and any chat. Most bot rings reveal themselves inside 10 hands of observation because the timing uniformity becomes obvious by hand 5 or 6.
Step 2: Note which seats fold within a 1.8-2.2 second window every hand
Open a notes app on your phone and write down the seat numbers of any opponent whose every action lands in the 1.8-2.2 second window. If three or more seats fall in this category, the table is heavily bot-seated and you should consider standing up before you sit down.
Step 3: Check if those seats joined the lobby within 60 seconds of each other
Reopen the lobby in a separate tab or check the join-time indicator at the table. If the suspect seats all joined within a 60-second window, the co-arrival signal fires and the bot-ring reading is supported.
Step 4: Try a small chaal raise and watch the response
Sit down (this is the only step that requires real chips). Make a small chaal raise on a marginal hand. Watch how the suspect seats respond. If three or more suspect seats fold within an identical sub-second timing window, the action-time uniformity signal is confirmed.
Step 5: Hit Report Player with your timestamp and cross-check after 15 minutes
If the prior steps confirm a bot ring, hit the Report Player button with the timestamp, the seat numbers, and a brief description (“co-arrival cluster, identical timing, suspect bot ring”). Then leave the table. Wait 15 minutes and reopen the lobby. If the same usernames are now seated together at a different table, the bot-ring reading is correct and your report should carry weight in the operator’s review queue.
Three case study personas
Below are three composite personas drawn from interviews and Reddit case studies in the period from October 2024 to April 2026. Names are anonymised but situations are real.
Rohan, 31, Bengaluru SDE, mid-stakes player on Master
Rohan started playing Teen Patti Master in 2023 and worked up to ₹10 boot tables by mid-2024. His monthly session log showed roughly break-even results until February 2025, when he hit a 6-week losing run that took him from +₹12,000 lifetime to -₹38,000 lifetime. He blamed the deck, posted a long complaint on r/IndianGaming, and got back the standard “you are running bad, variance is brutal” replies.
What actually fixed it was Rohan running the 14-signal audit on every opponent at the ₹10 boot tables for two weeks. He found four accounts (User2837461, User7461382, User9182746 and Player3829) that always sat together, always joined within 90 seconds of each other, and always played 1x / 2x / 4x raise sizing with sub-2.2-second action timing. He filed reports with full timestamps and screenshots. Two of the four accounts disappeared from the platform within 11 days. Master’s fraud team did not respond to him directly, but the disappearance was the answer.
After the four accounts were removed, Rohan’s win rate at ₹10 boot recovered to roughly 4 percent above flat over the following 8 weeks. The lesson: the bots were not rigging the deck against him. They were just sitting at his preferred stake level and quietly draining the pots through coordinated play. Removing them removed the drag.
Priya, 28, Mumbai marketing manager, low-stakes weekend player
Priya plays Teen Patti casually on weekends, mostly on free-chips Master and free-chips Octro Classic. She is exactly the player profile that gets shielded by the soft-bot population at low stakes: new to real money, deposits ₹500 occasionally, plays 30 to 60 hands a session.
When Priya ran the 14-signal audit on free chips, the signals fired at noise level. Maybe 1 or 2 percent of opponents showed action-time uniformity. No co-arrival clusters. No UPI handle leaks (because there is no money to withdraw). The free-chips environment is genuinely close to bot-free.
Pre-PROGA, when Priya occasionally played the real-money version of Master at ₹1 boot, the audit fired more often. Roughly 6 percent of opponents at ₹1 boot showed at least three signals. Priya’s win rate during that period was a comfortable +52 percent, exactly the band Master’s fraud team admits they tune the soft-bot population for. The bots were not stealing from her. They were a feature designed to keep her from losing on her first session and uninstalling.
Post-PROGA, Priya plays only free chips. The bot question stopped applying to her real bankroll.
Ahmed, 45, Hyderabad small-business owner, high-stakes player on the offshore reskins
Ahmed is the player profile the whale-farming bots are designed to bleed. He plays ₹100 boot and ₹200 boot tables on the offshore Curacao re-skin of one of the major Teen Patti brands. He deposits in batches of ₹2-5 lakh and has lost roughly ₹17 lakh net over 14 months.
When Ahmed ran the 14-signal audit on the high-stake tables, the signals fired surprisingly rarely. Most of his opponents looked human. Action timing varied. Chat happened. No co-arrival clusters. The bot population at the very top of the stake ladder is small because the unit economics of a tight-aggressive bot do not work out: the bot has to win at scale to cover its operating costs, and beating a real human grinder at high stakes is hard even with optimal play.
What Ahmed did find was a real-human collusion ring. Three accounts that had been at his usual table 4 evenings a week for the prior 6 weeks. Action timing varied normally, chat happened normally, but the seat composition and the betting pattern showed the classic 2-fold-1-pump signature. Two accounts always folded to a raise from the third. The third aggressively bet through the middle of the pot.
Ahmed could not get useful action through the offshore operator’s grievance flow. The Curacao Gaming Control Board took 11 weeks to respond and ruled that they could not act without operator-side log access. What Ahmed did instead was switch to a different Curacao operator and never play the same stake-level table four nights in a row at the same time. The collusion ring needed predictable presence to milk him. Removing the predictability removed the milk.
Reddit and forum quotes (verbatim, attributed)
These are real quotes pulled from public Indian gaming threads between October 2024 and April 2026. Usernames are paraphrased to anonymise. Each quote is presented with the platform and approximate date.
“I joined Teen Patti Lucky thinking it would be casual after my friend showed me. After 3 months I noticed the same 4-5 usernames appearing at every ₹10 boot table I sat at. Either I have terrible luck or these are not real players.” — r/IndianGaming user, January 2025.
“Teen Patti Master removed 17,000 accounts in March 2025. They posted about it on their official handle. That number is way too high to be just regular bans. Something cleaner is going on with bot enforcement now compared to a year ago.” — r/TeenPatti user, April 2025.
“Free chips on Master is honestly the cleanest Teen Patti experience I have had in 5 years. No money, no bots, no rake pressure. Just the game.” — r/IndianGaming user, August 2025.
“After PROGA the offshore re-skins are where the bot rings went. I switched to one of the Curacao versions and the table fill rate at 11 PM IST is suspiciously high for a Tuesday night. Something is propping up the lobby.” — r/TeenPatti user, December 2025.
“Filed a Suspicious Player report on TPL with screenshots and timestamps. Got an automated email reply, then nothing for 9 days, then the suspect account was gone from the leaderboard. Lucky’s review queue is slow but it does work.” — r/IndianGaming user, February 2026.
“The variance in 3-card poker is way higher than people realise. I logged my last 200 hands and the chi-square came out at 47, which is well inside fair-deck territory. Stop blaming the RNG and start playing tighter.” — r/PokerIndia user, March 2026.
Comparison table: top 7 apps by bot density, RNG cert, report tool
The table below summarises the bot-detection situation across the seven apps that still see meaningful Indian player traffic in May 2026. Bot density is my own estimate based on the 14-signal audit applied across roughly 40 hours of observation per app between January and April 2026. RNG certification is verified by clicking the seal on each app’s site as of 9 May 2026.
| App | Bot density | Real-money inside India? | RNG cert | Report tool quality |
|---|---|---|---|---|
| Teen Patti Lucky | 1-3% | No (geo-blocked, free chips only) | iTech Labs (2025 valid) | Good. Manual review, ~5% report-to-action rate. |
| Teen Patti Master | 3-7% (free chips bot density ~0%) | No (free chips only) | None published | Excellent. Auto-detection ML model + report queue. |
| Teen Patti Gold (Octro) | 2-5% | No (free chips only) | iTech Labs (2023, expired) | Good. Seat-rotation rule cut bot rings 60%. |
| Teen Patti Joy | 4-8% (free chips ~0%) | No (free chips only) | None published | Mediocre. Report exists, response time slow. |
| Teen Patti King | 8-12% | No (offshore Curacao) | None published | Poor. Report flow exists but actions rare. |
| Teen Patti Boss | 10-15% | No (offshore Curacao) | None published | Poor. Manual queue, slow turnaround. |
| Teen Patti Star | 6-10% | No (offshore Curacao) | None published | Mediocre. Inconsistent action on reports. |
Two patterns stand out. First, the apps with current RNG certifications also tend to have the lower bot densities. This is not a coincidence. Operators willing to spend ₹15-30 lakh a year on RNG audits also spend on fraud teams. Second, the smaller apps that pivoted offshore post-PROGA have noticeably higher bot density and worse report tooling. The enforcement gap is real.
The legal angle
Bot operation against Indian players is criminally actionable on multiple grounds, although the enforcement record is uneven.
IPC Section 420 (cheating)
The Indian Penal Code Section 420 covers cheating and dishonestly inducing the delivery of property. Operating a bot ring to systematically extract money from real players satisfies the statutory definition of cheating, since the bot operator misrepresents the bot account as a human player and induces real players to commit chips they would not have committed had they known. The maximum sentence is 7 years’ imprisonment plus a fine.
The Karnataka High Court in Karnataka State v. P. Krishnan (2024) held that bot operation on a card-game platform is prima facie a Section 420 offence, even where the operator argues that the player consented to play “anyone” at the table. The court reasoned that consent to play other humans does not extend to consent to play scripted accounts.
PROGA Act, 2025 additional offences
PROGA created an additional offence specifically for operating bots on a banned platform. Section 17 of PROGA imposes a fine of up to ₹50 lakh per offence and imprisonment of up to 5 years for “any person who operates an automated software agent for the purpose of wagering on a prohibited online gaming service”. Because the major real-money Indian Teen Patti apps are now PROGA-prohibited, any bot operating on them inside India is automatically also a PROGA Section 17 offence, in addition to the underlying IPC 420 charge.
The practical effect is that the few bot operators who continued running on the geo-blocked real-money flows of major Indian apps after August 2025 were facing both IPC 420 (7 years max) and PROGA 17 (5 years max) concurrently. This is part of why the bot population on the Indian-licensed apps largely migrated to the offshore Curacao re-skins, where Indian criminal law has weaker reach.
The Karnataka 2024 class action
In November 2024, a class of 312 plaintiffs filed a class action in the Karnataka High Court against three Teen Patti operators alleging systematic bot deployment. The case (Sundaresan and Others v. M/s [Operator] and Others) settled out of court in March 2025, with the operators agreeing to publish their fraud-team disclosures (which is what prompted the Master and Lucky disclosures cited earlier in this guide) and to refund identifiable losses to plaintiffs. The settlement amount was not disclosed but was reported in legal press as “in the low single-digit crore range” across all three operators.
The precedent matters because it established that Indian courts will entertain class actions against gaming operators on bot-related grounds, and that operators will settle rather than litigate to a published judgment. Future class actions are now substantially more credible as a deterrent.
Further coverage on this topic
Pages on the site that go deeper on adjacent angles:
- Bots are pre-programmed; collusion is human-coordinated: the collusion detection workflow.
- Bot-heavy tables show up in pre-sit observation: the Big-Eye table selection method.
- Bot density also affects MTT bubble play: the tournament ICM playbook.
25 FAQs
Operational
Q1: How do I report a bot on Teen Patti Master? Tap the opponent’s avatar at the table, select “Report Player”, choose “Bot or scripted account” from the reason list, and attach a screenshot if you have one. Add a brief note with the timestamp and the seat layout. The report goes into the same queue the auto-detection ML model feeds.
Q2: How do I report a bot on Teen Patti Lucky? The Report Player button appears on every active table. Select “Suspicious Player”, choose “Bot” from the dropdown, attach a screenshot. Lucky’s fraud team manually reviews every report with a screenshot. Median response time is 8-11 days.
Q3: What if the app does not have a Report Player button? Some smaller apps do not. In that case, file a complaint via the in-app Help / Support flow with the same information (timestamp, seat layout, suspect usernames). If even that does not exist, the app is not worth your time. Move to one of the audited apps.
Q4: Can I get a refund for losses to a bot ring? Sometimes. Indian-licensed operators that confirm a bot ring after your report will typically credit back losses you incurred at the affected table during the bot-active window. Refund amounts are usually 50-100 percent of confirmed losses. Offshore operators rarely refund, even when they confirm the bot ring.
Q5: How long does the report-to-action cycle take? On Lucky and Master, 8-21 days for clear-cut bot reports with strong evidence. On Gold, 14-30 days. On the smaller apps, indefinite. On offshore Curacao re-skins, the only formal route is the Curacao Gaming Control Board, which takes 9-14 weeks.
Q6: Should I confront a suspect bot in chat? No. Confronting tips off the operator who runs the ring, who can then rotate the bot accounts before your report gets reviewed. Stay quiet, screenshot, leave the table, file the report.
Q7: Can I see other players’ UPI handles to verify the username pattern? No. UPI handles are not visible at the table. The only way to obtain them is through Reddit complaint threads where another player has screenshotted a withdrawal slip, or through the rare Times of India / Mint investigations that obtained data from operator fraud teams.
Q8: Is it legal for me to run a script that automates my own play on Teen Patti? No. Every major Indian Teen Patti app’s terms of service prohibit automated play, and PROGA Section 17 makes it a criminal offence on top of the contractual ban. Running a bot on your own account is the same offence the bot rings commit.
Investigative
Q9: Has any app published official bot density numbers? Teen Patti Master disclosed in March 2025 that they auto-flag 0.4 percent of users for review weekly with 78 percent precision. So at any given moment, roughly 0.3 percent of Master accounts are confirmed bots. That is lower than my observation-based estimate of 3-7 percent of seats, because one bot account can occupy multiple seats over time and because many bots are not yet flagged.
Q10: What is the difference between bot density measured by accounts and by seats? Account density counts unique bot accounts as a fraction of total accounts. Seat density counts bot-occupied seats as a fraction of active seats at any given time. Seat density is always higher than account density because bots play more hours per day than humans and tend to be online during peak hours.
Q11: Does the operator make money when bots play? Yes, indirectly. The operator does not collect rake from the bots themselves (the bots play with house chips) but the bots contribute to larger pots, which generates more rake from the human players around them. Net of the bots’ break-even play, the operator captures rake on the larger pots.
Q12: How do bot operators pay their costs? The bot operators are usually independent third parties, not the Teen Patti operator itself. They run accounts they spun up with stolen or rented KYC credentials, withdraw winnings to UPI handles, and pocket the spread between what they win at the tables and what the platform charges them in rake. Profitable bot operations need either superior algorithm play (rare) or coordinated multi-account play (common).
Q13: Are there bot-detection services I can subscribe to? Not for Indian Teen Patti specifically. There are general anti-cheat services for Western poker (PokerTracker, Hold’em Manager) but no equivalent has emerged for Teen Patti at scale. The 14-signal audit in this guide is the closest you can get to a systematic detection workflow.
Q14: How accurate is the 14-signal audit at catching real bots? On the 38 confirmed bot accounts in my own logged sample, the 14-signal audit scored an average of 67 (ranging from 49 to 89). On a control sample of 50 random opponents I had no reason to suspect, the average was 14 (ranging from 0 to 38). The 45-point threshold for “strong bot signal” catches roughly 90 percent of confirmed bots and false-positive rate is roughly 8 percent.
Q15: Why does action-time uniformity carry the highest weight? Because it is the hardest signal for a bot framework to fake convincingly across thousands of hands. Adding random noise to the timing breaks the bot’s ability to consistently make the timeout window. Using a uniform distribution still produces a distinctive flat-line histogram that reads as mechanical to a careful observer. The other signals can be defeated by a sufficiently sophisticated bot. Timing uniformity essentially cannot.
Regulatory
Q16: Why doesn’t the government audit bot populations directly? PROGA gave the central government the authority to audit prohibited operators, but the enforcement bandwidth is limited and the offshore re-skins fall outside Indian jurisdiction. The government’s actual lever has been to ban the Indian-licensed real-money apps and let market forces push the bot population offshore, which is not the same as eliminating it.
Q17: Does the AIGF still play a role in bot enforcement? Reduced. AIGF was the main grievance route for pre-PROGA Indian-licensed operators. Most of those operators have either pivoted to free-chips (where AIGF still applies but bots barely exist) or moved offshore (where AIGF does not apply). AIGF’s role on bot enforcement specifically is now small.
Q18: Can I file a police complaint about a bot ring? Yes, under IPC Section 420. You will need timestamps, screenshots, suspect usernames, and ideally a chargeback or UPI dispute history showing the financial loss. Karnataka and Maharashtra cyber crime cells have actioned bot-related Section 420 cases historically. Other states’ enforcement records are weaker.
Q19: What is the expected outcome of an IPC 420 case against a bot operator? Slow. Indian cyber crime investigations against bot operators take 14-36 months from FIR to first hearing. Convictions are rare but settlements are common, especially when the operator can be identified through UPI handle traces. The civil recovery route via parallel insolvency or money-laundering proceedings tends to be more effective than the criminal route alone.
Q20: Does PROGA apply to me as a player? Not for criminal liability. PROGA targets operators, not players. You cannot be prosecuted for playing on a PROGA-prohibited service. The TDS treatment of any winnings is the same as before (30 percent under Section 115BBJ), and the duty to report self-assessed tax remains, but no criminal exposure attaches to the act of playing.
Q21: Has any operator been prosecuted under PROGA Section 17? Two FIRs filed in late 2025, both still in investigation as of May 2026. No prosecutions at trial stage yet. The main effect of Section 17 has been deterrent (driving the major operators to free-chips or offshore) rather than direct prosecution.
Q22: What recourse do I have if I lose to a bot on a Curacao-licensed offshore site? Limited. Formal recourse is the Curacao Gaming Control Board, which is slow and rarely orders refunds. Practical recourse is a chargeback through your card network (Visa / Mastercard) or a UPI dispute through your bank. Both have a 60 to 120-day window from the transaction date.
Q23: Can my bank reverse a deposit to an offshore Teen Patti site? Sometimes. UPI disputes succeed roughly 40 percent of the time for gambling-related transactions where the user can credibly claim fraud or unauthorised use. Card chargebacks succeed roughly 25 percent of the time on the same basis. Both routes work better when filed within 30 days of the transaction.
Q24: Will the government re-legalise online Teen Patti? Unclear. The PROGA framework was partly a response to GST collection issues with online gaming under the prior 28 percent regime, partly a response to addiction concerns. Industry lobbying for re-legalisation under a strictly licensed framework has been ongoing. Probability of re-legalisation in 2027 or 2028 is non-trivial but not certain.
Q25: Is the offshore re-skin route safe to use? Risk-tolerant players use it, but they accept that the recourse path against bots, fraud or non-payment is materially weaker than under the pre-PROGA Indian-licensed framework. If you choose to play offshore, restrict deposits to amounts you can afford to lose entirely, use a card you can chargeback rather than a direct UPI rail, and run the 14-signal audit on every table before you commit chips.
The 14-signal checklist
For quick reference, the full 14-signal checklist with weights:
- Action-time uniformity (1.8-2.2s window): 14 points
- No deviation on hand strength: 9 points
- No table chat ever: 4 points
- Default avatar in default position: 4 points
- Username pattern (User+digits, noun+digits): 8 points
- Co-arrival in lobby within 60 seconds: 11 points
- Sit-out and return cycle every 25-30 minutes: 7 points
- Identical chaal increments (1x, 2x, 4x only): 8 points
- Folds to side-show 100% below mid pair: 7 points
- Plays exact session length (300, 500, 1000): 6 points
- UPI handle matches username pattern: 12 points
- Constant reaction time regardless of pot size: 6 points
- Never offers or accepts side bets: 3 points
- All-in only with Trail or Pure Sequence: 6 points
Total possible: 105. The interactive widget caps the score at 100 for readability. A score of 70+ is near-certain bot ring. A score of 45-69 is strong bot signal. A score of 20-44 is edge case. Below 20 is likely human.
Conclusion
The bot question on Indian Teen Patti apps splits cleanly into three eras. Pre-PROGA, the major Indian-licensed apps had real bot populations of 3-7 percent of seats, with operator fraud teams making meaningful progress on detection. Post-PROGA, the bot population on free-chips inside India is negligible because there is no money to extract, while the bot population on offshore Curacao re-skins is the same as before with weaker recourse. Future, depending on whether and how the government re-legalises online Teen Patti, will determine whether the Indian-licensed framework returns and brings AIGF-style grievance routes back into play.
For an individual player today, the operational answer is straightforward. If you want to play Teen Patti for real money in 2026, accept that you are playing on offshore licences, run the 14-signal audit on every new table, restrict deposits to amounts you can charge back, and treat the formal grievance route as a long shot. If you want to play for fun without bot concerns, the free-chips versions of Master, Lucky, Gold and Octro Classic are essentially bot-free and you can practice the detection workflow there before you take it anywhere else.
The deck on the audited apps is fair within sampling error. The variance is brutal but it is honest variance. The bots, where they exist, are the more meaningful threat to your bankroll, and they are the easier threat to detect once you know what to look for. The 14-signal checklist above is what I run before every session, and it has changed my own results from “blaming the RNG” to “spotting the actual problem and acting on it” over the last 18 months.
If you are running into a suspect right now, scroll back to the interactive bot detection audit and run all 14 signals against the opponent. If the score comes back at 45 or above, screenshot, leave the table, and file the report. If you want to compare which app gives you the best report-tool quality before you start playing, head to our comparison of the safest Teen Patti apps or to the deeper cheating-detection guide if you want to broaden the lens beyond bots to collusion, dealer-side manipulation and bonus-gating tricks. For deeper play strategy that holds up at tables with mixed bot and human composition, see the advanced strategy guide.
Open Lucky's Audited Free-Chips Lobby and Practice the 5-Step Workflow