Use Contract Statistics and side statistics

Summarize one explicitly filtered print set

Contract Statistics reports selected call/put premium, contracts, trade counts, sentiment, ratios, trade types and largest prints. Contract Side Statistics reorganizes activity by inferred aggressor. Use these tools to describe the admitted selection rather than claiming a universal market total. The same symbol can produce different summaries when session, right, premium threshold or expiration filters differ.

Reconcile the summary step by step

A stable small selection is easier to audit than a market-wide changing total.

1. Open Contract Statistics in Map → Statistics or Add Tool.
2. Set symbols, session, date and relevant flow filters.
3. Choose the available measurement and inspect call/put totals.
4. Read the put/call ratio's measurement basis.
5. Compare side statistics and the largest-print list.
6. Use the raw tape for a specific constituent rather than inferring it from a summary tile.

Counts and ratios have denominators

Premium weights by executed option value, volume counts contracts and trade count counts admitted execution records under the tool's grouping. A premium put/call ratio can differ from a volume ratio because prices and sizes differ. A zero or unavailable denominator should not become an ordinary finite ratio. Unknown/midpoint categories and selected classification rules affect directional summaries, so keep their inclusion explicit when comparing side percentages.

Worked example: premium ratio differs from volume ratio

Imagine fewer put contracts trade, but their executed prices are much higher than the selected calls. The put/call volume ratio can be below one while the premium ratio is above one. That is consistent. Next add a minimum-premium filter: it can remove many smaller prints and change both denominators. Reconcile the selected totals after each change rather than expecting a ratio to remain fixed while its population changes.

Troubleshoot totals that do not match screenshots

Compare observation times and filters first. A live total can advance between screenshots, while repaired history can revise older totals. Check whether one view uses consolidated groups and another raw prints. Read partial coverage before treating a total as a complete session. A useful report names the exact tile or ratio, measurement, filters and timestamp. Include the side breakdown so support can distinguish a denominator issue from missing inputs.

Align filters, measurements and coverage

Premium, contract volume and trade count measure different things. Ten contracts at a high option price can contribute more premium than many contracts at a low price. Gross premium, signed net premium, call-minus-put drift and an individual time bucket are also different aggregates. Before reconciling tools, match the symbol family, exact roots where relevant, trading date, session, expirations, call/put choice, size and premium thresholds, aggressor filters and any trade-type selection.

A live stream can begin after the session started. Its current rows may be fresh while an earlier prefix is missing. Historical repair can add eligible prints and recompute older totals without representing new live trades. Empty filtered results mean no admitted matching rows, not necessarily no market activity. Read the reported source times, observed bounds and partial-coverage state. For an apparent mismatch, reproduce it with broad filters first, then add one filter at a time and compare the same measurement over the same time interval.

Use largest prints and side buckets as cross-checks

A headline total is easiest to understand when you inspect both its composition and an individual large contributor. Start with the largest-print list, record one exact execution, and compare it with the raw tape under matching filters. Then inspect the side distribution. A single expensive print can dominate premium while contributing little trade count, so a concentrated premium summary need not imply broadly distributed activity. Distinguish the number of prints from the number of contracts and from the number of grouped rows.

For a ratio audit, write the numerator and denominator explicitly. Compare them before and after one filter change. If a denominator becomes zero or unavailable, the ratio's presentation should reflect that state rather than a normal finite value. A live screenshot taken several seconds later can legitimately have a different total, so use source/cutoff information for comparisons. When sending support a ratio issue, include both components, measurement, session and filters; a single rounded headline cannot reveal whether the discrepancy comes from weighting, scope, classification or incomplete capture.