A signal track record is only credible if every signal goes out before the outcome, with its entry, original stop and exit, and the losing trades stay on the list. Stop changes should be dated, results should be in R (risk units), not just win rate, and nothing should be editable after publishing. Screenshots and winners-only lists are not a track record.
If you've ever paid for signals, or come close, you've probably seen this: a feed full of green screenshots and a "92% win rate" banner. Then you join, and the losses show up in your account but never in the marketing.
This guide gives you a checklist you can run on any signal service in about ten minutes. Then I run it on my published signal record, losers included, so you can see what passing and failing each check looks like. If you're new to signals, start with how daily signals work and come back.
The short answer
A real track record lists every signal, and each one was published before anyone knew how it ended. Each signal shows the entry, the original stop, any dated stop changes, and the exit with a reason. Losing trades stay on the list. Results are shown in R, the amount risked, not only as a win rate. And the list can't be quietly edited later.
Why it matters: one deleted loser can hide the real risk. If a service drops its worst trade every month, the record looks smooth while your account takes the hit.
The 7-point checklist
1. Every signal is listed, including losses
Start by counting. If a service says it sent 200 signals this quarter, you should find 200 rows. SniperMachine makes this point in its verification checklist: the gap between signals sent and signals shown is where filtering hides.
What to look for: a full list, in date order, with losing rows right next to winners.
Red flag: a winners-only feed, or a "best trades" page with no full list behind it.
2. Entry and stop exist before the outcome
A signal without a stop isn't finished. With no stop, a losing trade can stay "open" forever, waiting to recover, and never count against the record. The entry and the stop both need to be on record before price decides the result.
What to look for: an entry price and an original stop on every row, published before the exit.
Red flag: "entry zone" calls with no stop, or stops that only show up after the trade has closed.
3. Stop changes are dated
Moving a stop is normal. But an undated stop move can't be checked, because you can't open the chart and confirm it happened when the service says it did. With a date, you can match the new stop to a specific candle and see whether the move followed the stated rule.
What to look for: the original stop plus every stop move, each with its own date.
Red flag: a single "stop" column that shows only the final stop, with the original level gone.
4. The exit reason is stated
Every closed signal should say why it closed: a stop, a target, or a flip. A flip is when the opposite signal fires and the position reverses. The reason tells you whether the method followed its own rules. Exits with no stated reason are judgment calls, and those are easy to tidy up later.
What to look for: an exit price, an exit date and a reason on every closed row.
Red flag: exits labeled "closed" or "secured profit" with no rule behind them.
5. Results are in R, not just win rate
R is the distance from your entry to your original stop. It's the amount you said you were willing to lose. A trade that loses exactly that much is −1R. A trade that makes twice that is +2R. Win rate alone can mislead. Someone in r/algotradingcrypto describes a 76% win rate with negative expectancy: lots of small wins wiped out by a few big losses. R shows that. Win rate hides it.
What to look for: results stated in R, or enough data (entry, original stop, exit) to work out R yourself.
Red flag: only a win rate, or only percent gains on the winners.
6. Nothing can be edited after publishing
A track record should be append-only. New rows get added, and old rows never change. Each row should carry a visible publish date. Third-party auditors like Verpips build whole methods around this, but you don't need their tools to check the basics. Screenshot a few rows today, come back in two weeks, and compare.
What to look for: a clear statement that published rows are never edited, plus publish dates you can spot-check over time.
Red flag: rows that change, disappear, or get "corrected" without a note.
7. Enough history, including losing streaks
Traders asking how to vet a trader on r/Daytrading often hear 12 months or more, and that's a fair bar. A short record can't show you how a method handles a bad month. I'll be straight about mine: my published list starts Oct 6, 2026. That's enough to show how the record works and what a losing stretch looks like on it. It isn't enough to prove anything about the method over time. Nobody should treat one week as proof of anything.
What to look for: months of history, with at least one rough patch visible.
Red flag: a short history sold as proof, or a "track record" that starts right after a big run of winners.
Worked example: auditing my own record (/record)
Here's the checklist run on my published signal record, pulled on Oct 13, 2026. At that point the published list held five closed signals. All five were losses. There were no published wins yet, so there's nothing to show on that side. I'm not waiting for a winner to make this example look better.
| Opened | Ticker | Side | Indicator | Entry | Original stop | Stop move | Exit | Exit date | Result |
|---|---|---|---|---|---|---|---|---|---|
| 2026-10-12 | AR-USD | long | PDHL 1d | 4.3120 | 4.0720 | → 4.3840 (2026-10-13) | 3.7460 flip:short | 2026-10-13 | −2.36R / −13.13% |
| 2026-10-12 | CELO-USD | long | PDHL 1d | 0.0996 | 0.0953 | → 0.1002 (2026-10-13) | 0.0910 flip:short | 2026-10-13 | −2.00R / −8.63% |
| 2026-10-12 | LDO-USD | long | PDHL 1d | 0.4451 | 0.4202 | → 0.4501 (2026-10-13) | 0.4031 flip:short | 2026-10-13 | −1.69R / −9.44% |
| 2026-10-12 | LTC-USD | long | PDHL 1d | 64.68 | 63.41 | → 64.85 (2026-10-13) | 61.07 flip:short | 2026-10-13 | −2.84R / −5.58% |
| 2026-10-12 | FET-USD | long | 3/9X (ema39) 1d | 0.2387 | 0.2148 | → 0.2442 (2026-10-13) | 0.2132 flip:short | 2026-10-13 | −1.07R / −10.68% |
Against the checklist: every published close is listed (check 1). Each row has an entry and an original stop (check 2). The stop move has its own date (check 3). The exit has a reason, here a flip to short (check 4). The result is in R (check 5). The page says nothing in the list is edited after publishing (check 6). The history is short, and I say so (check 7).
Reading one row
Take AR-USD. Here's the math, one step at a time.
| Step | Math | Value |
|---|---|---|
| Risk (1R) = entry − original stop | 4.3120 − 4.0720 | 0.2400 |
| Move = exit − entry | 3.7460 − 4.3120 | −0.5660 |
| Result in R = move ÷ risk | −0.5660 ÷ 0.2400 | −2.36R |
| Result in % = move ÷ entry | −0.5660 ÷ 4.3120 | −13.13% |
Both numbers match the record. Note that R is measured against the original stop, not the moved one. That's on purpose. The original stop is what the trade was sized for, so it's the honest baseline.
Why some losses are bigger than −1R
If every trade has a stop, how does a loss reach −2.36R? Look at the stop move column. On Oct 13 the stop on AR-USD was raised to 4.3840, above the 4.3120 entry. On paper, that should have locked in a small gain. Instead the trade exited at 3.7460 on a flip, far below both the raised stop and the original one.
That's the lesson. A stop is a plan, not a guaranteed price. These signals run on daily candles and exit on a flip, so the recorded exit lands wherever price was when the flip fired. In a fast move, that can be a long way past the line. All five rows show it: every stop had been raised above entry on Oct 13, and every trade still closed at a loss of more than 1R.
"Published" vs "Already stored"
My record page has two lists. The difference matters for exactly this kind of check.
| Published | Already stored | |
|---|---|---|
| Covers | Signals published since Oct 6, 2026 | The latest closed trades stored for the current top indicator on each asset |
| Shows | Entry, original stop, every dated stop move, exit, reason, result in R | Entry, exit and result only |
| Stop history | Yes | No |
| Can change? | Never edited after publishing | Replaced when the scorecard is rebuilt |
| Use it for | Verification | Context only |
Use the Published list to verify. Treat the stored list as background. It can't pass checks 2, 3 or 6, because it has no original stop, no dated stop moves, and its rows can be replaced. That's why none of its rows appear as evidence in this article.
How to spot-check a row yourself
Don't take my word for any of this. Pick a row and check it against the chart:
- Open my published signal record and pick a row. Note the ticker, dates, entry, stop and exit.
- Open that ticker's daily chart in any charting tool you like.
- Find the candle on the opened date. Does the entry match a price that candle actually traded?
- Find the original stop. Does it sit where the indicator's rule says it should?
- Find the stop-move date and check that the new level fits that day's candle.
- Find the exit date and confirm the exit price is inside that candle's range.
For crypto, make sure your chart uses the same daily candle I do: the UTC day, closing at 00:00 UTC. If your chart uses a different session close, the highs and lows can differ a little. You can also follow a signal from the start: open today's open signals, write down the levels, and check them against the record when they close.
Red flags that should end the conversation
- Screenshots only. A screenshot proves someone took a screenshot. It can be cropped, cherry-picked, or made up.
- No stops. Without a stop, there's no risk to measure and no way to count a loss.
- "90%+ win rate" claims. Without R, a high win rate tells you very little, and it often hides large losses.
- Edited or deleted posts. If old calls vanish or change, the record is whatever they want it to be today.
- Guaranteed returns. Nobody can guarantee a market outcome.
- Pressure to subscribe fast. "Only three spots left" is a sales tactic. A real record will still be there next week.
This also answers the question that keeps coming up in r/CryptoCurrency: are paid signals all a scam? Not all of them. But the ones that can't pass these checks give you no way to tell.
What a track record can't tell you
Even a perfect record has limits.
- The future. A record shows what happened. Markets change, and a method that did well in one stretch can struggle in the next.
- Your results. Your fills, timing, slippage and fees will differ from the published numbers. If you enter late, your R won't match the record's.
- Sample size. Five trades, or fifty, can be luck either way. The longer the record and the more varied the markets, the more it can tell you.
- Who checked it. As someone in r/Trading asks, "verified" by whom? Trasignal's audit guide covers what third-party verification does and doesn't prove, and points to the NFA's BASIC database for checking registered firms in the US. A verification badge is a starting point, not the end of the check.
FAQ
What makes a trading signal track record "verified"?
It lists every signal, published before the outcome, with entry, original stop, dated stop changes and an exit with a reason. Losses stay on the list, results are shown in R, and rows can't be edited after publishing. Third-party audits can help, but the most direct check is matching a few rows to the chart yourself.
Is a high win rate a good sign?
Not by itself. A method can win 76% of the time and still lose money if its losses are much bigger than its wins. What matters is the average result per trade in R, which combines how often you win with how much you win or lose. Ask for results in R, or for enough data to work R out.
What is R in trading results?
R is the amount you risk on a trade: the distance from your entry to your original stop. A loss of exactly that distance is −1R. A gain of twice that distance is +2R. R puts trades on different assets and prices on the same scale, and it shows how big the losses are next to the wins.
Why would a loss be bigger than 1R if there's a stop-loss?
A stop is a planned exit level, not a guaranteed price. Fast moves and gaps can carry price past the stop before the exit happens. On daily signals that exit on a flip, the exit lands wherever price is when the flip fires. On my record, AR-USD lost −2.36R even after its stop was raised above entry.
How long should a track record be before I trust it?
Longer is better. Many traders ask for 12 months or more, so the record covers different market conditions and at least one losing streak. A short record can show how a service reports trades, but it can't prove anything about the method. My published list starts Oct 6, 2026, and I treat it that way.
Are screenshots of trades proof?
No. Screenshots are easy to crop, cherry-pick or fake, and they only show what someone chose to share. A real track record is a complete, dated list where every signal appeared before its outcome and losses stay visible. Use screenshots as illustration at most, never as evidence of results.
Can I check a signal against the chart myself?
Yes, and you should. Open the ticker's daily chart, find the candles on the entry, stop-move and exit dates, and confirm each price sits inside that day's range. For crypto, use the same daily close the service uses. Mine is the UTC day, closing at 00:00 UTC. It takes a few minutes per row.
See it for yourself
The best way to judge any signal service is to read its record like a bank statement: every line, losses included. Start with mine. ALK Trading is free for everyone.
See every published signal, losers included, on the record, then try the checklist on today's open signals.
If you want to learn to read these setups and set your own stops, Join the mentorship, $79/mo.