1 · Authority state
The website asks the CCM Authority service for the current Immersive Roulette lane state and up to 1,000 history rows for the active run.
Data methodology and provenance
How CCM records and checks Immersive Roulette results
This page defines what CCM means by a verified public result, what the current history window covers, how duplicate and reconnect cases are handled, and what the site does when it cannot confirm the source state.
What “verified” means here
Accepted by CCM’s public result checks — not a claim of independent certification.
The website reads result history already accepted by the CCM Authority service. It then applies a narrow public contract before displaying a number. “Verified” on this site means the row passed those identity, source, run and value checks. It does not mean CCM independently filmed the wheel or certified the casino provider.
Public history is currently limited to the active Immersive Roulette run and up to 1,000 accepted results. It is a retained live-history window, not a claim of complete long-term archival coverage.
Public data flow
From source state to the result you can inspect.
2 · Public contract
Rows are filtered by game, approved reader source, run identity, result value and duplicate identity before they enter the public snapshot.
3 · Browser view
The accepted snapshot is rendered with a source state, timestamp coverage, history windows and descriptive statistics. Live revisions must continue the same run and sequence.
Data-quality rules
What has to be true before a result is shown.
Game and source
A history row must identify Immersive Roulette, an approved reader source, a current run/session identifier and a roulette number from 0 to 36 before the website will accept it.
Duplicate handling
Rows are deduplicated by result identity/signature, not by winning number. Two consecutive spins can therefore both be 17 when their result identities are different.
Run boundaries
The public history is limited to the active run. Rows from another run are not mixed into the current result window.
Timestamps
CCM records how many retained rows contain parseable timestamps and exposes the earliest retained timestamp when available. The latest accepted result time is shown in UTC.
Live sequencing
A live revision must continue the current sequence. If the sequence or run no longer lines up, the website requests a fresh history snapshot instead of guessing what was missed.
Unavailable data
When the source is offline, stale, waiting or fails validation, the interface reports that state. It does not insert example numbers or generated spins.
Coverage
The live page reports retained history, not an unlimited archive.
The public snapshot is scoped to the current run and capped at 1,000 accepted results. When timestamps are parseable, CCM can show the earliest retained timestamp and how many retained rows carry timestamp evidence. Those values describe the current snapshot only.
Result identity
Identical numbers are not treated as duplicate spins.
A result can carry its own signature. Where that is unavailable in a history row, CCM derives an identity from the run, round/spin identifiers, timestamp and number. Duplicate identities are removed inside the current history snapshot; duplicate winning numbers are not.
Reconnects and corrections
The site reconciles rather than filling gaps.
During live updates, CCM expects the next sequence number for the current run. A run change or sequence discontinuity triggers a fresh snapshot request. The refreshed Authority history becomes the public view; CCM does not invent an inferred result to preserve continuity.
Statistical boundary
Observed minus expected is descriptive, not predictive.
Frequency, gaps, streaks, colour, parity and wheel-sector summaries are calculated from the selected recorded window. Comparing an observed count with the theoretical 1/37 expectation describes sample variation; it does not make the next independent result due or more likely.
Dataset status
The current public history is not advertised as a downloadable research dataset.
CCM does not currently claim a complete archival dataset or publish Dataset/DataDownload markup for this live-history window. Any future public dataset would need its own coverage dates, fields, provenance, licence and distribution terms before CCM describes it that way.
Methodology scope
This specification describes the public website contract visible in the current CCM source. It does not document upstream casino systems outside CCM’s codebase or imply affiliation with Evolution. Methodology reviewed 8 August 2026.
Questions about a published result? Contact CCM support →Check the data yourself
Open the live history, change the sample and inspect the recorded numbers.
The Results page exposes the current source state, retained-history coverage, selectable windows and descriptive statistics in the same public view.