Average swap size per trading terminal: who carries the biggest tickets
A day's routed volume divided by that day's swap count, per trading terminal, across every chain or one at a time. Separates the terminals carrying large tickets from the ones carrying many small ones.
TL;DR. As of , Maestro leads avg swap size at $97.94 (24h) across 8 ranked terminals. Source: OpenChainBench, https://openchainbench.com/benchmarks/terminal-avg-trade-size.
Read this carefully
Average swap size is one complete UTC day's routed volume divided by that day's swap count, on the chain the tab names or across all of them. From the public tehcscreener API, which is Allium-backed. Both figures include bot and MEV activity. A mean, not a median, so a handful of large tickets moves it and this is not the typical trade. Larger is not better in any product sense; it describes who the terminal serves.
Average swap size tells you who a trading terminal serves without asking anyone. A terminal whose average ticket is ninety dollars is carrying different flow from one averaging thirty-eight, even when both route comparable volume, and the difference shows up in what they can charge and who they keep. This page divides each terminal's routed volume on the latest complete day by the number of swaps it took to get there. It is a mean, so read it alongside volume rather than instead of it.
Methodology
The harness reads one day per terminal from the tehcscreener /bots/{bot} endpoint, takes the Solana series, and publishes volume divided by transactions as terminal_avg_trade_usd. Numerator and denominator are the same row of the same day, so the ratio cannot mix two periods. Three names left this cohort when the source changed on 2026-10-07. Padre, Phantom and Bloom are not covered by the current source, and a row that cannot be measured is removed rather than left to read as zero. pump.fun joined it, because a figure built on fee-wallet attribution could not see a terminal that charges no fee.
- Source: the public API of tehcscreener (tehcscreener.com), served at tehcscreener.com/api, Allium-backed, no key, synced once a day. The harness reads /bots over the full history for the roster and /bots/{bot} for each terminal's per-chain daily series, and publishes one day: the latest the source names.
- The ratio: that day's routed volume in USD divided by that day's swap transaction count, both read from the same row of the same series. A terminal whose day carries volume but no transaction count, or the reverse, publishes nothing rather than a ratio built on a half-loaded day.
- A mean, not a median: the source publishes daily totals, not a trade-size distribution, so a small number of large tickets moves this figure. It describes the mix of flow a terminal carries, and it is not the size of a typical trade on it.
- Cohort changes on 2026-10-07: Padre, Phantom and Bloom are not covered by the current source and were removed rather than published as zero. pump.fun was added, having been invisible to fee-wallet attribution because it charges no terminal fee.
- Latest complete day, not a rolling 24 hours: the source publishes daily and its latest day is normally yesterday. A terminal with no activity on that day carries no figure and reads unresponsive rather than having its last live day carried forward. BasedBot is the live case, with volume on Robinhood Chain and almost none on Solana.
- Stale source: a day more than 3 whole days behind, or a terminal the source stops returning, has its gauges deleted and reads unresponsive. An old figure is never republished as current, because these gauges are scraped every 60 seconds and read through a 24h window, which would average a frozen figure in as though it had just been measured.
- Two freshness layers, because they fail differently: terminal_activity_last_success_unix says the harness is still running, and terminal_activity_health says this particular terminal and chain published a day inside the window. A harness that runs while its source freezes trips the second, not the first.
- Not scored here: execution quality. A large average ticket says nothing about slippage or fees on that ticket, which benches 268 and 279 measure directly.
Results: 8 terminals ranked by Avg swap size (24h)
| № | Terminals | Value |
|---|---|---|
| 1 | MaestroTelegram bot, multi-chain | $97.94 |
| 2 | FomoCross-chain terminal, gas sponsored | $52.35 |
| 3 | GMGNMulti-chain terminal, widest chain reach | $42.62 |
| 4 | TrojanTelegram-native bot, Solana only | $38.69 |
| 5 | TerminalTrading terminal, heaviest wallets | $37.83 |
| 6 | PhotonWeb terminal, Solana only | $31.44 |
| 7 | AxiomSolana-first trading terminal | $30.13 |
| 8 | pump.funLaunchpad's own trading app | $24.42 |
Frequently asked
Is a larger average swap better?
Not in any product sense. It describes who the terminal serves: larger tickets usually mean more professional or automated flow, smaller ones a broader retail base. Read it next to volume and wallet count rather than as a ranking of quality.
Is this the typical trade size?
No. It is a day's volume divided by a day's swap count, so it is a mean over totals. The source publishes daily aggregates rather than a trade-size distribution, so no median is available and a handful of large tickets pulls the figure up.
Why did Padre, Phantom and Bloom disappear?
The source behind this bench changed on 2026-10-07 and does not cover those three. They were removed rather than left in the table reading zero, because a zero would rank them last on a figure nobody measured.
Does this include bot activity?
Yes, every swap the source attributes to the terminal, including automated and MEV flow. A terminal serving mostly bots will usually show a smaller average ticket and a much higher swap count than wallet count; bench 232 publishes that ratio.
Source code github.com/ChainBench/OpenChainBench/tree/dev/harnesses/terminal-activity