Fast Fielder

Demo, RTP 97.50%, paytable, symbols & full capture data

Free demo · not real-money play 1 plays in 30 days · last one 6 days, 5 hours ago
✓ Working · checked 1 week, 4 days ago Verified · 22 Aug 2026
RTP 97.50%
Volatility —
Max win —
Grid —
For webmasters & affiliates
Embed demo

Direct demo link or iframe code for your site. Free · no sign-up

Asset pack

15 screenshots · palette · spec sheet. ZIP — captcha check, no sign-up

Slot API

GET /v1/slots/fast-fielder-b27/

10,000 free requests / month · sign-up required

Ask AI MCP

This slot’s spec, symbols, palette and demo link — queryable from Claude, Cursor or VS Code. Read-only · free · no key, no sign-up.

mcp.i-gaming.tools/mcp
What to ask → 2-min setup
Verified capture
iGaming Tools capture pipeline Manual demo playthrough · paytable OCR-verified

Captured by hand from a live demo and verified frame-by-frame — the paytable was OCR-checked against the provider. 4 aspects we couldn’t confirm are flagged below, not hidden.

Captured 22 Aug 2026 View capture log

Per-screen breakdown

15 demo screens
15 PNG (ZIP)
Autoplay settings
autoplay Autoplay settings
Base game
base_game Base game
Base game
base_game Base game
Base game
base_game Base game
Info / About screen
info Info / About screen
Logo
logo Logo
Preview / Loading screen
preview Preview / Loading screen
Rules / How to play
rules Rules / How to play
Rules / How to play
rules Rules / How to play
Rules / How to play
rules Rules / How to play
Rules / How to play
rules Rules / How to play
Rules / How to play
rules Rules / How to play
Rules / How to play
rules Rules / How to play
Game settings
settings Game settings
Win screen
win_screen Win screen

Search Demand

monthly search interest · last 12 months
Total demand / month
Sep '25: 30 30 Sep Oct '25: 20 20 Oct Nov '25: 40 40 Nov Dec '25: 40 40 Dec Jan '26: 40 40 Jan Feb '26: 20 20 Feb Mar '26: 20 20 Mar Apr '26: 20 20 Apr May '26: 20 20 May Jun '26: 20 20 Jun Jul '26: 20 20 Jul Aug '26: 0 Aug
Per-country demand by month · sorted by month-over-month growth (freshest first)
Country Aug '26 Jul '26 Jun '26 May '26 Apr '26 Mar '26 Feb '26 Jan '26 Dec '25 Nov '25 Oct '25 Sep '25
🇵🇰Pakistan 0 0 0 20 0 0 0 20 0 20 0 0
🇲🇾Malaysia 0 0 0 0 0 0 0 0 20 0 0 0
🇵🇭Philippines 0 0 0 0 0 0 0 0 0 0 0 10
🇮🇳India 0 20 20 0 20 20 20 20 20 20 20 20
Full per-country breakdown via the API →

What we extracted from Fast Fielder

Everything pulled from Fast Fielder into machine-readable data — symbols, paytable, palette, modes and assets. A capture result, not a game review.
15 screens captured
6 palette colors from frames
6 accessibility groups profiled
4 gameplay modes NOT captured — flagged honestly below

manual demo playthrough → 15 screens captured → paytable verified (OCR) → catalogued & reviewed

Specification

verified parameters
provider Turbo Games
series Cricket Arena · 4 games in this series ↓
rtp 97.50% · single configuration
bonus_buy No
mechanic Instant Win
release_date 2023

Cricket Arena series

where this game sits among its own

Its 97.50% is the highest RTP of the 2 games in the family. The series also includes 2 crashs, not compared here.

Game Released RTP
Cricket Boom Crash Apr 2025 95.99%
Fast Fielder you are here Jun 2023 97.50%
Spin Strike Apr 2023 93.50%
Wicket Blast Crash Apr 2023 95.00%
See all 4 games in this series →

Bonus modes

2 modes
Base Game Modifier manual
Manual Betting

Player chooses Under N or Over N by dragging the slider (or the chevron buttons), sets the stake on the circular Bet Amount dial, then presses the matching blue (Under) or green (Over) Place bet button; one random number 0-100 resolves the round instantly and pays bet_amount x multiplier, rounded down to two decimals, if the result lands on the chosen side.

Other autoplay
Autoplay

Dialog opened from the icon between the two Place bet buttons: set the stake and a fixed round count (10/20/50/100) or unlimited (infinity symbol), then start a run on the chosen side via a Start Autoplay button (blue for Under, green for Over); stoppable via a Stop Autobet control named in the rules text.

Colour system

extracted from frames · HEX
Export palette
#131F31 base dominant 1 base
#253349 base dominant 2 base
#344B61 base dominant 3 base
#3189A2 base dominant 4 base
#346D28 base dominant 5 base
#50708E base dominant 6 base

Accessibility

profile for all groups
Color Blind
  • Under (blue) and Over (green) sides are never color-only: each carries the text label 'Under N'/'Over N', a fixed left/right position, and a different wedge texture (smooth felt-like matting for Under vs a mown-grass texture for Over).
  • The rounds history strip marks wins with colored text and losses with grey text and no other cue ('Colorful outcomes stand for winning rounds, grey - for losing ones') - a color-only distinction that is hard to read for red-green colorblind players.
Screen Reader
  • All round-state information (balance, win chance percentages, payout amounts, multiplier values, the slider's N value, round history numbers) is rendered as on-screen text/numerals rather than conveyed only by animation.
Motor Accessibility
  • Every control has a click-only alternative to dragging: slider chevron buttons step the N value, dial +/-/min/max buttons set the stake without dragging; the two Place bet buttons are large, roughly a third of the screen width each, reducing mis-click risk.
Hearing Accessibility
  • Round outcomes are communicated fully through visual cues (ball landing position, balance change, history entry color) rather than requiring audio; a Sound volume slider in Settings can be muted via a crossed-speaker icon.
Low Vision
  • Inside the scrollable Rules panel the first and last visible lines fade to semi-transparent at the top and bottom edges of the viewport, so a line must be scrolled into the panel's centre to be read at full contrast.

Media & assets

5 files · 5 types
15 PNG (ZIP)
Base game
base_game
Base game
base_game
Base game
base_game
Logo
logo
Preview / Loading screen
preview

Data provenance

what we captured and what we didn't
base game idle (N=50, both sides x1.95), slider dragged to its minimum (Under 3 / Over 3, x32.50 / x1.01), a lost round (Under 3, roll 74.03) and a won round (Over 25, roll 39.54, x1.30 payout)
rules booklet in full - all 6 scroll pages / 7 sections: How to Play, Game Details, Min & Max Multiplier, Rounds History, RTP (97.5%), Autoplay, Settings, Disconnection Policy, Version (game 1.0.1 / RNG 2.0.0)
Limits submenu (min bet $0.1, max bet $100, max profit $10000 operator cap), Settings overlay (nickname, sound, Turbo Universe menu), Autoplay dialog (stake, round count presets, unlimited), preview/loading screen, logo
exact bets_per_round behavior is not printed as an explicit rule: rules text frames Under/Over as an either/or choice and the UI has two separate Place bet buttons, pointing to one side per round, but no directly stated number exists to confirm it
no explicit formula converting the chosen win-chance percentage into its multiplier value is printed anywhere in the rules; only the downstream win = bet_amount x multiplier formula is given, multiplier values are read directly off the field/panel per configuration
provably fair verification is not confirmed inside this build - no seed/hash display or verify tool was found in the rules or on any captured screen, despite the provider's general marketing claim of provably-fair gameplay
whether the two Place bet buttons can be pressed in immediate succession within the same round, or whether pressing one starts a non-interruptible resolution, was not testable from static screenshots

Ask AI about Fast Fielder

MCP · VERIFIED CAPTURE DATA

AI apps like Claude are chat apps: you ask, they answer. Normally they can’t see this capture — MCP is the plug that connects them to it. Add one link, and your chat answers with this slot’s verified data. No coding.

Server https://mcp.i-gaming.tools/mcp paste into Claude, Cursor, VS Code, Gemini, Codex, Windsurf or Zed · read-only · free · no key Setup guides →
What it looks like

How does Fast Fielder play? Keep it simple.

Player chooses Under N or Over N by dragging the slider (or the chevron buttons), sets the stake on the circular Bet Amount dial, then presses the matching blue (Under) or green (Over) Place bet button; one random number 0-100 resolves the round instantly and pays bet_amount x multiplier, rounded down to two decimals, if the result lands on the chosen side.

RTP 97.50%demo ✓

From the verified capture of 22 Aug 2026 — not from the AI’s memory.

Playersearch_slots

“Find slots like this but medium volatility — with free demos.”

→ matches by mechanics and theme; official free demos only.

Affiliateget_slot ×2

“Comparison table: Fast Fielder vs Mines — RTP, max win, bonus buy.”

→ side-by-side table, ready for your review page.

Editorget_slot

“Fact-check my review: RTP, max win, paylines, bonus-buy price, release year.”

→ OCR-verified numbers — including the 4 aspects we couldn’t confirm, flagged.

Designerget_slot

“Creative brief: theme, 6 palette hexes and the symbol descriptions.”

→ same palette and symbol data as the sections above, as one brief.

Verified capture: manual playthrough, paytable OCR-checked Honest gaps: 4 uncaptured aspects flagged, not hidden Read-only · free, no key · per-IP rate limit 18+Free demo data only — no real-money links

Technical info

Free JSON data API — token auth.
GET /api/v1/slots/fast-fielder-b27/

Public data API. Send Authorization: Token <your-token>. Full structured data, media and demo links in one call. See the API docs.

Spec sheet — extracted, unverified. This is the raw OCR dump, not the full API response.
GET /api/v1/slots/fast-fielder-b27/
{
  "game": {
    "name": "Fast Fielder",
    "in_game_wordmark": "FAST FIELDER",
    "wordmark_note": "In-game logo top-left splits the name across two colors/fonts: 'FAST' in bold italic yellow-orange with a dark outline, then a small circular red badge containing a tiny running/batting cricketer silhouette, then 'FIELDER' in bold italic white with a dark outline. The text itself matches the catalogue name exactly (no shortened variant, unlike some other Turbo Games titles).",
    "provider": "Turbo Games",
    "game_kind": "instant_win",
    "genre": "Single-round over/under prediction game on a circular dial, cricket-themed (part of the provider's self-described 'cricket (game) series' per the provider's own game page text). Not a reel slot: no symbols, no paylines, no cash-out ladder. Each round resolves instantly with a random number 0-100.",
    "art_style": "Semi-realistic 3D-rendered playing field (textured turf, felt matting, wood grain pitch board, glossy cricket ball with a visible highlight/reflection) shown top-down/orthographic, sitting on a plain flat dark navy-to-black dashboard background lit by two large soft stadium floodlight glows (blurry grids of white light discs) placed left and right of the field. All surrounding UI chrome (buttons, dials, sliders, modals, panels) is flat, minimalist dark-mode dashboard design: rounded rectangles, thin light outlines, solid saturated blue/green/red accent colors, bold condensed sans-serif typography, no gradients besides the ambient floodlight glow. No cartoon characters (aside from the tiny mascot silhouette inside the logo badge) and no painterly cel-shading. Overall mood: a clean, slightly moody nighttime sports-betting/casino dashboard, not a whimsical cartoon.",
    "demo_currency_note": "The demo balance is shown as US dollars ('Balance: $1000'). This is the demo-wallet display convention observed on this build; it is not asserted here as the game's real configured currency."
  },
  "rtp": {
    "printed_statement": "Rules panel, RTP section (rules_p4.png), dossier verbatim: \"Fast Fielder has RTP 97.5%\".",
    "form": "SINGLE FIXED NUMBER, with NO caveat about bet size, slider position (N value), or any other player choice anywhere in the rules text.",
    "cross_check": "The provider's own game-page snapshot (sources[].page_url text) states the same figure: \"Fast Fielder has an RTP of 97.5%\" — matches the in-build number exactly, unlike several sibling titles from this provider where the storefront number disagrees with the build.",
    "note_on_family_comparison": "This is a deliberate, verified difference from the sibling title Dice Twice (same provider, same Under-N/Over-N slider mechanic, same x32.50 multiplier ceiling): Dice Twice's rules state the RTP DEPENDS on bet size ('With a bet of \"1.0\", the minimum RTP is 97.06%. When betting \"0.1\", the RTP can decrease to as low as 89.10%'), while Fast Fielder's rules give one number with no such qualifier anywhere in the four rules pages read in full. This was checked specifically and is not an omission — the qualifying sentence simply does not exist in this game's rules text."
  },
  "multipliers": {
    "min_multiplier": {
      "value": 1.01,
      "source": "rules_p3.png verbatim: 'Min multiplier is x1.01.'"
    },
    "max_multiplier": {
      "value": 32.5,
      "source": "rules_p3.png verbatim: 'Max multiplier is x32.50.'",
      "second_channel": "Confirmed on the live field: dragging the slider to its extreme position ('Under 3' / 'Over 3') makes the small (3% chance) side display exactly 'x32.50' on the field itself (base_game_slider_min.png) — matches the printed rules number.",
      "note": "This is a FRACTIONAL cap (x32.50), consistent with how this provider's slider-based over/under games generally compute the multiplier from the selected win chance rather than picking it from a round list."
    },
    "formula_win_amount": {
      "printed": "rules_p2.png verbatim: \"Your potential win amount is calculated by multiplying your bet amount by the payout multiplier. This means that the higher the payout multiplier, the more you stand to win if your prediction is correct.\" Also: \"Win amount is rounded down to two decimal places.\"",
      "note": "This is the ONLY formula printed anywhere in the rules. No explicit mathematical formula converting win-chance-percent into the multiplier value is printed (unlike e.g. Turbo Plinko's rules, which do print a coefficient-sum formula). The relationship is only described qualitatively: 'The riskier your prediction (that is, choosing a smaller sector), the higher your potential win!' The multiplier values themselves are read directly off the field/panel per configuration, not derived by us from a formula."
    }
  },
  "bet_limits": {
    "min_bet": {
      "value": 0.1,
      "currency": "$",
      "source": "Menu -> Limits (info.png): 'Min bet: $ 0.1'."
    },
    "max_bet": {
      "value": 100,
      "currency": "$",
      "source": "Menu -> Limits (info.png): 'Max bet: $ 100'."
    },
    "second_channel": "The 'min'/'max' buttons on the circular Bet Amount dial (base_game.png / autoplay.png) snap the stake to the same two figures, confirming the Limits menu numbers.",
    "max_profit_operator_cap": {
      "value": 10000,
      "currency": "$",
      "source": "Menu -> Limits (info.png): 'Max Profit: $ 10000'.",
      "important_distinction": "This is an OPERATOR-SIDE ABSOLUTE MONEY CAP on a single round's profit, NOT a multiplier and NOT the same thing as the x32.50 multiplier ceiling above. It is stated in the tech doc separately on purpose (see provider defect P-T08 in the internal playbook: this provider's games often print up to three different 'maximum' figures that must not be conflated)."
    }
  },
  "version_info": {
    "game_version": "1.0.1",
    "rng_version": "2.0.0",
    "source": "rules_p6.png, section 'Version', verbatim: 'Game version: \"1.0.1\"' and 'RNG version: \"2.0.0\"'. Also duplicated in the Settings overlay (settings.png, top-right badge).",
    "note": "These are build/RNG version numbers, NOT a release date and NOT a provider game-code (provider_ref)."
  },
  "provably_fair": {
    "status": "NOT CONFIRMED in this build.",
    "evidence": "The rules panel was read in full (all four pages, seven section headers: How to Play?, Game Details, RTP, Autoplay, Settings, Disconnection Policy, Version). None of these sections contain any round-verification / seed / hash-check mechanism. The only build-identifying information offered anywhere in the UI is the Game version / RNG version pair described above.",
    "caveat": "The provider's public storefront/marketing copy elsewhere claims a cryptographic provably-fair seed for its games in general, but that claim is NOT demonstrated anywhere inside this playable build (no 'Provably Fair' menu entry, no seed/hash display, no verify tool). Per project rule, a claim from one source (marketing copy) that is not corroborated by the build itself is not asserted as a game fact here — left as an open gap, not filled in as true or false."
  },
  "round_structure": {
    "bets_per_round_assessment": {
      "conclusion_from_text": "The rules describe the decision as a single either/or choice, not a simultaneous double bet. Game Details section (rules_p2.png) verbatim: \"As a player, your first task is to decide whether you believe the result of the roll will be 'under' (blue button) or 'over' (green button) a particular number.\" The wording 'whether... or' frames Under and Over as two mutually exclusive options for ONE bet, not two bets placed together.",
      "supporting_visual_evidence": "The two 'Place bet' buttons (blue Under / green Over) are visually two separate call-to-action buttons rather than one combined 'confirm both' control, and the same pairing repeats in the Autoplay dialog as two separate 'Start Autoplay' buttons (blue / green) — consistent with picking exactly one side per action, not both at once.",
      "caveat": "The rules text never states in so many words 'you may only place one bet per round' or gives an explicit bets_per_round number the way some sibling titles do (e.g. Crash X's two simultaneous stake panels). This conclusion is the best available reading of the printed text plus the UI's exclusive-choice framing, not a directly printed number — flagged accordingly rather than stated as a hard fact."
    },
    "resolution": "Pressing 'Place bet' on the chosen side generates one random number from 0 to 100 (per How to Play: 'Press \"Place bet\" to generate a random outcome from 0 to 100'); if that number falls in the selected side's range relative to the slider position N, the round wins and pays bet_amount x multiplier (rounded down to 2 decimals); otherwise the stake is lost.",
    "history_strip": "A pill-shaped bar just under the header (visible across all base_game/round_lost/win_screen frames) accumulates the numeric results of recent rounds. Rules verbatim (rules_p3.png): 'At the top of the game screen you can see the result of the previous game rounds. Colorful outcomes stand for winning rounds, grey - for losing ones.' Observed directly: '74.03' rendered in muted grey after a loss (round_lost.png), then '74.03' (grey) plus '39.54' rendered in green after a subsequent win (win_screen.png)."
  },
  "payout_presentation": {
    "no_traditional_paytable": "There is no symbols grid and no separate paytable screen/page — this is a single-outcome prediction game, not a reel or cluster game.",
    "on_field_presentation": "The current payout information for BOTH sides is always visible in two places simultaneously while idle or configuring a bet: (1) printed directly on the circular field itself, in large bold white numerals centered inside each colored wedge (e.g. 'x1.95' / 'x1.95' at the default N=50; 'x32.50' on the small blue wedge and 'x1.01' on the large green wedge at N=3); (2) in the circular 'Bet Details' info panel to the right of the field, which lists three paired rows — 'Win Chance' (percentages), 'Payout' (dollar amounts at the current $1 stake shown, blue value then green value), and 'Multiplier' (the same x-values as on the field) — plus a 'Bet Details' text link beneath it.",
    "field_as_gauge": "The circular field behaves like a live pie/radial gauge: a straight boundary line through the center divides it into a blue wedge (Under N) and a green wedge (Over N) whose arc lengths are always proportional to N% and (100-N)% respectively. At N=50 the boundary runs straight down the middle (two equal halves); at N=3 the blue wedge shrinks to a thin sliver near the bottom of the circle while green expands to fill nearly the whole disc. Small white numeric tick labels ('25', '50', '75', '0') sit around the rim like clock-face graduations to help gauge the wedge size at a glance. A red cricket ball marks the actual roll RESULT after each round, landing on a point around the circle's circumference (e.g. at coordinate '74.03' or '39.54' along the 0-100 scale) — its landing side (blue half vs green half) is what determines win/loss, independent of exact wedge boundary rendering nuances."
  },
  "screens": [
    {
      "type": "preview",
      "file": "preview.png",
      "description": "Provider splash screen, not a Fast Fielder screen per se: solid black background; centered horizontally and vertically, the Turbo Games provider logo — a red filled circle containing a black diagonal cross/X cut-out with a white 'X' accent, immediately followed by bold condensed white uppercase wordmark reading 'TURBO' on the first line and 'GAMES' on the second line. No numbers, no promotional text, no Fast Fielder branding on this frame; per provider playbook this is an early loading frame that later resolves into gameplay.",
      "ocr_text": "TURBO GAMES"
    },
    {
      "type": "base_game",
      "file": "base_game.png",
      "state": "Idle/default, slider at N=50 (even 50/50 split)",
      "layout": {
        "top_left": "'Balance:' label in light grey followed by '$ 1000' in bold white.",
        "top_left_below": "In-game wordmark 'FAST FIELDER' (see game.wordmark_note above), positioned left, below the balance.",
        "top_center": "Empty rounded-pill history bar (no results yet on this very first idle frame).",
        "top_right": "Icon cluster: white 'TURBO' logo pill badge with red dot notification marker and 'UNIVERSE' small text beneath the icon, a speaker/sound icon, and a settings icon made of three horizontal sliders/equalizer lines each with a small circle knob.",
        "right_edge": "Vertical red pill-shaped badge reading 'DEMO MODE' rotated 90 degrees, with a small circular refresh icon above it.",
        "center_left_and_right": "Two large soft-focus stadium floodlight graphics: a 4-row grid of blurred bright white circular light discs fading into a blue-grey halo, mirrored left and right of the playing field, against the plain dark navy-black background.",
        "center": "Large circular playing field (see payout_presentation.field_as_gauge above): left/blue half labeled 'Under 50' beneath it, right/green half labeled 'Over 50' beneath it; both wedges show bold white 'x1.95' centered inside them; in the very middle of the field sits a small tan/brown wooden pitch plank with a vertical wooden stump-post pair at each end and a glossy red cricket ball resting on a small white base marking, centered on the plank.",
        "below_field": "Horizontal slider control: 'Under 50' text label (blue) at left end, 'Over 50' text label (green) at right end, left/right chevron arrow buttons at the extreme ends, a round two-tone thumb/handle in the middle displaying the current value '50', track colored blue left-of-thumb and green right-of-thumb.",
        "bottom_left_control": "Circular 'Bet Amount' dial: outer ring with 'max' and '+' tick labels top-right, 'min' and '-' tick labels bottom-left, central white text '$1'; small grey 'Bet Amount' label with an info (i) icon sits just to the left of the dial.",
        "bottom_center": "Two large pill-shaped call-to-action buttons side by side: left solid blue 'Place bet', right solid green 'Place bet'; a small circular badge (compass/target-like icon) straddles the seam between the two buttons.",
        "bottom_right_control": "Circular 'Bet Details' info panel: 'Win Chance' row showing '50%' in blue then '50%' in green; 'Payout' row showing '$1.95' in blue then '$1.95' in green; 'Multiplier' row showing 'x1.95' in blue then 'x1.95' in green; a 'Bet Details' text link sits beside/below the circle.",
        "footer": "Bottom-left small grey text 'Turbo Games · Fast Fielder'; bottom-right a live clock/date readout from the demo wrapper (not part of the game itself, ticks every second)."
      },
      "colors_described": "Background: near-black to dark navy vertical gradient. Floodlights: bright white discs with a soft blue-grey glow halo. Field: left/Under wedge is a medium teal-blue (like cricket practice-net matting), right/Over wedge is a saturated grass green with a subtle mown-lawn texture; a thin white line traces the outer rim and the straight dividing boundary; the outer edge of the circle has a tan/brown soil-colored ring. Center pitch plank: light tan/beige wood grain with darker wood-grain striping; stumps are a slightly darker honey-wood tone. Ball: glossy red with a lighter red/pink highlight and a thin white/cream seam ring at its base shadow. Buttons: Under side is solid medium blue, Over side is solid medium green, both with white bold text and a fine darker-blue/green textured dot pattern overlay. Bet Amount dial: dark charcoal circle with a thin light-grey ring outline, white text and icons. Bet Details panel: dark charcoal circle, blue and green value text matching each side, grey label text. Balance and header text: white and light grey on the dark background."
    },
    {
      "type": "base_game",
      "file": "base_game_slider_min.png",
      "state": "Slider dragged to its minimum extreme via the chevron buttons: 'Under 3' / 'Over 3'",
      "description": "Same layout as the idle frame above, with the field re-rendered to show the maximum-multiplier configuration: the blue (Under) wedge has shrunk to a thin sliver reaching from the field's center down to its lower rim, labeled 'x32.50' in bold white next to it; the green (Over) wedge now fills almost the entire remaining disc, labeled 'x1.01'. Slider labels read 'Under 3' (blue, left) and 'Over 3' (green, right), thumb shows '3'. Bet Details panel: Win Chance '3%' blue / '97%' green; Payout '$32.50' blue / '$1.01' green; Multiplier 'x32.50' blue / 'x1.01' green. This is the on-screen confirmation of the rules-stated maximum multiplier (x32.50).",
      "ocr_text": "Under 3 · Over 3 · x32.50 · x1.01 · Win Chance 3% 97% · Payout $32.50 $1.01 · Multiplier x32.50 x1.01 · Balance $1000"
    },
    {
      "type": "base_game",
      "file": "round_lost.png",
      "state": "Resolved round: $1 bet placed on Under 3 (blue side), field still configured at N=3",
      "description": "Same 'Under 3 / Over 3' field configuration as above, but the roll result now shows: a small history entry '74.03' appears in the top-center pill bar in muted grey/white (a losing result, per the rules' grey=loss convention); the red cricket ball has moved from the center pitch plank up and to the right, landing near the top edge of the green (Over) wedge at the point marked '74.03' along the field's 0-100 scale. Balance has dropped from $1000 to '$999' (top-left), confirming the $1 stake was deducted. Because 74.03 falls in the Over range (greater than the N=3 boundary), and the player's bet was on the Under side, this round is a loss.",
      "ocr_text": "Balance $999 · 74.03 · Under 3 · Over 3 · x32.50 · x1.01"
    },
    {
      "type": "win_screen",
      "file": "win_screen.png",
      "state": "Resolved round: $1 bet placed on Over 25 (green side), field reconfigured to N=25",
      "description": "Field now split roughly into a larger blue (Under 25) quarter-to-third wedge at lower-left and a larger green (Over 25) wedge covering the rest, labeled 'x3.90' (blue) and 'x1.30' (green). The history bar now shows two entries: '74.03' in grey (the earlier loss) and '39.54' in green (this round's winning result). The red ball sits near the top of the circle, above the boundary, landing inside the green (Over) wedge at point '39.54' — since the bet was placed on Over 25 and 39.54 > 25, this is a WIN. Balance increased from '$999' to '$999.3' (top-left, bold white), consistent with a $1 stake being replaced by a $1.30 payout net of the stake already deducted for this round. Bet Details panel confirms: Win Chance 25% blue / 75% green; Payout $3.90 blue / $1.30 green; Multiplier x3.90 blue / x1.30 green. The winning (Over) 'Place bet' button area shows a subtle green glow/highlight around its edges compared to the idle state.",
      "ocr_text": "Balance $999.3 · 74.03 · 39.54 · Under 25 · Over 25 · x3.90 · x1.30 · Win Chance 25% 75% · Payout $3.90 $1.30 · Multiplier x3.90 x1.30"
    },
    {
      "type": "info",
      "file": "info.png",
      "description": "'Limits' submenu, reached via the settings/menu icon. Header 'Limits' centered, '< Back' top-left, 'X' close top-right. Background: black with a faint repeating dotted diamond/plus pattern. Three stacked dark rounded-rectangle cards, each with a red line-icon on the left and bold white value text on the right: a circular-gauge icon with 'Min bet: $ 0.1'; a banknote/card icon with 'Max bet: $ 100'; an upward-arrow-in-circle icon with 'Max Profit: $ 10000'.",
      "ocr_text": "Limits / Min bet: $ 0.1 / Max bet: $ 100 / Max Profit: $ 10000"
    },
    {
      "type": "settings",
      "file": "settings.png",
      "description": "Menu overlay reached via the gear/sliders icon. Top-left dark pill badge 'Play time: 00:15:52'. Top-right dark pill badge showing 'RNG version: \"2.0.0\"' and 'Game version: \"1.0.1\"' stacked, plus a white 'X' close icon. Left panel: a bordered rounded-rectangle card with 'Nickname' label above an editable text field showing a randomly generated name 'Ruling Junglefowl' and a pencil/edit icon on the right; below it, 'Sound' label above a horizontal slider (thin dark track filled mostly red up to a white circular thumb near the right/max end), flanked by a muted-speaker icon (left) and full-volume speaker icon (right). Right panel: 'TURBO UNIVERSE' heading in bold italic white next to a small red/white circular Turbo icon, followed by a vertical menu list with red line-icons: 'My bets' (list icon), 'Limits' (circular gauge icon), 'Rules' (document icon), 'Exit game' (house icon).",
      "ocr_text": "Play time: 00:15:52 / RNG version: \"2.0.0\" / Game version: \"1.0.1\" / Nickname / Ruling Junglefowl / Sound / TURBO UNIVERSE / My bets / Limits / Rules / Exit game"
    },
    {
      "type": "autoplay",
      "file": "autoplay.png",
      "description": "Modal dialog opened via the small circular compass/target icon between the two 'Place bet' buttons, overlaying a dimmed base game (field configured at 'Under 25 / Over 25' with the earlier win_screen state visible behind it, balance '$999.3'). Dialog header shows the same slider readout as the base field: 'Under 25' (blue, left) / 'Over 25' (green, right), chevrons, thumb at '25', close 'X' top-right of the dialog card. Body: 'Bet Amount' label with info icon above a control row — 'min' / '-' button, central '$1' white text, '+' / 'max' button. Below: 'Number of rounds' label above five pill-shaped selector buttons: '10', '20', '50', '100', and an infinity symbol '∞' for unlimited rounds. At the bottom: two large call-to-action buttons side by side, solid blue 'Start Autoplay' (left, matching Under) and solid green 'Start Autoplay' (right, matching Over).",
      "ocr_text": "Under 25 · Over 25 · Bet Amount · min · $1 · max · Number of rounds · 10 20 50 100 ∞ · Start Autoplay · Start Autoplay"
    },
    {
      "type": "rules",
      "page": 1,
      "file": "rules_p1.png",
      "description": "Left sidebar (identical on every rules frame): seven black rounded-rectangle section-anchor buttons in bold white text with thin white borders — 'How to Play?', 'Game Details', 'RTP', 'Autoplay', 'Settings', 'Disconnection Policy', 'Version'. Header reads 'Rules' centered in white, with a '< Back' control top-left and an 'X' close control top-right. Body text is white on black. scrollTop=0 of 2161 (top of document). Opening tagline line with pictographs: two dice/ball emoji, 'Bet on dice, experience cricket excitement! Predict over/under, swing for the fences!' and a lightning-bolt emoji. Heading 'How to Play?' with three bullets: 'Use the slider to change the winning range of the chosen color', 'Press \"Place bet\" to generate a random outcome from 0 to 100', 'If the result turned out to be in the selected range, the win is yours!'. Then heading 'Game Details' and its sub-heading 'Place Bet', whose first lines begin at the bottom and fade out. The panel fades text out towards the top and bottom edges of the scroll viewport, so lines at the very edge of a frame are semi-transparent — that is a design effect, not a capture artefact.",
      "note_on_ocr": "OCR of the previous, differently-scrolled frame is not carried over: the series was re-shot at a 450 px step and page identity changed."
    },
    {
      "type": "rules",
      "page": 2,
      "file": "rules_p2.png",
      "description": "Left sidebar (identical on every rules frame): seven black rounded-rectangle section-anchor buttons in bold white text with thin white borders — 'How to Play?', 'Game Details', 'RTP', 'Autoplay', 'Settings', 'Disconnection Policy', 'Version'. Header reads 'Rules' centered in white, with a '< Back' control top-left and an 'X' close control top-right. Body text is white on black. scrollTop=450. Faded remnant of 'Place Bet' at the top, then its body in full: 'Enter a valid amount in the field \"Amount\".', 'Drag the slider until you reach the desired win chance and payout. There is a circle with the colored sectors to make the evaluation of your chances easier.', 'After everything is settled press \"Place bet\" and ... good luck!'. Then sub-heading 'Gameplay' in full — the under/over choice sentence, the risk/payout sentence, the win-amount formula and 'Win amount is rounded down to two decimal places'. Heading 'Min & Max Multiplier' appears at the bottom with its first line fading. The panel fades text out towards the top and bottom edges of the scroll viewport, so lines at the very edge of a frame are semi-transparent — that is a design effect, not a capture artefact.",
      "note_on_ocr": "OCR of the previous, differently-scrolled frame is not carried over: the series was re-shot at a 450 px step and page identity changed."
    },
    {
      "type": "rules",
      "page": 3,
      "file": "rules_p3.png",
      "description": "Left sidebar (identical on every rules frame): seven black rounded-rectangle section-anchor buttons in bold white text with thin white borders — 'How to Play?', 'Game Details', 'RTP', 'Autoplay', 'Settings', 'Disconnection Policy', 'Version'. Header reads 'Rules' centered in white, with a '< Back' control top-left and an 'X' close control top-right. Body text is white on black. scrollTop=900. Faded 'Win amount is rounded down to two decimal places' at the top, then heading 'Min & Max Multiplier' with both figures fully legible: 'Min multiplier is x1.01' and 'Max multiplier is x32.50'. Heading 'Rounds History' with its paragraph: 'At the top of the game screen you can see the result of the previous game rounds. Colorful outcomes stand for winning rounds, grey - for losing ones.' Heading 'RTP' and its first sentence; the line carrying the actual figure sits in the bottom fade — read it on rules_p4.png instead. The panel fades text out towards the top and bottom edges of the scroll viewport, so lines at the very edge of a frame are semi-transparent — that is a design effect, not a capture artefact.",
      "note_on_ocr": "OCR of the previous, differently-scrolled frame is not carried over: the series was re-shot at a 450 px step and page identity changed."
    },
    {
      "type": "rules",
      "page": 4,
      "file": "rules_p4.png",
      "description": "Left sidebar (identical on every rules frame): seven black rounded-rectangle section-anchor buttons in bold white text with thin white borders — 'How to Play?', 'Game Details', 'RTP', 'Autoplay', 'Settings', 'Disconnection Policy', 'Version'. Header reads 'Rules' centered in white, with a '< Back' control top-left and an 'X' close control top-right. Body text is white on black. scrollTop=1350. The RTP figure line is fully legible here: 'Fast Fielder has RTP 97.5%'. Heading 'Autoplay' in full: the auto-mode paragraph, 'Settings:' with two bullets ('bet amount. This sum will be applied for every auto game', 'number of rounds') and 'You can stop autobetting by clicking on \"Stop Autobet\" button.'. Heading 'Settings' appears at the very bottom, faded. The panel fades text out towards the top and bottom edges of the scroll viewport, so lines at the very edge of a frame are semi-transparent — that is a design effect, not a capture artefact.",
      "note_on_ocr": "OCR of the previous, differently-scrolled frame is not carried over: the series was re-shot at a 450 px step and page identity changed."
    },
    {
      "type": "rules",
      "page": 5,
      "file": "rules_p5.png",
      "description": "Left sidebar (identical on every rules frame): seven black rounded-rectangle section-anchor buttons in bold white text with thin white borders — 'How to Play?', 'Game Details', 'RTP', 'Autoplay', 'Settings', 'Disconnection Policy', 'Version'. Header reads 'Rules' centered in white, with a '< Back' control top-left and an 'X' close control top-right. Body text is white on black. scrollTop=1800. Heading 'Settings' fully legible with its paragraph 'Click the gear icon in the top right corner of the screen to open the settings menu. In Settings you can:' and four bullets: 'change the nickname', 'view bet limits: Minimum bet, Maximum bet, Maximum Profit', 'turn on/off sounds', 'view a list of your recent bets'. Heading 'Disconnection Policy' follows with its opening sentence fading at the bottom. This section was missing entirely from the first capture pass. The panel fades text out towards the top and bottom edges of the scroll viewport, so lines at the very edge of a frame are semi-transparent — that is a design effect, not a capture artefact."
    },
    {
      "type": "rules",
      "page": 6,
      "file": "rules_p6.png",
      "description": "Left sidebar (identical on every rules frame): seven black rounded-rectangle section-anchor buttons in bold white text with thin white borders — 'How to Play?', 'Game Details', 'RTP', 'Autoplay', 'Settings', 'Disconnection Policy', 'Version'. Header reads 'Rules' centered in white, with a '< Back' control top-left and an 'X' close control top-right. Body text is white on black. scrollTop=2161 — the bottom (scrollTop stops growing here). 'Disconnection Policy' in full with both bullets about bets placed before and after a disconnection, then heading 'Version' with 'Game version: \"1.0.1\"' and 'RNG version: \"2.0.0\"'. Nothing follows, confirming the end of the document. The panel fades text out towards the top and bottom edges of the scroll viewport, so lines at the very edge of a frame are semi-transparent — that is a design effect, not a capture artefact."
    }
  ],
  "modes": [
    "Manual single-round betting: choose Under N or Over N via the slider, choose stake via the Bet Amount dial, press the matching 'Place bet' button.",
    "Autoplay: configure stake and a fixed round count (10/20/50/100) or unlimited (∞), then start a run on the chosen side (blue 'Start Autoplay' for Under, green for Over); stoppable via a 'Stop Autobet' control per the rules text (not directly captured on a screenshot, but named explicitly in the rules)."
  ],
  "features": {
    "free_spins": false,
    "bonus_buy": false,
    "jackpot": "Not mentioned anywhere in the rules text; not present on any captured screen. No jackpot mechanic in this game.",
    "note": "This is a single-mechanic instant-resolution prediction game; there are no bonus rounds, no free spins, and no purchasable features."
  },
  "accessibility": {
    "colorblind_notes": [
      "The two betting sides are coded blue (Under) vs green (Over) throughout the UI (field wedges, slider track halves, 'Place bet' buttons, Bet Details panel values, Autoplay buttons). However, color is never the ONLY signal: every instance is paired with the text label 'Under N' / 'Over N' (or just 'Under'/'Over' plus the button's fixed left/right position), so a colorblind player can rely on position (Under is always the left-hand control, Over is always the right-hand control) and on the printed word rather than the hue.",
      "The Rounds History strip distinguishes wins (colored/green text) from losses (grey text) per the rules ('Colorful outcomes stand for winning rounds, grey - for losing ones'). This IS a color-only distinction as printed in the rules with no stated secondary cue (no +/- sign, no icon) — flagged as a potential accessibility gap for red-green colorblind users, since a losing grey result and a winning colored result carry no shape/text difference beyond the color itself.",
      "The circular field's blue/green wedge split additionally carries a textured visual difference (blue side has a smooth felt/matting texture, green side has a grass/lawn texture), which gives colorblind users a secondary non-color cue for which wedge is which, on top of the 'Under'/'Over' labels beneath the field."
    ],
    "motor_notes": [
      "All controls (slider chevrons, dial +/-/min/max, Place bet buttons, Autoplay buttons, menu items) are discrete click targets; the slider can also be dragged directly. No timed inputs or precision-drag-only controls were observed — the chevron buttons and dial +/- buttons offer a click-only alternative to dragging.",
      "Two full-size 'Place bet' buttons sit side by side with a small circular Autoplay-launcher icon between them; the buttons are large (roughly a third of the screen width each) with generous vertical padding, reducing mis-click risk."
    ],
    "screen_reader_notes": [
      "All information needed to understand a round's state is rendered as text/numerals on screen (Balance, Win Chance %, Payout $, Multiplier x, slider N value, round history numbers) rather than conveyed only through animation or audio, which is favorable for text-to-speech read-out once elements are properly labeled in markup (labeling itself was not assessed here — this is a canvas/DOM-mixed build per the provider's own platform conventions)."
    ],
    "audio_notes": [
      "A single Sound volume slider exists (Settings overlay) with mute (crossed speaker) and full-volume (speaker with sound waves) icon endpoints; no separate music/effects split was observed. No spoken narration or subtitles were present on any captured screen — outcomes are communicated visually (ball position, balance change, history color) and presumably by a sound effect on win/loss, which was not capturable from static screenshots."
    ],
    "rules_panel_edge_fade": "Scroll fade: inside the Rules panel the first and last visible lines are rendered semi-transparent as the document is scrolled, so text at the edges of the viewport has markedly lower contrast than the middle of the panel. A reader who needs high contrast has to scroll a line into the centre of the panel to read it comfortably."
  },
  "symbols": [],
  "provider_platform_chrome_not_part_of_game": [
    "The 'TURBO UNIVERSE' badge/menu entry, 'My bets' list, and the rank/loyalty-style elements are the provider's shared platform layer across all of its games, not a Fast Fielder-specific feature.",
    "The bottom-of-screen results ticker convention described in the rules ('At the bottom of each Turbo game there is a panel...') is a provider-wide component; on this build it renders as the top-center history pill rather than a bottom panel, but it is still shared UI, not a Fast Fielder-only mechanic.",
    "The bottom-right timestamp on every frame is the demo-wrapper's live clock, ticking every second; it is not part of the game itself and was not used as evidence for any in-game fact."
  ],
  "unreadable_or_uncertain": [
    "Exact bets_per_round behavior (can a player stake BOTH Under and Over in the same round, or is it strictly one side per round?) is not printed as an explicit rule/number. Best available evidence (quoted text framing it as an either/or decision, plus two independently-triggered 'Place bet' / 'Start Autoplay' button pairs) points to exactly one side per round, but this is an inference from phrasing and UI pattern, not a directly stated figure — see round_structure.bets_per_round_assessment above for the full reasoning and citation.",
    "No explicit mathematical formula for converting a chosen win-chance percentage into its multiplier value is printed anywhere in the rules; only the downstream win = bet_amount x multiplier formula is given verbatim. Multiplier values used in this document are all read directly off captured screens/rules text, never derived by us.",
    "Provably-fair verification is not confirmed as present in this build (see provably_fair block above) — left as an open gap rather than asserted true or false.",
    "No jackpot, no bonus round, and no purchasable feature were found anywhere in the rules text or on any captured screen; this is recorded as a confirmed absence (checked via full rules-text read), not an unexamined gap.",
    "Whether the two 'Place bet' buttons can be pressed in immediate succession within the SAME round (e.g. changing your mind before the ball drops) versus each press independently starting/resolving its own round was not testable from static screenshots; the captured round_lost.png and win_screen.png each show a single resolved outcome per screenshot, consistent with an instant, non-interruptible resolution once 'Place bet' is pressed, but this was not exhaustively verified by rapid double-clicking.",
    {
      "resolved_gap": "Settings section of the rules booklet",
      "note": "Originally reported as illegible: the capture step (700 px) exceeded the scroller viewport (600 px), so the section fell into the gap between two frames and its remnants sat in the panel's edge fade-out. The rules series was re-shot with a 450 px step (150 px overlap); the section is now fully legible on rules_p5.png: 'Click the gear icon in the top right corner of the screen to open the settings menu. In Settings you can: change the nickname; view bet limits: Minimum bet, Maximum bet, Maximum Profit; turn on/off sounds; view a list of your recent bets.'"
    }
  ],
  "sources_used": [
    "manifest.json capture notes for this slot (screenshot list, cross-checked balances/frame order)",
    "Direct visual inspection of all 12 captured frames (preview, base_game x2, round_lost, win_screen, rules_p1-6, info, settings, autoplay)",
    "Verbatim DOM text dump of the Rules panel (all four pages, all seven sections, read to completion)",
    "Provider game-page snapshot text (sources[].page_url) for the RTP cross-check only"
  ]
}

API documentation for this slot

Ready-to-run request examples in curl, Python, JavaScript & PHP — plus the full structured-data field reference for this exact slot, on GitHub.