Casino / Live
Cricket Targetbets sits inside the 87db1 lobby as a cricket-themed fixed-target betting game where you decide a run total and back it across delivery intervals.
Cricket Targetbets is a structured cricket-themed game built around run targets rather than live match outcomes. You pick a target run total for a defined delivery window, and the game resolves whether that target is met or exceeded within the round.
Cricket Targetbets runs on a round-by-round structure where each session has a clear entry point, a target selection phase and a delivery-interval resolution window. On mobile, the game scales to a single-column layout so the target selector and odds display stay visible without horizontal scrolling.
At the start of each round you pick a run-target band from a visible list. The bands cover low, mid and high target ranges, each showing its own odds value before you confirm. You lock in before the delivery interval countdown starts.
Once your target is confirmed, the delivery interval counter runs on screen. Each delivery shifts the live probability displayed beside your chosen target band, so you can follow how close the round is to resolving in your favour.
When the final delivery interval completes, the game resolves the round against your selected target. The outcome — win or no-win — is shown immediately on screen, and the result posts to your account transaction record within the same session.
On a mobile browser the game loads in a single-column view. The target bands, stake input field and round timer stack vertically so nothing is hidden off-screen. You do not need to switch to landscape mode for the full interface to be usable.
Knowing what drives outcomes in Cricket Targetbets means reading what the game itself publishes, not relying on external summaries. The game window contains a rules or information panel — usually accessible via a small icon in the corner of the screen — that shows how target bands
The game's rules panel is inside the Cricket Targetbets window itself. Look for the information or help icon on the game screen. That panel is the authoritative source for how target ranges, delivery intervals and round resolution logic work.
RTP and volatility details appear only where the game interface itself surfaces them. If the panel shows a figure, that is the published value. We do not reproduce separate percentages on this page because only the game's own data is reliable.
Cricket Targetbets runs in a standard mobile or desktop browser. No app download is needed. The game loads from the lobby in your signed-in account session and the rules panel is accessible on the same screen without navigating away.
Every completed round appears in your account's transaction history with stake and outcome recorded. You can use this record to review your activity across sessions. The record updates within the same session, so there is no need to wait for a separate report.
If something in a Cricket Targetbets round does not resolve as the rules describe, or if you cannot locate the game inside the lobby, there are a few places to check before reaching out.
The rules panel inside Cricket Targetbets is the first place to check for mechanics questions. It covers target band calculations, delivery interval logic and how the round resolves. Open it via the information icon visible on the game screen during any session.
Your account transaction history logs every Cricket Targetbets round with stake, target selection and outcome. If a round result looks unexpected, your history gives you the round detail needed to raise the issue through the site's published support route accurately.
For account or game-level issues that the rules panel does not answer, use the support contact route shown on the 87db1 site. Have your account details and the relevant transaction reference ready. Only the channels listed on the site are the verified contact points.
The information on this page describes Cricket Targetbets as it appears in the 87db1 lobby — its round structure, the controls visible on screen, where published rules sit and how your transaction history records outcomes.
We point to the in-game rules panel as the authoritative source for Cricket Targetbets mechanics. That panel covers delivery intervals, target band logic and resolution conditions as the game itself defines them — not a third-party summary.
RTP and volatility are shown only if the game's interface publishes them. This page does not reproduce percentage figures that were not drawn from the game window. If the game exposes an RTP value, you will find it in the game's own information panel.
Every round you complete in Cricket Targetbets posts to your account transaction record with the full stake and outcome detail. That record is the verified reference point if you need to check or question a result — not an estimate or a session summary.
Whether Cricket Targetbets is available to you depends on your local law and the eligible regions configured in your account. The account area shows the access conditions that apply. We do not make eligibility claims that override what your account settings reflect.
Quick definitions for the terms that come up most often when you are playing or reading the rules for Cricket Targetbets. Each entry is drawn from the mechanics visible in the game itself.
A target band is a predefined run-total range you can back in a single round. Each band covers a span of possible run totals and displays its own odds value before you confirm your stake.
A delivery interval is one counted step in the round's progression, modelled on a cricket delivery. Each interval advances the round timer and shifts the probability display shown alongside your chosen target band.
Round resolution is the moment the game calculates whether the actual run outcome met your selected target band. It occurs after the final delivery interval and determines whether your stake returns a win or a no-win result.
RTP stands for Return to Player — the theoretical percentage of stakes returned over many rounds. For Cricket Targetbets, the figure is shown only where the game's own interface publishes it; no external value applies.
Your stake is the amount you commit to a single round before the delivery interval countdown starts. It is entered in the stake field on the game screen and recorded immediately in your account transaction history.
Volatility describes how frequently and how heavily a game pays relative to its stake. High volatility means less frequent but larger swings; low volatility means more frequent smaller outcomes. The game panel publishes this only if the interface includes it.
These questions come up regularly from people who have just found Cricket Targetbets in the lobby or want to understand how the round structure works before they start.
After signing in, look in the sports games or cricket games section of the lobby. Cricket Targetbets is listed there. If you use the search field in the lobby, typing the game name brings it up directly without scrolling through the full catalogue.
No download is needed. The game runs in your mobile or desktop browser from your signed-in account session. Load the lobby, open Cricket Targetbets and the game launches in the same window. The rules panel is accessible on the same screen.
Yes. The game scales to a single-column mobile layout with the target selector, stake input and round timer stacked vertically. You do not need to switch to landscape mode — the full interface is usable in portrait orientation on a standard mobile browser.
Every completed round posts to your account transaction history with the target band you chose, your stake amount and the round outcome.
Cricket Targetbets runs on short round cycles, so you can complete multiple rounds in a single sitting. There is no published cap on rounds per session, but your account wallet balance and any limits shown in your account settings apply to each stake you place.
Refresh your browser and sign back into your account. The round outcome is recorded server-side, so the transaction history will show the result once the round completed — even if your screen did not display it. Use the published support route if the transaction record is unclear.