Stats — advanced
Rotation breakdown
Use By rotation to compare Sideout %, Break %, evaluation mix, efficiency, and impact across rotations. Tap a rotation row for player-level detail.
Treat small samples carefully. A strong percentage from only a few rallies is a lead to investigate, not a final conclusion.
Player × rotation
Choose a player to see their efficiency in each on-court position. The larger number is the selected player's value; the value in parentheses is the team baseline for everyone who played that position.
The baseline does not change when you switch players. It is a reference point, not that player's personal average.
Rally analysis
Rally analysis groups attacks by the quality of the pass entering the attack, such as after a perfect pass or after a positive pass. This helps separate transition problems from first-ball offense.
Filter attacks by set quality
Like the blocker filter, the attack conditions include a Set quality filter (the evaluation of the set right before the attack: A set / B set / C set). Attacks after an unchecked set quality drop out, so you can check "efficiency on A sets only" or "who still scores from a C set" in the player, rotation, player × rotation and rally analysis views alike. Rows are counted for the hitter, not the setter. It appears in the attack condition bar of the aggregate stats and under Conditions in match stats.
Sets are recorded on this five-step scale.
| Evaluation | Criteria | Result |
|---|---|---|
| A set | Ideal set. The hitter attacks at full reach and full approach tempo, and can hit any angle | Continue |
| B set | Good set. The hitter can swing, but the height or the available angles are slightly off | Continue |
| C set | Failed set. Too tight to or too far off the net. The hitter cannot swing hard and is forced to tip or play the ball off the block | Continue |
| D set / Returned | The set goes straight over the net, or is so poor that the hitter can only send over a free ball | Continue |
| Error | Double contact, catch (held ball), crossing the center line, a set sent over by mistake, and so on | Point to opponent |
Mapping from the previous names
The previous "Good set / Slightly off / Well off / Overpass / Fault" are shown as A set / B set / C set / D set · Returned / Error. Matches you already recorded do not need to be re-entered.
The filter offers A, B and C sets. D sets, errors and second-ball attacks (below) do not lead to an attack, so they are not options.
While the filter is on, attacks with no evaluated set right before them are left out. Sets are mostly recorded one by one with voice input (Japanese only), so tap-entered matches mostly drop out (when no attack has an evaluated set, the filter is not shown at all).
Second-ball attacks
When the setter attacks the second ball directly (a second-ball attack, or "setter dump"), record it instead of a set — never both for the same touch. There are three evaluations.
| Evaluation | Meaning | Result |
|---|---|---|
| Second-ball kill | The setter attacked the second ball and scored | Point, rally ends |
| Second-ball in play | The setter attacked the second ball, the opponent dug it, and the rally continued | Continue |
| Second-ball error | The second-ball attack was an error or was stuffed, losing the point | Point to opponent, rally ends |
How to record it
- Tap input: select the setter, choose Set, then tap Second-ball attack below the evaluation buttons to switch to the three buttons Kill / In play / Error
- Voice input (Japanese only): say "12番 ツーアタック成功", "12番 ツーアタック継続" or "12番 ツーアタックミス". Short forms such as "ツー成功", "ツー決めた" and "ツー失敗" also work. Leaving out the number assigns the play to the designated setter. "ツーアタック" on its own is recorded as in play
In the stats
- On the Set tab, a Count: Sets / Second-ball attacks toggle appears under the action tabs (in both match stats and the aggregate stats). It applies to the player, rotation, player × rotation (position) and growth views. Sets (A–D, error) and second-ball attacks (kill, in play, error) are counted as separate populations, so neither efficiency dilutes the other
- CSV export writes sets and second-ball attacks as separate sections
- The attack "Set quality" filter has no second-ball option, because no attack follows a second-ball attack
Sets by pass quality
Choose the Set tab in the Rally analysis view to see sets grouped by the quality of the first touch right before them (reception, dig or free ball). Rally analysis shows only the Attack and Set tabs. Above the table is the same fan heatmap as the attack rally analysis (for both attacks and sets, tap i at the top right of the chart to see what each area counts): Rec. A / Rec. B are sets right after a reception, A/B total covers every A/B pass including digs during the rally, and C shows set efficiency after a C pass. Rows are the pass quality (after A/B pass, after C pass, other; the A/B row also shows the reception A / B breakdown), columns are the set evaluation (A–D set, error), and the player is the setter who delivered the set. Tap i (How to read) next to the heading for an explanation.
| Look at | Reading |
|---|---|
| Few A sets after A/B passes | Good passes are not being converted — a basic setting-accuracy issue |
| Many B-or-better sets after C passes | The setter recovers broken passes well; the closer this row's efficiency is to the A/B row, the better |
| Gap between a setter and the team total | Each setter's strengths and weaknesses; also useful for comparing with a backup setter |
- Only your team's sets with an evaluation (A–D, error) are counted. Unevaluated sets are left out
- Second-ball attacks are not sets and are excluded (see the Set tab with Count: Second-ball attacks)
- Efficiency and impact use the set weights from team settings. Sets are mostly recorded one by one with voice input (Japanese only), so tap-only matches will have little data here
- The same table is appended to the CSV export
Attacks by blockers
Attack results by the number of blockers faced (0 / 1 or fewer / about 2 / 3). Blocker counts can only be recorded with voice input (Japanese only), so when there are none the table is replaced by an "Unlock with voice input" note.
Reception attack comparison
In the By player view, the Reception tab adds a Compare by switch at the right of the visible-players row.
- Reception (default): the reception itself — the pass-quality mix and its efficiency.
- Reception attack: the attack immediately after that player's reception. Both the scatter plot and the table switch over.
In reception-attack mode the scatter plot becomes X = reception efficiency/attempt and Y = reception-attack efficiency/attempt. Both axes use the same scale, so a gray dashed Y = X diagonal is drawn as a reference. The target is the upper right: good passes the team converts into points.
A player below the diagonal is not getting much offense out of passes that grade well. There are two ways to improve, and they combine into a higher sideout percentage:
- Move right — pass better. Turn more serves into perfect or positive passes and raise reception efficiency itself.
- Move up — raise the quality of the pass. Even at the same grade, aim for a height and speed the setter can take without moving, and a timing the hitters can approach from.
A player above the diagonal converts better than the pass grade alone suggests; share what is working after the pass with the rest of the team. Tap the i button on the plot for the same explanation with a diagram.
The table switches to attack results, with a leading Rec. column for how many receptions that player took. Tap a row to see who actually hit those attacks.
Reception attacks are counted the same way as on the Reception attack tab: only the first attack right after the reception, excluding free-ball returns. It counts on the receiver's row even when someone else hit it. Opponent receptions are not recorded, so this comparison has no opponent row.
Opponent comparison
Compare your team with the opponent across core metrics. For reliable player-level opponent data, link an Opponent analysis match.
Without a linked analysis match, opponent values are limited to what can be inferred from your own entries.
Shot placement
Link an Course analysis match to visualize attack origin, set location, target, and outcome on court diagrams.
Below the player selector, a Receiver selector narrows the view to the attacks that came right after one player's reception — useful for asking whether the offense goes to different places depending on who passed. Choosing a receiver switches the view to reception attacks only, and clearing it puts both back.
The receiver is only known when a standard match has an analysis match linked to it: the analysis mode records where the reception happened but not who took it, so the app matches each rally to the standard match by set and score to recover the passer. The selector does not appear without that link or when you open the analysis match directly. Linked matches work the same way in the aggregate stats page.
The filter rows from the line mode down to the reception-attack and rotation row fold into a single bar, so the court diagram stays near the top. Tap the bar to open or close it; while closed it summarizes the conditions in effect, for example Attack → target / #6 / Rec. #6 / Front row only. The evaluation filter, shot-type filter, set-location zones, and the totals bar are always visible.
Growth charts
The team Stats page can compare a metric across multiple matches and a selected date range. Use consistent input standards across matches; a change in how actions are graded can look like a performance change.
Customize evaluation weights
Editors and administrators can change the integer weight assigned to each evaluation. Use Reset to defaults to restore the standard ATaMa volley values.
Document custom weights
Changing weights changes the meaning of efficiency and impact. Agree on the scale as a team and avoid changing it during a comparison period.
Export CSV
Use Export CSV to download the current player, rotation, or rally-analysis view. Test matches may disable export. The exported labels follow the selected app language where supported.
Share reports
Supported views can be saved or shared as a PDF or ZIP report. Check the match name, set filter, and selected action before generating the file.