Stats
Real players
Production accounts created since launch · bots and pre-launch accounts excluded
All player statistics
Who and what counts
This section uses production game records, independently of the traffic filters. The cohort starts with the first verified public release on 12 October 2026 at 18:24:31 UTC. Every account in the bot registry is excluded, including disabled AWS bots. Earlier accounts and known audit accounts using @example.test are excluded.
Accounts created includes guest profiles; registered and guest counts show their current account type. A guest who signs up keeps their original creation date, so these are not historical signup events. Active players means accounts last seen in the selected period. One person can have multiple guest profiles. Unmarked owner visits or browser tests can still appear here.
Games played have at least two saved plies and a saved move or non-abort completion in the selected period. Each game counts once, including games against bots when a qualifying player takes part. Completed games have at least two plies and finished in the period, excluding aborts. Games created also includes untouched starts; cancelled / aborted games are separate. Online includes rated, arcade and friend games; local means pass and play. Puzzle counts use training sessions, including practice and retries; solves are recorded in the period they finish.
Since-launch totals cover retained records. Deleted accounts and expired guest profiles are absent, so historical account and activity totals can fall after cleanup. This is a count of qualifying accounts and their activity, not independently verified people.
What visitors do
Page order, clicks and active time · visits started in the selected period
Loading…
Landing section
First section explored
Last section seen
What they click
Where they go next
Time by section & scroll depth
Start-game path & visit details
Sources
Devices
How visit tracking works
New visitors means the first measured visit from a browser in the retained history. New players means visits linked to a non-bot account created after production launched; it includes that account’s returning visits. Anonymous browsers are separate from identified players. Cleared cookies and different devices can count as new browsers. Known automation, bots and pre-launch player accounts are excluded; unmarked tests can remain.
First section explored is the first different section after landing; a visit that stays on its landing section keeps that section. Last section seen includes visits still in progress. Section names replace raw URLs and private identifiers. Clicks use fixed categories, with unlabelled controls grouped as Other button. No typed text, passwords, form values, chat text, game positions or session replays are collected.
Active time counts only a visible, focused page, stopping 60 seconds after the last interaction. It differs from the measured visit span, which can include idle gaps. Updates are batched every 15 seconds and attempted on exit, so abrupt closes and offline visits can lose final activity. Visits are per tab and restart after 30 minutes of inactivity or four hours. Scroll depth is the furthest document position in 25% bands; inner scroll panels are not measured.
The start-game path counts visits with a Start game click followed by a game-screen visit, not confirmed completed games. Engaged visits have at least 10 seconds of active time, a click or multiple page views. These are browser-supplied interaction signals; the Real players panel uses saved game records for actual play and completions.
Collection begins with this feature and cannot reconstruct earlier behavior. DNT, GPC and disabled Usage measurement prevent collection. Records expire after 90 days; deleting an account or expiring a guest removes its linked visits. Only aggregate results are public.
Where players come from
Loading…Campaigns & placements
How attribution works
Visits are visible browser arrivals, grouped into 30-minute sessions. Known automation is excluded; browsers are not verified people. Link requests include previews and repeat requests and are shown separately.
Played means at least two saved plies; Finished excludes aborted games. Player milestones are credited once to their first recorded source, using the players first attributed in the selected period. Signups include guest upgrades. Returned means a later measured session at least 24 hours after first arrival. Existing accounts can enter this measured cohort. Later direct visits preserve the last tagged source.
A shared bio link identifies a platform, not the video that prompted the visit. Typed homepage visits and missing referrers appear as Direct / unknown. Reports start when tracking is enabled; prior traffic cannot be reconstructed. Browser identifiers expire after 30 days and measurement records after 90 days. The traffic-scope and client-category controls below do not change this player report.
Activity
What’s happening
Where from
Responses
Explore details
Client types
All activities
Countries & clients
All responses
API routes & files
More statistics
HTML loads
Estimated visits
Requests
Page loads and visits include bots and tests.
Countries
Devices
Browsers
How traffic numbers work
Browser traffic is not a confirmed human count. Automation includes headless browsers and scripts. Crawlers includes verified services and unverified crawler claims; expand Client types to separate them.
Countries locate connections, not people. Referrers and unique humans aren’t available in the Cloudflare traffic dataset. Reads can be preloads or refreshes; writes aren’t necessarily completed games or puzzles. Game bots counts runner/operator connections, not moves.
The 13 October production audit alone recorded 12,921 browser requests. Tests without an automation signature remain in Browsers.
Cloudflare data can be sampled. Percentages use classified requests. Data refreshes every 20 seconds, with caching and processing delay. No IPs, player IDs or raw user agents are published.
Posts by account
Your latest content, at a glance.