# OG Algo Beta Our latest — and so far most beloved — algorithm among users. While the original OG Algo triggers new calls every 20 minutes, OG Algo Beta is different: It’s event-based, not time-based. The core trigger is reaching a specific number of profitable wallets buying a token. That number (X) dynamically adjusts based on current market conditions. This makes OG Beta faster when the market is active — and more selective when it’s not. {% hint style="info" %} OG Algo Beta is available to all ATM Pro users with a 1-month or longer subscription {% endhint %} {% embed url="" %} ### Core Сharacteristics Same as OG Algo: * **Focus:** Mid-cap tokens ($100K – $2M MC) * **Discovery timing:** After first strong on-chain traction, before mass awareness * **Key signal:** Professional Traders’ Activity — entry from historically profitable wallets * **Use case:** Best fit for consistent 2x setups and short-term plays What's new: * **Number of tokens:** around 100 tokens a day (no more 20min timer) * **Winrate:** 50%+ tokens hit 2x without dipping below -50% first * **Catches runners earlier** and more often than the current OG Algo ### Best Use Case OG Algo Beta is best suited for traders who: 1. Want to catch tokens right as smart wallets start buying 2. Prefer faster, event-based signals over fixed time intervals 3. Have higher risk tolerance and want early entry potential 4. Are comfortable reacting quickly with a predefined plan {% hint style="info" %} **Strategy tip:** our recommendation is the same as for OG Algo. Start with 100% trailing take profit, 50% stop loss. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://atm-day.gitbook.io/docs/algorithms/og-algo/og-algo-beta.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.