How TraderStat checks signals and explains the evidence
TraderStat uses public-source evidence and separately identified private-channel aggregates to create profiles, comparisons and market context. The process is designed to make the inputs and their limitations visible, not to promise outcomes.
Methodology version 1.3 · Last reviewed: 16 September 2026
Why private signals are shown as aggregate results
TraderStat publishes aggregate results for private channels, not their messages, individual trade instructions, timestamps or access links. This is our publication policy to respect creators' rights, confidentiality and channel access terms. Missing public trade details do not mean that no checking took place.
Why we prioritise structured signals
In our checking workflow, explicit signals are usually simpler and less expensive to evaluate than open-ended forecasts. An instrument, direction, entry, target and stop define a testable scenario; general predictions may require interpretation and modelled assumptions. This makes structured signals a more useful starting point for evaluating a provider's recorded outcomes.
Private channels often provide these structured instructions, but privacy or payment alone does not make a signal clearer, more accurate or more profitable. A missing level or ambiguous sequence still limits what can be checked. We do not promise a fixed verification cost or a profitable subscription.
What readers can and cannot verify
Public-source checks, modelled outcomes and supplied private-channel aggregates are identified separately. Readers can examine published counts and instrument subtotals, but cannot reproduce private-message checks from this website. Source-bot check flags describe that source's process; reconciling an imported aggregate is not an independent recheck of every message or an audit of a subscriber's account. Unknown observation dates remain unknown; the import date is not the trading period.
Compare free and paid evidenceVerification workflow
Directional ratings run from 0 to 100. A value closer to 0 represents a stronger sell bias in the evaluated input; a value closer to 100 a stronger buy bias. A midpoint reflects more mixed or neutral evidence.
Overall Score combines the available component ratings. Users should inspect those components because missing coverage, changing market conditions and conflicting inputs can affect the result.
Not every public claim contains enough information to verify. Public wallets may not represent every account or strategy, and historical performance does not predict future results.
TraderStat describes evidence as available, tracked or verified according to the underlying source. The platform does not provide personalised investment advice.
Media signal performance policy
Use the author's first published Entry, Target and Stop. When Entry is omitted, use the open of the first complete minute after publication, or the next market opening during a scheduled closure. When Stop is omitted, place it at half the distance from Entry to Target in the opposite direction. For Buy targets at least 200% above Entry, an omitted Stop is 50% of Entry so it stays positive. For Entry 50,000 and Target 100,000, the modelled Stop is 25,000.
The first confirmed Target or Stop determines the outcome. Missing prices, invalid levels and unresolved ordering within a minute do not earn a result. The directory Signals count combines Free and Paid in the profile's market. Imported Paid replaces the legacy Paid bucket rather than adding it twice. Average result per signal is the sum of available results divided by that combined count; missing results remain unavailable. A profile's separate Free and Paid summaries show sums of their own outcomes. Imported Paid target-hit rate uses targets / (targets + stops + breakeven); it is not a measure of account returns. Forex uses broker pips, Crypto uses percent. Modelled outcomes are not confirmed account executions and exclude fees, spread, slippage and leverage; their sum is not a portfolio return. Source levels and modelled levels remain separate.
Who maintains the methodology?
The methodology is developed by the TraderStat team under founder Denis Gramovich, a trader and developer with 14 years of trading experience. Developers and traders contribute to the data systems and ongoing review of the product.