Stephen Thompson
The tape in one line
the strongest measured read on file — receipts attached
40% of Thompson's output comes in bursts — strikes less than 1 second apart. That's 3.0× what his own pace would produce by chance.
Watch the Film Study▾
tap a time — replays in-page, slowed · times index the registered upload
standup-scoped, in-round hand-log events (single annotator; ~11–15% estimated strike undercount — every level is a floor)
burst = inter-strike interval < 1.0s
lift = observed burst share ÷ a null that keeps this fighter's event COUNT but redistributes onsets uniformly over his active in-round time
engine provenance ▸
Signature tendencies
the strongest measured patterns in his verified tape — nothing editorial, receipts on every line
Output by round
pooled pace — read the trend, not single-round precision
Thompson's pace holds steady: 3.8 strikes a minute in round 1, 4.2 in round 5.
n = 110 strikes across 5 rounds
When he gets hit · bursts
what he does when he gets hit, and how his output clusters — each measured against what his own pace would produce by chance
When strikes come at Thompson, he fires back within 2 seconds 26% of the time. That's 2.2× what his own pace would produce by chance. He usually answers with a rear punch (55% of his responses).
Watch the Film Study▾
tap a time — replays in-page, slowed · times index the registered upload
standup-scoped, in-round hand-log events (single annotator; ~11–15% estimated strike undercount — every level is a floor)
response = this fighter's next strike within 2.0s of the opponent's strike (two-sided stream, single-opponent context)
lift = observed rate ÷ a circular-shift null that keeps this fighter's own pace and burst structure but scrambles timing vs the opponent
engine provenance ▸
Output by round — pooled
Thompson's pace holds steady: 3.8 strikes a minute in round 1, 4.2 in round 5.
n = 110 strikes across 5 rounds
Punches make up 69% of what Thompson throws; the other 31% is kicks and everything else.
Watch the Film Study▾
tap a time — replays in-page, slowed · times index the registered upload
standup-scoped, in-round hand-log events (single annotator; ~11–15% estimated strike undercount — every level is a floor)
engine provenance ▸
Thompson throws 34% of his strikes from the lead side. His kicks come off the lead leg 21% of the time.
Watch the Film Study▾
tap a time — replays in-page, slowed · times index the registered upload
standup-scoped, in-round hand-log events (single annotator; ~11–15% estimated strike undercount — every level is a floor)
engine provenance ▸
Thompson's most-thrown strike is the cross — 35% of everything he throws.
Watch the Film Study▾
tap a time — replays in-page, slowed · times index the registered upload
standup-scoped, in-round hand-log events (single annotator; ~11–15% estimated strike undercount — every level is a floor)
engine provenance ▸
Thompson's pace holds steady: 3.8 strikes a minute in round 1, 4.2 in round 5.
Watch the Film Study▾
tap a time — replays in-page, slowed · times index the registered upload
standup-scoped, in-round hand-log events (single annotator; ~11–15% estimated strike undercount — every level is a floor)
per-round counts sit on a Poisson floor of roughly ±18–25% — read trends, not single-round precision
engine provenance ▸
Computed from a human sweep (no hand-log). Sides are physical left / right — stance unavailable, not lead / rear; a per-fight stance asset would unlock lead/rear.
What follows what
each row shows what he throws next after that strike — deeper red means it happens more often; click a row for the film. rows without enough tape stay visible with their reasons — an honest “not enough data” beats a confident guess
Sequences
consecutive strikes with every gap inside the fixed window — ranked by frequency
Thompson's go-to 2-strike combination is cross → jab — he threw it 7 times, 26% of his 2-strike sequences.
Watch the Film Study▾
tap a time — replays in-page, slowed · times index the registered upload
only 9 3-strike sequences on file — 25 needed
unlock: pooling more labeled fights unlocks this
When he gets hit
how often Stephen Thompson fires back within 2 seconds of eating a strike. The “vs chance” number compares that to what his own pace would produce at random — so it measures deliberate answering, not just busyness. This is about his offense, not how open he is to being hit.
When strikes come at Thompson, he fires back within 2 seconds 26% of the time. That's 2.2× what his own pace would produce by chance. He usually answers with a rear punch (55% of his responses).
Watch the Film Study▾
tap a time — replays in-page, slowed · times index the registered upload
standup-scoped, in-round hand-log events (single annotator; ~11–15% estimated strike undercount — every level is a floor)
response = this fighter's next strike within 2.0s of the opponent's strike (two-sided stream, single-opponent context)
lift = observed rate ÷ a circular-shift null that keeps this fighter's own pace and burst structure but scrambles timing vs the opponent
engine provenance ▸
⟶ Measured reads
the strongest conditional signals on file — receipts attached, nothing editorial
pre-registered gate: n ≥ 25 for shares/conditionals. Rows below the gate stay visible with their reasons — an honest "not enough tape" beats a confident guess.
guard telemetry coverage too thin under the frozen validity rules for this fighter
unlock: a defense-telemetry upgrade is pre-registered — these cells re-grade automatically after the next data pass
110 human-verified strikes (swept) in this fight — 76 punches, 34 kicks.
Watch the Film Study▾
tap a time — replays in-page, slowed · times index the registered upload
standup-scoped, in-round hand-log events (single annotator; ~11–15% estimated strike undercount — every level is a floor)
no round/segment scoping available for this fight — raw fight-window counts only
engine provenance ▸
Verified verdict profile
Operator verdict-ledger evidence, kept separate from temporal tendencies. Complete reviews may support totals and gated rates; partial reviews remain labeled samples; reviews below the coverage floor expose only their withholding reason.
The three frozen verdict gates
- Per-fight mix shares require n ≥ 25 reviewed real attempts; below it, counts only.
- Complete-fight pooled mix shares and own rates require n ≥ 25 real attempts.
- Defense clean-absorb rates require a complete review and n ≥ 25 opponent real attempts.
- Partial reviews are non-random samples: counts and eligible sample mixes are not fight totals or accuracy.
- Physical side means left/right, not lead/rear stance. Jab/cross for swept strikes is stance-INFERRED from pose: a windowed ankle-vote at the strike instant when decisive (94.3% vs hand-log truth), else the fight-level lead; strikes where both abstain stay "straight" rather than guess.
- A single reviewer produced these verdicts; unresolved attribution/validity verdicts are a floor on missingness.
Coverage & provenance
adjudication_only
Not measurable from broadcast
the single-feed footage can’t support these — they are not a locked upgrade, they simply aren’t recoverable. Saying so is the product.
Landed / grazed / missed
outcome carries ~no machine signal at this capture and is unreliable even by eye from a single broadcast feed
Fine punch subtype (jab / cross / hook)
capped by 72% annotator self-agreement and the single-feed capture wall
Clinch & ground interior
the corpus is standup-scoped — a single broadcast feed can't resolve grappling exchanges
Feint intent
intent-without-contact is not recoverable from broadcast video
Known limits
- single-annotator ground truth; measured undercount ~8.8% on the deepest-swept fight — global estimate 11–15%; every count is a floor, not an exaggeration
- tendency numbers are standup-scoped and in-round; clinch/ground exchanges are not measured
- stance (lead/rear) is a per-fight constant from a pose asset; a mid-fight stance switch would mislabel lead/rear symmetrically
- per-round counts sit on a Poisson floor of roughly ±18–25%; product language is trends and conditionals, never single-round precision
Every fight on this fighter's file — the event, the result, and how deep the verified data goes.
Want more of their fights processed? Start a pack or request a fight.