Lenz

Public Self-Scorecard

The app grades its own calls — winners, losers, and WAIT-resolutions, never hidden.

How results are counted just got more accurate

Previously, if price reached the target, the analysis was counted as "correct" — even when price never reached the suggested entry. Since July 18, 2026, only analyses whose entry price actually traded are counted. This is why the record number is lower. Past analyses have not changed — only the counting is now more honest.

This is analysis, not financial advice — the final decision is yours.

For a buy or sell call, “correct” means price reaches the first target before the stop-loss — the price that breaks our plan. Every call is graded against the levels it was published with — moving them later never re-grades it. If it reaches neither inside the window, the call still counts, just not as correct.

Resolved so far: 8 of the 10 calls needed. We show the accuracy figure once the count reaches 10.

One call never reached the entry price. It is not graded and is not counted in any figure on this page.

Performance summary

Resolved so far: 14

Buy/sell calls
8 of 10 needed to publish
Calls where the read was Wait
6 of 10 needed to publish

A WAIT call is scored only on whether the price reached the level it named within its stated horizon — never on what would have happened after.

We give analysis, not buy or sell orders.

The decision is always yours.

Last computed: 24 hours ago

How accurate we've been
Each point is one confidence group; the closer to the line, the more accurate — all call types combined.
Not at the needed count yet
Perfect accuracy0%20%40%60%80%100%0%20%40%60%80%100%Each group's benchmarkWhat actually happened
One circle per group — a bigger circle means more callsProbable error rangeThin data
Accuracy by call type
The wrong calls and reviewed waits are in this number too.
BuyStill gathering
3 of 10 needed to publish
SellStill gathering
5 of 10 needed to publish
Wait (resolved)Still gathering
6 of 10 needed to publish
HoldStill gathering
0 of 10 needed to publish
Secondary measure
Each call's own levels against its price outcome, in R

This is not a percentage and it does not replace the accuracy figure above; it measures how far price moved past each call's own published entry, target, and stop — not what someone who followed the call, including any exit, would have made.

This measure is shown once the needed episodes are on record.4 of 10 episodes needed

This count is not the same as the resolved-calls count above and must not be read against it: episodes that reached neither target nor stop — timed out, still open, or never entered — are left out here, because their realized return cannot be read off the original plan alone.

Buy and sell, separately
Buy calls
This measure is shown once the needed episodes are on record.1 of 10 episodes needed
Sell calls
This measure is shown once the needed episodes are on record.3 of 10 episodes needed

When the market gapped through the stop, a stop-out's R is booked at the breaching bar's open — the fill a holder could actually have got, which can be worse than -1R. Where no bar is on record it falls back to the analysis's own stop price.

The unit is R: one R is the distance from a call's entry to its stop — the amount that call puts at risk. A clean stop-out reads as −1R, and a negative number here is entirely normal.

Call audit ledger

Open every row and check the arithmetic yourself

Detail layer
What this app does with its own calls

This section is about the app's own behaviour: how often it steps away from a call, how long a call lives, and whether stepping away helped.

None of the numbers here is a score, and a high one is not good news; do not read them alongside the percentage at the top of the page.

This section stays hidden until at least 10 episodes have ended — not partially, and not with a stand-in number.

This scorecard updates weekly, and no call is ever removed — it is always right here.