Scam

How to Check a Crypto Signal Provider’s Track Record: An Independent Verification Guide

Learn how to check a crypto signal track record independently — without relying on provider screenshots. A step-by-step verification guide with checklist.

Last updated: 2026-07-13 · Reviewed by the editorial team

Key takeaways

Why independent verification matters when checking a crypto signal track record

Checking a crypto signal track record means going beyond what the provider has chosen to show you. When a service publishes a summary table, a screenshot of winning trades, or a highlighted monthly result, they have already made editorial decisions about what to include and what to leave out. A record that a provider has curated is not a track record in any meaningful sense; it is marketing material shaped to look like evidence.

Independent verification shifts the lens from what the provider presents to what actually happened. That distinction matters because the two are frequently very different. A service might publish a headline win rate of 72% while quietly excluding losing trades that were deleted, counting vague entry zones that always look like wins in hindsight, or omitting the exchange fees and slippage that erode real profitability. Independent verification is the process of checking those figures yourself from source material, rather than accepting a polished summary at face value.

The steps that follow are practical and do not require specialist knowledge. They do require a little time and the willingness to ask direct questions of a provider before committing any money.

What to request: the complete raw trade log

The starting point is asking for the full trade log, not a summary. A complete log contains a row for every signal the service has published, including the ones that did not work. Each row should ideally include the trading pair, the date and time the signal was sent, the stated entry price or range, the take-profit targets and which one (if any) was hit, and whether the stop-loss was triggered or the position was closed manually.

If a provider declines to share a full log, citing confidentiality, or if the only evidence available is a curated set of screenshots, that absence itself is informative. A service confident in its actual results has no reason to withhold the raw data. A service with poor underlying results has every incentive to show only a selection.

Screenshots are not a substitute for a raw log. A screenshot captures a single moment and can be edited or selectively taken. It cannot be queried, sorted, or verified against anything external. A spreadsheet or channel archive that can be cross-referenced with a price chart is a meaningfully different type of evidence.

How to recalculate win rate from raw data

Once you have the complete log, calculating the win rate yourself is straightforward. Count the total number of signals, then count the number the provider classifies as wins. Divide wins by total to get the raw percentage.

Two things to examine carefully before accepting that figure. First, how has the provider defined a win? Some services count any partial take-profit as a full win, so a signal that reached TP1 of three targets before stopping out at a loss might still be logged as a winner. If that is the case, the headline win rate overstates how often a subscriber would have profited meaningfully. Ask the provider to clarify their definition, and if you are doing the calculation yourself, apply a consistent standard: a signal is a win only if it closed profitably after accounting for fees.

Second, compare your recalculated win rate with the provider's headline figure. If there is a material difference, ask which trades are missing from the log you received. A legitimate service will be able to account for the discrepancy; a service that cannot or will not is showing you a gap that the raw data cannot explain.

Checking whether fees and slippage are included

A win rate calculated on gross trade outcomes and a win rate calculated net of exchange fees and execution slippage can differ substantially, particularly for high-frequency services or those trading less-liquid altcoins. It is worth asking directly: are these figures gross of fees, or have trading costs been factored in?

For illustrative purposes, if a service publishes a 70% gross win rate on 100 trades, but each trade incurs a round-trip fee of around 0.15% and the average gain per winning trade is only 1%, the net win rate after costs may look considerably worse than the headline. The exact numbers depend on the service's specific trade structure, but the principle holds: fees compound and erode results, and a provider that does not disclose whether their published figures include them is omitting information that changes the picture materially.

Slippage is a related but separate issue. On high-volume signals sent to large audiences, the act of many subscribers entering simultaneously can move the price of less-liquid assets. A signal entry that looks clean on a price chart may not be achievable at the stated price for subscribers who are not first in the queue. Ask whether the provider's stated entries are based on the exact signal price or a realistic average fill.

Verifying timestamps against price chart history

Even a complete log with timestamps is only as reliable as those timestamps. The key question is whether each signal was sent before the market moved in the anticipated direction, or whether the timestamp represents a record created or edited after the move was already visible on the chart.

Cross-referencing is possible for any service that broadcasts through a public or semi-public channel. Platforms that display message history show when individual posts were sent, and third-party archiving tools can capture this independently. For a sample of ten or more trades from the log, locate the signal timestamp and then look at the price chart for that asset at that specific date and time. If the price at the signal timestamp was near the stated entry zone and the move came afterwards, that is consistent with a live signal. If the price had already moved substantially in the stated direction before the signal was sent, something is wrong.

For illustrative purposes, if a log entry shows a BTC/USDT long signal timestamped at 14:23 with an entry zone of 65,000–65,200, but the price chart shows that BTC had already reached 66,500 by 14:20 and the signal entry zone was effectively already past, the timestamp does not reflect a genuine live call. Even a handful of such discrepancies across a sample of trades should prompt serious scepticism about the integrity of the entire log.

Minimum sample size before any result is meaningful

A track record that passes all of the checks above is still only useful if it is large enough to carry statistical weight. A run of 10 perfectly timestamped, independently verified wins might represent genuine skill, or it might be a short sequence that any random-outcome signal service would produce occasionally. At small sample sizes, luck and skill look identical from the outside.

As a practical floor, 30 or more live, consecutive trades is the minimum number before any win-rate calculation starts to narrow the range of what chance alone could explain. More is better: 100 trades across at least a few months, spanning different market conditions (rising, falling, and sideways), gives a much clearer picture than a cherry-picked three-week run during a one-directional market. This minimum sample size matters because providers can control the period their published results cover. A service that shows only its best 20-trade sequence from a 12-month operation is not providing a reliable track record, even if every individual trade in that sequence is verified.

A five-step independent verification checklist

These five steps summarise the process before subscribing to any paid service.

Risk note: This guide is educational and is not financial advice. Crypto trading is high-risk. Never trade with money you cannot afford to lose, use position sizing, and remember that past performance does not guarantee future results.

FAQ

Why can't I just rely on a provider's own screenshots to check their track record?

Screenshots can be selected, edited, or cropped to show only winning trades. They cannot be cross-referenced with external data and do not represent a complete record. A full raw trade log with timestamps is the only format that can be independently verified against price chart history.

What is the difference between a gross win rate and a net win rate?

A gross win rate counts trade outcomes without deducting exchange fees and execution slippage. A net win rate deducts those costs from each trade before deciding whether it was a win. For frequent trading or illiquid assets, the two figures can differ substantially, so always ask which basis a provider is using when they publish performance numbers.

How many trades do I need to verify before I can trust a track record?

At least 30 live, consecutive trades is a practical minimum, and that figure should span different market conditions — trending and range-bound, rising and falling. Fewer trades are too small a sample to separate skill from chance, even if every individual trade in the sample checks out.

What does it mean if a signal provider won't share their full trade log?

A provider who declines to share a complete trade history, citing confidentiality or any other reason, is asking you to evaluate their service without evidence. Legitimate services with genuine track records have no reason to withhold the raw data. Treat the refusal itself as a significant negative signal.

Can entry zone signals always be verified against a price chart?

When a signal specifies a wide entry zone rather than a single price, it becomes harder to verify whether the entry was achievable at the stated price. The wider the zone, the easier it is for the zone to appear correct in hindsight. A tighter entry zone is a sign of more specific analysis; a very wide zone that covers much of the day's price range is a sign that verification will be difficult and the stated win may not reflect real-world executability.