Tower Rush Rules, Limits and Payouts
How a Tower Rush round is defined
The rules of Tower Rush are short, and the entire agreement between a player and an operator sits inside them. A round opens when a stake in rupees is accepted and the Build button is pressed, and it closes either because you settled it by hand or because the tower failed. Nothing else closes it: there is no timer, no automatic settlement and no auto cash-out to fall back on if attention wanders.
| Rule | What the rule says | What it means in practice |
|---|---|---|
| Stake acceptance | A round opens only once the stake has been deducted and confirmed on the operator's server | A round that never registered was never placed, and the money stays on the balance |
| Settlement | A win exists only after Cash Out has been pressed and accepted | An unsettled round is worth nothing, however high the multiplier climbed |
| Failure | The round closes as a loss once the tower can no longer take a segment | The whole stake is lost and there is no partial return |
| Result authority | The server record of the round is the binding version of events | A dispute is settled against the log and the round hash, not against what the screen showed |
The order of events in a settled round
- The stake is deducted from the rupee balance and the round is registered on the operator's server.
- The crane is released and the first segment becomes droppable.
- Each placement is recorded as an outcome of its own, in sequence, against the seeds of that round.
- Cash Out fixes the multiplier at the value standing when the request reaches the server.
- The settled amount is credited to the cash balance and the round is closed to further action.
- A round cannot be cancelled, reversed or replayed once the stake has been accepted.
- Only one round is live at a time on an account.
- The multiplier applies to the stake of that round alone and never carries into the next one.
- Accounts are personal: shared logins and automated play breach the operator's terms and put settlements at risk.
Stake limits, the 100x ceiling and the cashier
Two sets of limits govern a session, and they come from different systems. The game sets limits per round: the smallest and largest stake it accepts, and the multiplier at which a win stops growing. The cashier sets limits per payment: the smallest deposit it will take and the caps on how much can leave the account in one transaction and across a calendar month. The two are unrelated numbers, and a plan built on the first while ignoring the second runs into the second eventually.
| Limit | Figure | Set by | What it controls |
|---|---|---|---|
| Minimum stake | PKR 25 per round | The game | The smallest round accepted, in demo and real money alike |
| Maximum stake | PKR 25,000 per round | The game | The largest amount that can be committed to one tower |
| Maximum payout | 100x the stake | The game | The ceiling on a round: PKR 25,000 staked settles at no more than PKR 2,500,000 |
| Withdrawal caps | Per transaction and per calendar month | The casino's cashier | How fast a balance can be moved out, whatever it was won at |
The 100x figure is a ceiling rather than a target. Once a round reaches it the multiplier stops counting, so PKR 1,000 staked cannot return more than PKR 100,000 however the tower behaves afterwards. It applies identically in demo play, which is part of what makes the practice mode a fair rehearsal.
Where the cashier limits start to bite
The interaction between the two sets of limits is easy to miss. A balance built at the top of the stake range still leaves the account at the cashier's pace: a payout larger than the per-transaction cap is split across several withdrawals, and the monthly cap for a standard account sits on top of that. Verification is a further gate again, usually triggered by the first withdrawal rather than by the deposit, and the name on the wallet or bank account has to match the name on the gaming account. The payment pages on this site set out the timings and the documents for each method; for the purposes of the rules, the point is that the game's limits say nothing at all about how quickly money comes out.
- Stake limits vary slightly between operators, and the figures above are the common band for rupee accounts.
- The payout ceiling belongs to the game and is the same in demo and real-money play.
- Withdrawal caps, fees and verification belong to the casino rather than to the game.
- Bonus terms can impose a lower stake ceiling than the game does, and the stricter of the two applies.
Void rounds, disconnections and provably fair checks
Most rounds resolve without incident. The rules worth knowing are the ones covering the exceptions: a round the system decides never properly happened, a round cut short by the network, and the mechanism that lets you confirm afterwards that an outcome was not manufactured.
When a round is void
A void round is one the operator annuls and settles as though it had never been played, with the stake returned to the balance. Terms usually reserve this for rounds affected by a technical fault in the game or on the server, for duplicated or incomplete transactions, and for play that breaches the account rules, with automated scripts, shared logins and exploiting a known defect as the standing examples. A void is not a refund you can ask for because a round went badly: the decision rests with the operator and the provider and is applied to the round record rather than negotiated.
If the connection drops mid-round
An interrupted round does not simply vanish, because its state is held on the server rather than in the browser. Reconnect promptly and the round is normally still live, waiting for the next decision. If the session cannot be resumed, the round is closed under the operator's rules on interrupted play and the outcome is taken from the server record. The practical advice is narrow: reconnect rather than reload, never open the game in a second tab, and if a result looks wrong afterwards, quote the round identifier to support instead of describing what the screen appeared to show.
Provably fair verification
Every round is built from a server seed, a client seed and a salt. The hashed server seed is published before the round starts, which commits the operator to an outcome it cannot then change, and the seed itself is revealed once the round is over, so hashing it yourself shows whether it matches what was published. The random number generator behind it is audited separately by independent international testing laboratories. Between the two, fairness is something you can check rather than something you have to take on trust.
- Void rounds: the stake is returned and the outcome annulled, decided by the operator against the round record.
- Interrupted rounds: the state lives server-side, so reconnect rather than reload and quote the round identifier in any query.
- Provably fair: the server seed, client seed and salt let each round be verified after the event.