Tower
Rush at 4RABET with PKR Payments, Bonus Rules and Mobile Access

4RABET supplies the account and cashier; Galaxsys supplies the original Tower Rush game. A search for “tower rush 4rabet” should be followed by checking the game name and provider in the catalogue. Tower Rush 2 is a separate product, and a similar tower image does not make two games interchangeable.

I opened both FUN demo and own-money play in the Pakistan account, keeping the welcome switched off for the cash session. A separate launch displayed “Not available in your region” after loading. These are different access outcomes: a successful account session does not mean every launch from every location will be accepted.

If that regional message appears, stop at the restriction and ask the operator about your account's eligibility. Changing an interface language or selecting PKR does not itself establish permission to play. The licensing guide explains the separate roles of the provider, operator and publisher.

The tested signup route used a phone number with Pakistan's +92 code, Pakistan as the account country and PKR as the currency. I confirmed the 18+ age requirement and terms, then verified the phone by OTP. Email confirmation was not required at signup; I added a separate email address in settings for the account's later actions.

To follow this account route:

1. Select Pakistan and PKR in the registration form and enter your own phone number.
2. Read and accept the required terms separately from optional marketing choices.
3. Enter the current OTP. If you request a replacement, use the new code rather than the previous one.
4. Sign in through the phone and password or OTP form offered for your account.
5. Open the catalogue, search for Tower Rush, and select the original Galaxsys title.

The recovery code lasts four minutes. In my recovery check, requesting a new code invalidated the old one; changing the password and ending the other sessions preserved the balance and history. Saved-password confirmation through the phone's operating system made returning easier, but it did not replace operator identity verification.

No documents were requested during my registration or first deposit. The first withdrawal required ID, while a later change of payment details required confirmation of the new wallet. Read the registration, login and verification guides for the corresponding account tasks.

FUN is a demonstration balance and cannot be transferred into the operator's cash wallet. The original game uses one initial stake followed by Build, server acceptance and the floor result. After a successful floor you can select Cashout or continue building; Cashout settles the round into the game balance and does not initiate a bank withdrawal.

The Pakistan money configuration has a 97% RTP, stakes from PKR 27.00 to PKR 36,000.00 in PKR 0.50 steps, and a gross payout cap of PKR 3,150,000.00 per round. The FUN configuration instead allows stakes of 1–100 FUN, a 0.50 FUN step and a 10,000 FUN cap. Neither cap is a universal maximum multiplier.

Frozen Floor protects an amount already accumulated; a larger eventual Cashout includes that protection rather than adding it again. Temple multiplies the current amount, and Triple Build adds floors without three new stake deductions. Autoplay, Auto Cashout and Buy Bonus are absent from this original profile. You can inspect the basic controls in the official demo.

Raast P2P has separate deposit and withdrawal conditions in this Pakistan account. Its PKR 1,175.00 deposit minimum is method-specific: it is neither the game's minimum stake nor a minimum that can be copied across every cashier entry. The executed transaction also provides timing evidence for one transfer, rather than a guaranteed processing deadline.

I created a new Raast P2P deposit request for PKR 4,700.00 and confirmed the transfer in the payment interface. The game account, payer and payment account were all in Pakistan, and the holder's name matched. The full amount arrived in 148 seconds, with no operator fee, external fee or currency conversion.

Open Cashier, select Deposit and Raast P2P, then create the request for the amount you intend to send. Confirm payment through the payment interface and return to that request to check its status. When I encountered a delay, I inspected the existing request rather than initiating a second transfer. The deposit guide covers this distinction in more detail.

The own-money session used eight stakes of PKR 587.50, for PKR 4,700.00 of turnover. I started with a zero balance, deposited that amount and played without an active welcome. The table separates gross payouts from the account balance after each settlement; a gross payout still includes the stake component where the outcome returns it.

Total game gross was PKR 6,051.27, so the gaming net was PKR 1,351.27 after subtracting the PKR 4,700.00 stakes. This particular sequence included three zero-payout rounds. Its positive total is a session result, not an expected return for your next eight bets or a promise that depositing the same amount reproduces it.

I requested PKR 3,525.00 to my own Raast P2P account after completing the ordinary 1× turnover requirement. There were no pending rounds or active welcome funds, and I confirmed the request by email. Review, including KYC, took 2,409 seconds; the transfer then took 491 seconds. The total was 2,900 seconds, or 48 minutes 20 seconds.

The 0.65% operator charge was deducted inside the request: PKR 3,525.00 × 0.0065 rounds to PKR 22.91. I received PKR 3,502.09, with no additional external charge. The game balance fell by the requested PKR 3,525.00, leaving PKR 2,526.27; subtracting the fee from that balance a second time would be wrong.

Before sending a withdrawal, select your own payment details, check the amount available and finish the required confirmation. I also cancelled a separate reserved request before it was sent: the reserve was released with no net change, and the main transfer still happened once. A cancellation is not an additional payout. See withdrawal stages for the difference between review, release and receipt.

The Pakistan cashier profile contains 145 deposit entries and 101 withdrawal entries. These include banks, networks, wallets, interfaces and other payment tools, so the count should not be read as 145 separate payment companies. I executed the Raast P2P route; the wider catalogue below describes availability by operation.

Deposit availability does not establish withdrawal availability. USDT (ERC20) and USDT (Polygon), for example, appear only in the deposit list, whereas USDT (Solana) and USDT (BEP20) appear in both directions. Preserve the complete network label when choosing a crypto route; the Raast PKR transfer has no blockchain-confirmation requirement.

Account currencies are listed separately: PKR, KRW, TRY, NGN, CAD, USD, EUR, NOK, PLN, CZK, USDT, BTC and ETH. PKR is displayed first. A wallet currency is not another cashier method, and limits from a PKR request cannot be assigned to a token balance. Use the payment-method guide to compare the relevant operation before funding an account.

Tower Rush has a 0% contribution in the selected 4RABET welcome offer. The 125% match therefore does not provide a way to clear its wagering requirement through this game. Own-money play and the separate welcome scenario must be read independently, even though both examples used a PKR 4,700.00 deposit.

I qualified for PKR 5,875.00 in the separate welcome scenario, but the initial credit was PKR 0.00. After I contacted support, the correction added PKR 5,875.00 once, within 303 seconds of qualification. That corrected amount was the final bonus, not a second bonus on top of an earlier payment, and none of it entered the own-money session above.

The match calculation is min(PKR 4,700.00 × 125%, PKR 122,500.00) = PKR 5,875.00. The panel then showed PKR 10,575.00 across own funds and bonus funds before reward use. Reading that combined figure as an immediately withdrawable balance would overlook the wagering and withdrawal conditions attached to the bonus.

The wagering requirement is 40× the bonus, giving PKR 235,000.00 of eligible turnover. In the welcome episode, PKR 4,700.00 staked on Tower Rush contributed PKR 0.00, so the entire requirement remained. Eligible slots come from the promotion's separate list; the original tower game is excluded from that contribution list.

Active bonus funds cannot be withdrawn before the offer's conditions are met. Cancelling the offer removes the unplayed bonus and associated rights, while own funds and already accepted rounds are accounted for separately. If your purpose is to play this game, compare the bonus eligibility rules before activating an offer whose headline percentage does not describe its usefulness to you.

The Android product is a 4RABET APK container for the operator's service; Tower Rush itself remains a Galaxsys HTML5 game. On iPhone, the tested route is an operator WebView using WebKit. There is no separate Tower Rush IPA to download in that route, and an App Store channel should not be confused with the web access described here.

I installed Android version 3.38.40 through the operator interface's Android button; installation took 28 seconds to the appearance of the icon. The compatibility profile specifies Android 11/API 30 or newer and arm64-v8a. Touchscreen and network access are required; camera access is optional because the KYC flow also accepts a file.

Storage and transferred data measure different things. The initial iPhone HTML5 transfer was 14.81 MB. The Android download is about 30.3745 MiB in binary units, corresponding to 31.85 decimal MB. Battery observations used 55% brightness over the stated session; the Android casing felt moderately warm.

I declined the initial Android notification request and could still play. After enabling notifications, I read a request notification; the iPhone WebView route instead used account history and did not deliver push. Camera refusal left file selection available for KYC on both routes. I did not grant Android location permission, selecting the account country in the form instead.

Saved-password access used operating-system confirmation on Android and Face ID on iPhone. Neither changed who held the server balance. I restored that balance after reinstalling the Android container and signing in again; clearing iPhone website data similarly required a fresh login without removing the operator-held funds.

Launch time was measured from selecting the Tower Rush card to an active Build button, excluding APK installation and opening the outer app. I ran seven attempts for each cold and warm series on each device. Cold starts used cleared data; warm starts retained cache. All 28 normal launches succeeded.

The main connection was home Wi-Fi in Pakistan, measured at 91.7 Mbps downstream and 31.4 Mbps upstream. Those connection speeds are not game-launch speeds. Deliberate network interruptions were assessed separately and do not enlarge the normal-launch denominator or become extra failures in that table.

In the interruption checks, losing connectivity before acceptance produced no stake deduction. After acceptance, I recovered the original round and its single payout. Returning from the background after 71 seconds on Android or 78 seconds on iPhone did not create a second bet. An offline shell could open, but it could not place a new stake.

Both portrait and landscape retained the stake, Build, Cashout and rules controls; on Android the keyboard needed closing to expose the controls. Wide iPhone history used local scrolling. Urdu RTL and English LTR were supported, with PKR figures and Latin identifiers kept readable.

The website and both mobile routes support ur-PK, en-PK, fr, es, tr, ar and de. Switching between Urdu and English preserved the account, currency and history; game language is a separate setting. The mobile-access guide separates these operator routes from standalone game downloads.

Live Chat is available 24/7 in this operator profile. I asked in Urdu about the difference between game Cashout and an external withdrawal: the automated response took five seconds, the first substantive answer 324 seconds, and resolution 1,332 seconds from contact. A separate English enquiry gave the same sequence of actions.

That explanation changed no funds. The PKR 5,875.00 welcome correction was a separate issue with its own 303-second interval, so it should not be presented as the response time for every chat. No external complaint was submitted. For a credit problem, keep the original request, amount and correction together rather than treating a reopened conversation as another entitlement.

I reduced a daily deposit limit from PKR 14,100.00 to PKR 9,400.00 with immediate effect; raising it had a 48-hour delay. A 23-minute session limit allowed the accepted round to finish. The 180-day self-exclusion check blocked the next betting login while keeping withdrawal of the remaining balance separate from permission to gamble.

4RABET scores 6.59/10 across the six operator categories below. The mobile measurements and completed PKR route are useful strengths, while the fee, initial bonus-credit correction and zero game contribution make the welcome headline less helpful to a Tower Rush player. The score evaluates the operator route, not the probability of a winning round.

The bonus category covers the offer and its conditions; its score does not make this game eligible. Likewise, successful mobile launches do not remove the first-withdrawal ID requirement. The methodology explains how the operator categories are assessed and weighted.

For Pakistan readers considering this route, the decision rests on the same practical points: Raast P2P completed with a fee, the welcome contributed 0%, mobile access performed consistently in the measured series, and KYC and account controls still governed use. The overall 6.59/10 reflects that balance. Compare the other Tower Rush operator routes before choosing an account.

Play responsibly

Publisher and operator roles