← THE CHARTSPOD LEDGEROPEN TERMINAL →
AGGR.TRADE GUIDE · READING

How to Read Aggr.trade: Large Trades, Side Filters and Rolling Volume

Aggr.trade shows aggregated trades from many venues in real time. Reading it well means knowing what a row represents, which side it is, and what the rolling counters are summing.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

Read Aggr.trade in three layers. Each row in the trade feed is an aggregated print: fills sharing a timestamp, market and side grouped into one, shown in buy or sell colour and highlighted when it passes your size thresholds. The counters and stats are rolling sums over set periods (for example buy versus sell volume), updated about once per second. The chart panes plot what the connected exchanges send. Large trades matter most when you know the venue, the threshold that highlighted them and whether they printed into support or resistance.

What one row means

The README says Aggr groups trades by time, market and side and can merge trades with the same timestamp to filter noise. Since version 3.1.3 it uses Binance's aggTrade streams rather than raw trades, and version 3.6.2 shows a weighted average price in the trade feed rather than the last price.

Anatomy of an aggregated trade rowAnatomy of an aggregated trade row: Side colour — buy or sell aggressor; Size — summed fills, after aggregation; Price — weighted average of the fills; Venue / market — where it printed; Threshold tier — colour, audio, highlighting.Side colourbuy or sell aggressorSizesummed fills, after aggregationPriceweighted average of the fillsVenue / marketwhere it printedThreshold tiercolour, audio, highlighting
Every field depends on aggregation and threshold settings. Original ChartsPod editorial graphic.

Large trades and thresholds

Thresholds decide which prints are highlighted and how they sound. The changelog records multiple thresholds per trade type (3.0.7), an all-in-one threshold slider (3.0.9) and an exchange threshold formula of threshold × multiplier (2.5.6). A "large trade" is therefore defined by you, per market.

What you seeAsk
A highlighted buyWhich threshold tier, and on which venue?
Many mid-size sellsAre they one order split, or many traders?
A large print with no follow-throughDid it hit resting liquidity? Check the book.

Tuning thresholds is covered in Aggr.trade Bitcoin Settings: Reduce Noise Without Hiding Relevant Trades and Aggr.trade Audio Thresholds: Match Alerts to Trade Size and Market.

Scenario: a burst of highlighted sells

Illustrative: during a quiet hour, the tape suddenly highlights five large sells within twenty seconds, all on one venue's perpetual. The rolling sell counter for 1 minute jumps while the buy counter barely moves. Price drops a few ticks and stops.

Reading it: the aggression was real and one-sided, but price did not travel far. That points to resting bids absorbing the selling. The tape alone cannot confirm that; a heatmap or order book at the same time would show whether bids were filled and replenished. If the same sells had hit spot and perpetual on several venues, the reading would shift toward broad risk-off rather than one participant.

What to record: venue and market of the prints, their aggregated size and threshold tier, time window, and what price did over the next few minutes. Patterns become visible only across many such notes.

Rolling volume and counters

Counters and stats are rolling sums, updated after 1 second to reduce lag (2.5.1), and markets panes can reset counts every 1m, 15m, 30m, 1h or 4h (3.1.3). A rising buy counter over 15 minutes is a summary of recent aggression, not a forecast.

Reading a burst of activityReading a burst of activity. Steps: 1. Feed — Spot highlighted prints; 2. Counters — Buy vs sell over the window; 3. Venue — Spot or perp, which exchange; 4. Level — Where on the chart; 5. Context — Book, funding, OI elsewhere1FeedSpot highlightedprints2CountersBuy vs sell overthe window3VenueSpot or perp, whichexchange4LevelWhere on the chart5ContextBook, funding, OIelsewhere
The tape starts the question; context answers it. Original ChartsPod editorial graphic.

Check a highlighted print's level against the order book and funding.

Open the live chart in ChartsPod

Read each row as an aggregated, threshold-filtered print, and read counters as rolling summaries over a window you chose.

Compare tools: Aggr.trade vs ChartsPod: Live Tape and Full Research Workflows.

Put How to Read Aggr.trade next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

Questions readers ask

Is each Aggr row one trade?

Not necessarily. Rows can aggregate fills sharing timestamp, market and side.

What price does Aggr show for an aggregated row?

Since version 3.6.2, the trade feed shows a weighted average price instead of the last price.

How often do Aggr counters update?

The changelog says counters and stats update after 1 second to reduce lag.

Sources and methodology

Aggr.trade behaviour is taken from its public README and CHANGELOG (version numbers cited) as read on 17 October 2026; the interface changes over time, so confirm settings in your build. Numbers in examples are illustrative.

  1. Aggr repository README — exchanges, aggregation, audio, history via aggr-server.
  2. Aggr changelog — workspaces, audio thresholds, liquidations, alerts.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.