Hit rate (+120 min)
51.0%
1367 winners / 2682 measured
Honest scorecard — every recorded signal, every outcome
How Sigmatic's public signals have actually performed
Every BUY, WAIT, and SELL the app recorded for the public intraday scope, scored against the actual stored minute bars 30, 60, and 120 minutes after the call. WAIT counts are surfaced separately because a WAIT is not a directional bet — it's the absence of one. Disclosures · Back to the dashboard
Expectancy per call
-0.1%
Average signed return per directional call. Hit rate alone hides this.
Worst single session
-120.5%
Worst sum of signed returns from any one trading day in this window.
Window: Apr 23, 2026 → Jun 22, 2026 (NY) · 40 sessions. 2682 of 4291 directional calls have +120 min outcomes (price 2 hours later), 11,369 WAIT calls, 18 distinct symbols. Data last refreshed Jun 22, 4:37 PM ET (page rendered Jun 23, 3:16 AM ET).
Best + worst session in window
Best session+103.2%
Jun 9, 2026 · 116 of 136 directional calls measured · hit rate 62.1%
Worst session-120.5%
Apr 23, 2026 · 257 of 340 directional calls measured · hit rate 38.5%
Daily roll · last 40 sessions
| Session (NY) | Directional calls | With outcomes | Hit rate | Signed return |
|---|---|---|---|---|
| Jun 22, 2026 | 129 | 81 | 50.6% | -6.2% |
| Jun 18, 2026 | 42 | 37 | 51.4% | +0.4% |
| Jun 17, 2026 | 0 | 0 | — | — |
| Jun 16, 2026 | 169 | 117 | 88.0% | +22.9% |
| Jun 15, 2026 | 45 | 39 | 100.0% | +6.1% |
| Jun 12, 2026 | 53 | 53 | 35.8% | -5.7% |
| Jun 11, 2026 | 60 | 58 | 20.7% | -45.3% |
| Jun 10, 2026 | 123 | 71 | 64.8% | -9.5% |
| Jun 9, 2026 | 136 | 116 | 62.1% | +103.2% |
| Jun 8, 2026 | 82 | 52 | 28.8% | -13.6% |
| Jun 5, 2026 | 163 | 92 | 100.0% | +65.3% |
| Jun 4, 2026 | 26 | 26 | 96.2% | +5.4% |
| Jun 3, 2026 | 84 | 46 | 23.9% | -5.1% |
| Jun 2, 2026 | 154 | 132 | 71.2% | -19.2% |
| Jun 1, 2026 | 20 | 14 | 71.4% | +0.2% |
| May 28, 2026 | 59 | 56 | 98.2% | +10.9% |
| May 27, 2026 | 64 | 53 | 1.9% | -10.4% |
| May 26, 2026 | 29 | 26 | 3.8% | -5.3% |
| May 22, 2026 | 42 | 14 | 50.0% | -0.7% |
| May 21, 2026 | 31 | 20 | 25.0% | -0.7% |
| May 20, 2026 | 48 | 36 | 55.6% | -0.5% |
| May 19, 2026 | 55 | 48 | 31.3% | -10.2% |
| May 18, 2026 | 99 | 25 | 76.0% | +2.2% |
| May 15, 2026 | 29 | 18 | 0.0% | -6.1% |
| May 14, 2026 | 47 | 47 | 44.7% | -4.5% |
| May 13, 2026 | 30 | 29 | 82.8% | +6.2% |
| May 12, 2026 | 133 | 87 | 44.8% | +1.7% |
| May 11, 2026 | 17 | 1 | 0.0% | -0.4% |
| May 8, 2026 | 194 | 0 | — | — |
| May 7, 2026 | 362 | 122 | 56.6% | +19.6% |
| May 6, 2026 | 255 | 201 | 55.7% | -46.6% |
| May 5, 2026 | 95 | 26 | 53.8% | +2.3% |
| May 4, 2026 | 198 | 137 | 24.8% | -110.3% |
| May 1, 2026 | 110 | 61 | 32.8% | +16.4% |
| Apr 30, 2026 | 120 | 0 | — | — |
| Apr 29, 2026 | 15 | 5 | 100.0% | +3.9% |
| Apr 28, 2026 | 243 | 177 | 33.9% | -76.2% |
| Apr 27, 2026 | 210 | 161 | 30.4% | -24.2% |
| Apr 24, 2026 | 180 | 141 | 70.9% | +55.0% |
| Apr 23, 2026 | 340 | 257 | 38.5% | -120.5% |
Hit rate counts BUY + SELL calls whose price 2 hours later moved in the predicted direction. Sessions with zero directional calls don't appear (WAIT-only days are summarized in the headline counts above).
Data quality · tick counts in this window
Full ticks2,870
Every symbol the scanner attempted at this minute returned price data. Most ticks in a healthy window land here.
Partial ticks32
At least one symbol failed at this minute, but the broad-market posture symbols (QQQ + SPY) did return data. Signals are honored.
Outage ticks832
The scanner couldn't reach the data provider at this minute. Signals from these ticks are surfaced but flagged.
In flight0
The tick is still recording — the cron started but hasn't logged its end yet. A persistent nonzero count here signals stuck handlers.
All four buckets count ticks, not signals — each scanner run looked at every symbol we watch. 22 of 40 sessions in this window pre-date the per-tick history table (started 2026-05-02) — those sessions don't contribute to these counts.
1,288 provider ticks in the last 90 days were degraded (partial completion, handler error, or timeout). The most recent 50 are surfaced below.
- Jun 22, 4:45 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 4:40 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 4:35 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 4:25 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 4:20 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 4:15 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 4:10 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 4:00 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 3:55 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 3:50 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 3:25 PM partial-completion 0 of 2 symbols affected
- Jun 22, 3:20 PM partial-completion 0 of 2 symbols affected
- Jun 22, 3:10 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 2:45 PM partial-completion 0 of 2 symbols affected
- Jun 22, 2:40 PM partial-completion 0 of 2 symbols affected
- Jun 22, 2:35 PM partial-completion 0 of 2 symbols affected
- Jun 22, 1:40 PM partial-completion 0 of 2 symbols affected
- Jun 22, 1:35 PM partial-completion 0 of 2 symbols affected
- Jun 22, 1:25 PM partial-completion 0 of 2 symbols affected
- Jun 22, 1:05 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 12:50 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 12:10 PM handler-timeout 0 of 2 symbols affected
- Jun 22, 11:30 AM handler-timeout 0 of 2 symbols affected
- Jun 22, 11:25 AM handler-timeout 0 of 2 symbols affected
- Jun 22, 11:20 AM handler-timeout 0 of 2 symbols affected
- Jun 22, 10:49 AM partial-completion 0 of 1 symbols affected
- Jun 22, 10:49 AM partial-completion 0 of 1 symbols affected
- Jun 22, 10:48 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 10:48 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 10:47 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 10:47 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 10:34 AM partial-completion 0 of 1 symbols affected
- Jun 22, 10:33 AM partial-completion 0 of 1 symbols affected
- Jun 22, 10:32 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 10:32 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 9:59 AM partial-completion 0 of 1 symbols affected
- Jun 22, 9:58 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 9:58 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 9:57 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 9:57 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 9:55 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 9:54 AM partial-completion 0 of 1 symbols affected
- Jun 22, 9:52 AM partial-completion 0 of 1 symbols affected
- Jun 22, 9:51 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 9:51 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 9:49 AM partial-completion 0 of 1 symbols affected
- Jun 22, 9:48 AM partial-completion 0 of 1 symbols affected
- Jun 22, 9:47 AM handler-timeout 0 of 1 symbols affected
- Jun 22, 9:42 AM partial-completion 0 of 1 symbols affected
- Jun 22, 9:41 AM partial-completion 0 of 1 symbols affected
Why we don't lead with win rate
Win rate is the easiest number to inflate. A signal generator that calls a 0.1% move a “win” can hit 70% hit rate while losing money on every losing trade because the average loss is bigger than the average win. That's why this page leads with three numbers in equal weight:
- Hit rate — share of directional calls (BUY + SELL) that moved the predicted direction 120 minutes later. Easy to read but easy to game.
- Expectancy — average signed return per directional call. A 60% hit rate paired with +0.05% expectancy is a worse engine than a 45% hit rate paired with +0.4% expectancy. This is the number that pays the bills.
- Worst session— the worst single trading day's sum of signed returns. Tells you what the engine looks like on a bad day, not just an average day.
Read all three together. A scorecard that surfaces only one of them is a marketing pitch.
Corrections log
Sigmatic stores any after-the-fact correction to a signal or outcome (with operator email, before/after payload, and rationale) in an append-only audit table. The dashboard never silently rewrites history — if a number on this page changes after the fact, there's a row in the corrections log explaining why.
0 corrections recorded since the audit table started accumulating data on 2026-05-02. Zero corrections so far — the dashboard's recorded history matches what was shown live.
Not investment advice.This scorecard reflects what the public intraday scanner has done so far — it's a measurement, not a forecast. Past performance does not predict future results. Every signal on this page was generated by the same engine that runs the public dashboard, with no override or curation. R-based math (entry / stop / target / risk-reward) becomes available once the new outcomes materializer (deployed 2026-05-02) has run for a full window of trading sessions; until then, hit rate and signed-return metrics are the load-bearing numbers.