> For the complete documentation index, see [llms.txt](https://docs.itradingbot.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itradingbot.net/en/signals-and-strategy-conditions/filters/filter-by-trade-count-2-0.md).

# Filter by trade count 2.0

<mark style="color:$tint;">This filter is available to Binance. It compares the number of market transactions of a single bar to the average of previous bars multiplied by the coefficient.</mark>

### Add a filter to the task

<mark style="color:$tint;">Open up the</mark> [<mark style="color:$tint;">Binance robot</mark>](/en/binance-robot/binance-first-task-and-launch.md) <mark style="color:$tint;">task. In the filter block, select Transaction number 2.0.</mark>

<mark style="color:$tint;">Field Active is missing. Set the filter for the pair the task is going to work with.</mark>

### Set the calculation

* <mark style="color:$tint;">**The TF**</mark> <mark style="color:$tint;"></mark><mark style="color:$tint;">sets the time frame for the calculation. The initial value is 1 minute.</mark>
* <mark style="color:$tint;">**Calculation**</mark> <mark style="color:$tint;"></mark><mark style="color:$tint;">On closing the bar or On crossing (every second). The first uses closed bars, the second takes into account the current unopened bar. In the new form, the mode P is selected (every second).</mark>
* <mark style="color:$tint;">Period setting the window for the average number of transactions: use the whole number from 2 to 720, starting value 60. The filter may not give permission for period 1.</mark>
* <mark style="color:$tint;">**The coefficient**</mark> <mark style="color:$tint;"></mark><mark style="color:$tint;">is a multiple of the mean, from 0.1 to 500. The new form is 2.</mark>
* <mark style="color:$tint;">**Allow entry if**</mark> <mark style="color:$tint;"></mark><mark style="color:$tint;">Rost is more or Rost is less. By default, Rose more.</mark>

### When the filter allows action

* <mark style="color:$tint;">Growth is more efficient if the number of deals in the bar being checked is significantly higher than the average multiplied by the coefficient.</mark>
* <mark style="color:$tint;">**Growth is less**</mark> <mark style="color:$tint;"></mark><mark style="color:$tint;">permissible if the number of transactions is much lower than this level. With a precise equality, no condition is met.</mark>
* <mark style="color:$tint;">The terms apply to the market trades of a pair, not your trades. When it's done, the filter allows both directions.</mark>

### Determine the meaning of the parameters

<mark style="color:$tint;">For example, the coefficient 2 compares the double average number of transactions. It doesn't mean adding two trades or growing 2%. The calculation mode determines whether a current or already closed bar is used.</mark>

### Set the action when you exit the filter

<mark style="color:$tint;">Field When the filter is out refers to the situation when the task stops passing this condition. The new card has the Cancel Cycles option. The form also includes Sell by market and Sell by market with deviation (if indicated).</mark>

<mark style="color:$tint;">The filter can also affect a task that is already working: the exit from the condition transmits the selected command. Before you save, check the results of the command for your robot in the Binance task description. —</mark> [<mark style="color:$tint;">Binance tasks</mark>](/en/binance-robot/binance-robot-tasks-and-active-trades.md)

### Save and verify the task

<mark style="color:$tint;">Save the filter card, then check the rest of the conditions and parameters. Several filters should allow it to move at the same time. The filtering permission itself does not mean that the order has been sent or executed.</mark>

<mark style="color:$tint;">If the task mode supports the task without a basic signal, the filters can be involved in its start. So the conditions and the action you choose to take when you exit them should be checked before the robot starts.</mark>
