Definition
What this measures
Move-aware solves show how turning rate and move count vary across real solve-time bands.
SupaKewber first-party research
Typical TPS by solve-time bracket
Move-aware solves show how turning rate and move count vary across real solve-time bands.
SUPAKEWBER PRACTICE DATA
Research question
How many turns per second do speedcubers average?
The live dataset will publish a quantified answer automatically after it reaches at least 20 distinct users and 100 eligible observations.
Published results
Aggregate benchmark table
Every displayed cell has passed the public sample threshold. Empty tables are a deliberate “not enough evidence yet,” never a fabricated estimate.
Loading current publication state…
Methodology
How it is calculated
TPS is reported moves divided by execution seconds for valid smart-cube solves with plausible move counts.
Inclusion rules
What enters the sample
- Eligible SupaKewber observations with valid measurement fields.
- Only aggregate cells above the stated privacy and stability threshold.
Exclusion rules
What is removed
- Deleted, invalid or structurally inconsistent records.
- Small cells that could be misleading or identify a narrow group.
Interpretation limit
What this dataset cannot prove
Protocols can differ in how rotations and slice moves are reported, so TPS is most useful within the documented SupaKewber collection method.
SupaKewber data describes people who use this platform; it is not automatically representative of every speedcuber. Definitions and thresholds stay attached to every JSON download so the number cannot be separated from its method.
Source separation
This is practice data, not an official competition result.
SupaKewber records browser practice and platform interactions. Official WCA results appear only on separately labeled WCA analysis pages with the required WCA attribution and export date.