App / Live
bet1177 keeps registration on one short page: an email address or mobile number, a password you choose, then a confirmation before the lobby loads. Nothing is charged to finish the form — the wallet screen, where Nagad, Rocket and Upay sit, opens after you sign in.
Registration here is a form, not a queue. You type your email address or your mobile number, set a password, and submit — that is the whole of the register step. After that the page moves you to a confirmation screen so you can see the account was created against the detail you gave. Signing in later uses the same pair: the same email or number, the same password. If either one is mistyped, the form tells you before it lets you through, so you are not left guessing at a half-open account. We keep the fields short on purpose. Every extra box on a sign-up page is one more place a number can go wrong, and a Bangladesh mobile number is easy to mistype when you are doing it one-handed. Before you submit, read the number back to yourself digit by digit. Your password is yours to set and yours to keep; we do not ask you to send it anywhere. Once the lobby loads, open your account area first, not the game list.
Registration asks for an email address or a mobile number, plus a password you set yourself. No wallet detail is requested on that page. You add a funding route later, from inside the signed-in account, so the first step stays quick enough to finish on a phone.
After you submit, the page shows a confirmation tied to the detail you entered. Read it once before you carry on. If the number or address looks wrong, sign out and open the form again rather than taking a typo into the lobby with you.
Your sign-in uses the email address or mobile number and the password from the register step. Nothing else is needed to get back in. Keep both where your phone can reach them, and ask the help route to correct a number that has changed rather than registering again.
If a field will not take what you typed, the help routes published on the site are where to ask. We do not advertise a reply window, and we would rather you send one clear message with the error wording than three short ones that lose the detail.
Money reaches your bet1177 account by wallet, and the register step is where that habit starts. We do not ask for a wallet number on the sign-up form. You finish the account, sign in, then open the wallet screen, where Nagad, Rocket and Upay appear as the local routes we support. Each works the way you already use it on your phone: send from the wallet app, then record the transfer against your account so it can be matched. The matching step matters more than the sending step. A transfer sent from a wallet registered in someone else's name is the usual reason a record sits unmatched, so use one that carries your own name. Copy the reference number the wallet app shows you before you close its confirmation screen — that string is what our wallet screen asks for. If a transfer does not appear on your record, check the number you entered against the app before sending the same amount twice. Registration commits you to nothing. Availability of each route depends on local law and eligible regions.
Nagad is the route most people already carry on the phone, so it sits first on the wallet screen. Send from your Nagad app to the number the screen shows, then paste the reference the app gives you. The record appears against your account once the transfer is matched.
Rocket sends arrive as a wallet-to-wallet transfer, and the wallet screen asks for the reference string the Rocket app shows on its confirmation. Read the number back before you tap send, because the reference is what links the money to your account and not to the phone.
Upay is the third local route on the same screen, and the steps do not change: send from the app, copy the reference, enter it where the wallet form asks. Nothing at registration depends on which of the three you pick — choose the one already loaded on your phone.
Four things are worth settling before you open the register form, and none of them involve money. First, check that the page you are on is the current bet1177 domain; a lookalike address is the easiest way to hand your password to somebody else. Second, keep the email address or mobile number you can actually open to hand, because a number that has run out will not receive a confirmation. Third, choose a password there and then, not one you already use for your bank app. Fourth, have your own name and date of birth ready if the form asks for them. The checks take a minute. Read the address bar rather than the page design — a copy can match colours easily, but the domain in the bar is the part you can verify. Keep your SMS inbox in reach while you fill the form. If you share a phone, sign out when you hand it over.
Type the address yourself instead of following a link someone sent you. The domain in the bar is the detail a copied page cannot fake, so confirm it before you enter an email address or a password. Save the page once you are sure of it.
You need an inbox or a working SIM you can check while the form is open. Use a number that stays with you, not a friend's or a relative's. A confirmation sent to a number you cannot open leaves the account stranded on the first step.
Pick a password you can type one-handed and still remember a week later. Keep it separate from your bank app and from your wallet PIN, because this one only guards the account here. Nothing on the register page asks you to send it by message.
Have your full name and date of birth as they appear on your own documents. Entering a friend's detail, even for a quick first look, causes trouble later when the account has to match a wallet in your name. Keep the two consistent from the start.
Losing a session is normal — you close the browser, the phone restarts, the page times out. What matters is that you get back into the same account rather than opening a fresh one with a second email address. Start at the sign-in form and use the exact email address or mobile number you registered with; a single wrong digit looks identical to a wrong password from the page's side. If the password is the part you have lost, do not create a second account to work around it. Open the account help routes published on bet1177 and describe what you can and cannot see. Tell the team the email or number on the account and what happens when you submit the form, because the error shown there is the first thing anyone needs. We will not promise a reply window here; what we can say is that every request sent through the published routes reaches the team that handles access questions. Keep a record of the message you sent so a follow-up continues the same thread.
Start where you signed in last: the sign-in form, not a new register page. Enter the email address or mobile number exactly as you first gave it. Change one character and the page treats you like a stranger, which reads the same as a wrong password on screen.
Before you submit, compare the number on screen with the one in your phone settings. Autofill sometimes carries an old address from another site, so clear the field and type it fresh. A failed attempt costs nothing but a retry at this point.
If two careful attempts fail, stop retrying and open the help route published on bet1177. Describing what you typed and what came back gives the team something to work with, and it keeps your account on one thread instead of splitting the story across messages.
Do not register a second account to get around a sign-in problem. Two accounts split your wallet records, and a transfer sent against one will not show on the other. Let the help route fix the first account, because that is the one your history sits on.
Account problems are usually small and specific: a number that will not accept, a password that will not match, a form that stops half way. Ask about them through the routes published on this site rather than in a message to whoever shared a link with you. Those routes reach the team that handles registration and sign-in questions, and they are the only channels we can point you to from here. What makes an account question easy to answer is detail. Tell us the email address or mobile number on the account, the page you were on, and the exact wording the form gave back. If you already sent a message, follow the same thread instead of starting a new one. Do not send your password, and do not send a wallet PIN, in any message. Nobody on our side needs either to look at an account. If a transfer is the thing that looks wrong, say so in your own words and keep the reference string the wallet app gave you nearby.
Every account question starts on the help page published on this site, which carries the route to the team that reads register and sign-in problems. Write what you typed, what the form said back, and the email or mobile number on the account. One clear message saves a round of replies.
Once you are signed in, the account area is where you check the detail we hold: your email address, your mobile number, your name. Look there first if a sign-in fails, because an out-of-date number explains most of them. Ask the help route to correct it if it has changed.
The terms and privacy pages set out what we hold about your account and how to raise a question about it. Both are linked from this site and neither needs a sign-in to read. Read the account section before you register, so the form lines up with what you have already seen.
Registration is a short form, and most of the safety questions around it are ones you can settle yourself before you type anything. The domain in your address bar is the first check; a page that copies our colours but sits on a different address is not us. The terms and privacy pages published here are the second, because they set out what we hold about your account and what you can ask us to correct. Everything else is habit. Use a wallet registered in your own name, since a transfer from somebody else's Nagad, Rocket or Upay account will not match the account holder. Keep your password off shared phones, and sign out when you finish. Access depends on your local law and eligible regions, so check that before you register rather than after. If something about an account looks wrong, the help routes on this site are the place to raise it; we would rather answer a question early than unpick a problem later.
Confirm the address in the bar says bet1177 before you type a password. Copied pages match colour and wording easily, so the domain is the part worth reading. Save the page once you are sure, and open it from that saved entry next time instead of a forwarded link.
The terms and privacy pages sit on this site and open without a sign-in. They set out what we hold about your account and how to raise a question about it. Read them before registering, so nothing in the form arrives as a surprise at the last field.
A wallet transfer is matched to the account holder, so send from a Nagad, Rocket or Upay account registered in your own name. Using a relative's wallet, even with permission, is the common reason a record sits unmatched and a question lands with the help team.
Availability depends on your local law and eligible regions. Check that before you register rather than after, and treat anything you read elsewhere about access as unconfirmed until this site itself shows it. No setting inside the lobby changes that position for you.
These are the questions we get asked at the register step most often, answered the way we would answer them across a counter. Registration asks for very little, and most confusion comes from a mistyped number or from opening a second account instead of recovering the first. A sign-in uses the same email address or mobile number and the same password you set on the form, so there is nothing new to learn between the two pages. If an answer here does not cover your case, the help routes published on this site carry the question to the team that handles account access. We do not list reply times, because we would rather point you at a real route than a promise. Keep the reference string from any wallet app until the transfer shows on your record, and keep your password out of messages.
No. The form asks for an email address or mobile number and a password, and that is the whole of it. You add a funding route from inside the signed-in account, on the wallet screen. Opening the account first lets you look around the lobby before you send anything.
Use whichever one you entered at registration, and keep using the same one. Mixing an email on one visit and a number on the next is the usual reason a sign-in fails. If you cannot recall which you used, try the one you check most often on that phone.
Check the digits first, because a single swap looks like a rejected number. Use the format the field shows, without spaces or extra characters at the start. If it still refuses, send the number and the exact error to the help route published on this site.
Keep to one account. A second registration with a different email splits your records, and a wallet transfer sent to one will not appear on the other. If you cannot get into the first account, use the help route rather than opening a new one beside it.
On the wallet screen inside your signed-in account, listed against your record. That screen is the reason registration comes first: the record is tied to your account, not to the handset. Keep the reference string from the wallet app until you can see the transfer listed.
Yes. The form is built for a phone screen and needs no app installed. Keep the browser tab open while you wait for a confirmation, and have your SMS inbox or email app within reach. A desktop browser shows the same fields if you prefer a larger keyboard.