How to read EOD replay & stats
After the session, Discord #eod-replay and the public
stats page show what the scanner graded —
and an illustrative option-premium path under a simple +25% / −25% plan.
That is not your fill, not subscriber P&L, and not a promise of future results.
Two places, one idea
- Discord EOD replay — members see that day’s graded setups and hypothetical bracket notes.
- Public stats — featured cards + weekly/session KPIs (A+ / B counts, call/put mix) for transparency.
- Desk → Replay pane — intraday timeline of today’s A+/B candidates from the live log ((desk guide).
What a featured card shows
- Symbol — SPY, QQQ, or IWM (which index the alert was on).
- Direction — CALL or PUT (the side the setup implied).
- Time — when the scanner printed (ET).
- Grade — A+ (7–8/8) or B (6/8).
- Setup — plain-English structure (e.g. bounce off the pin, failed breakout at resistance).
- Level / spot — the rail and underlying price at the alert.
- Peak % — best mark after the alert for the rest of the session. A late rip still counts.
- Ran green — premium printed a gain after the alert.
- Never green — no gain after the print. These are the losing trades.
Peak · never green
End-of-day stats measure the rest of the session after the alert — not a 30-minute ±25% clock.
- Peak % — best mark after the print. If it ripped later, that is the number.
- Ran green — premium printed any gain after the alert.
- Never green — no gain after the print → a losing trade.
If premium ran green at all, the big number is that peak. The Never-green tab is only the ones that never went green.
Why this is not “P&L”
- Entry is modeled (ATM-ish 0DTE), not your actual fill or strike.
- A tight ±25% bracket sits inside normal 0DTE noise for many days — real desks often use structural stops and scale-outs.
- Same-rail re-fires are collapsed on the public page so one idea doesn’t look like six winners.
- KPIs use distinct setups where noted — raw scanner spam is not the headline count.
How to use the page as a subscriber
- Read grades and structure first — did the scanner fire at a real rail with a candle?
- Treat peak / never-green as a quality sketch, not a scoreboard to chase.
- Compare to your own journal: did you take the idea, skip it, or exit differently?
- Never size up because last week’s illustrative peaks looked big.
KPIs on the stats hero
- A+ · this week — distinct high-conviction prints in the focus window.
- B · this week — distinct 6/8 prints (dupes collapsed).
- CALL / PUT — direction mix of A+ and B in the featured / focus window (A+-only can read 0%/100% on one-sided weeks).
See this week’s cards
Public scanner stats — educational transparency, not a performance guarantee.
Open stats How grading works