Browser access
Chrome, Safari, Firefox and the browsers bundled with local handsets all render the lobby. Keep yours updated so sign-in prompts and wallet screens behave the way they should.
Your 256bd account opens straight from your phone's browser, with the slot lobby, live tables and the cricket betslip sharing one sign-in.
Speed is the point. We keep the sign-in screen to one field plus a fingerprint or face check on handsets that support it, so a returning session takes seconds rather than a typed password. Dark mode is the default, useful when you're checking a BPL score late at night without lighting up the room. Alerts are opt-in per category, so slot news never wakes you for a cricket market. And if the connection drops, the last lobby screen you loaded stays readable until the network comes back.
Your session stays open for the length our security policy allows, so reopening on the same phone lands you back in the lobby. Fingerprint or face unlock handles the rest where the handset supports it.
Nothing to memorise. You approve the device once with your fingerprint or face, and every visit after that asks for the same check instead of a typed password, which helps on a moving bus.
Dark mode is set as the default on phones and the colour set stays readable at low brightness, useful for a late Crash Blaze check without the screen glaring back at you.
Turn notifications on for the things you follow and off for everything else. Match reminders, table openings and wallet confirmations each have their own switch, so nothing lands that you didn't ask for.
Most phones sold in Bangladesh over the last few years run the browser lobby without trouble; the real question is screen size and connection, not a spec sheet. We list supported devices on the access page and refresh it whenever a build changes, so you can confirm before you sign in. Small screens fall back to a single column with the betslip pinned low, while larger phones and tablets get the wider grid. If your model isn't listed, the browser route still works with the account you already have.
Chrome, Safari, Firefox and the browsers bundled with local handsets all render the lobby. Keep yours updated so sign-in prompts and wallet screens behave the way they should.
Small phone screens get a single-column view, while bigger handsets and tablets show the wider grid with side panels. Rotating the device helps when you compare two live tables.
You need one registered account, a verified phone number and a wallet name that matches your 256bd profile. Duplicate or shared accounts are held at the sign-in step.
Open the access page and read the device line. It says whether a native build exists for your handset today and which browser route applies when it doesn't.
Access depends on your local law and eligible regions. If your region isn't supported, the sign-in step stops before the lobby loads and no details are stored.
The app build is a shortcut layer over the account you already hold. Push alerts tell you when a live table you follow opens or a Cricket Toss Master round is about to start, so you stop refreshing the lobby by hand. Fingerprint or face sign-in replaces typing a password on a crowded bus. From the betslip you can place a cricket
market and confirm it in two taps, while the wallet screen keeps your saved bKash, Nagad and Rocket details one step away. Crash Fast Lift and Roulette GlowSpin open inside the same shell, so switching tables never means signing in again.
There is nothing to sideload. Open the site on your phone and the lobby reads your screen size, laying the tables out in a single column. Sign in with your usual 256bd number and password, or the biometric you set earlier, and the account wallet loads with your saved bKash, Nagad or Rocket details. Add the page to your home screen from
the browser menu if you want an icon that skips the address bar; it opens the same session with no update prompt in between. If a native build is live for your handset, the access page shows that route instead.
These are the things people message our support team about most often, answered plainly. If your handset isn't covered below, open the access page first — the device line usually settles it before you contact anyone.
Service availability depends on eligible regions and local law. Users should check local rules before opening an account.
Access may be available only where local law permits.