FuturesAI Scoreboard: 10 New Crypto Calls, 0 New Hits

Short answer: FuturesAI’s crypto scoreboard record went from 48 hits in 84 calls (57.1%) on October 31, 2026 to 48 hits in 94 calls (51.1%) on November 15, 2026. All 10 new calls were misses. At the scoreboard’s 1.19 payoff ratio, break-even is about 45.7% before costs and 51.6% in the strictest fee case below, so the crypto record has slipped under that line. Not investment advice. Leveraged futures can lose your entire margin.

Educational arithmetic, not investment advice and not a forecast. Figures were read on FuturesAI on November 15, 2026 and can change.

Forty-eight hits. That number has not moved across three snapshots of the crypto line.

The denominator did move. 84 calls, then 92, then 94. Every call added in between missed, and that changes how the record reads next to a fee line. This post tracks the drift and works out how far it can go before it matters.

Check it on FuturesAI

What This Works Out

What did the crypto record look like at each snapshot?

FuturesAI’s public scoreboard, last auto-checked on November 15, 2026, lists crypto accuracy at 51.1% (48 of 94 scored calls), against 46.9% for US stocks (53 of 113) and 41.2% for Korean stocks (54 of 131) (futuresai.io/en/quant/scoreboard).

When I compared that with the two earlier readings I took of the same line, the hit count was identical each time.

Reading date Crypto hits / scored Accuracy Rough 95% band
October 31, 2026 48 / 84 57.1% 46.5% to 67.2%
November 11, 2026 48 / 92 52.2% 42.1% to 62.1%
November 15, 2026 48 / 94 51.1% 41.1% to 60.9%

Bands are Wilson 95% intervals that I computed from the counts. The October 31 and November 11 readings match what I wrote in FuturesAI UP vs DOWN Calls: How to Read the Return Gap and FuturesAI Scoreboard: Where Crypto’s 52.2% Sits After Fees.

Same pattern elsewhere. The overall line went from 148 hits in 321 graded calls to 148 hits in 323. Two more calls, no more hits.

Notebook and calculator on a desk used to work out a trading break-even win rate
Crypto hits stayed at 48 while scored calls rose from 84 to 94 between October 31 and November 15, 2026.

Where does 51.1% sit against the break-even line?

At the scoreboard’s overall payoff ratio of 1.19, a trade breaks even at a win rate of (R + C) / (R x 2.19), where R is dollars risked and C is round-trip fee plus slippage in dollars, which gives 45.7% when C is zero.

The fee inputs come from FuturesAI’s payback page as I read it on November 15, 2026: an effective market-order rate of 0.015% on Bitget and 0.045% on Binance (futuresai.io/payback). On a $10,000 position that is $3.00 and $9.00 for a round trip. I added slippage of 0.02% per side, or $4.00 round trip. That slippage is my assumption for a liquid pair, not a measured number.

Stop distance No costs Bitget rate + slippage ($7) Binance rate + slippage ($13)
1% ($100 risk) 45.7% 48.9% 51.6%
2% ($200 risk) 45.7% 47.3% 48.6%
5% ($500 risk) 45.7% 46.3% 46.8%

Check one cell by hand: a 1% stop on $10,000 risks $100, the Binance cost is $13, and (100 + 13) / (100 x 2.19) = 51.6%.

Now compare. On November 11 the crypto record, 52.2%, cleared even the 51.6% cell by 0.6 points. At 51.1% it is 0.5 points under that cell and still 2.2 points above the Bitget 1% cell (48.9%). It sits above every other cell in the table.

That is a small move on paper. It is the first time this record has crossed one of the lines.

How unusual is a 10-call run with no hits?

If crypto calls hit at a steady 51.1%, the chance of 10 misses in a row is 0.489 to the tenth power, about 0.12%, or roughly 1 in 820.

Against the earlier 57.1% rate it is 0.429 to the tenth, about 0.02%. Even at a flat 50% coin flip it is 0.1%. So the run is hard to explain as plain bad luck at a fixed hit rate.

Here is where people get tripped up: that does not tell you why. The scoreboard page does not say how it orders grading, and it does not publish call-by-call crypto dates in a way I could use to split by week. Some possibilities are a change in the crypto market, a batch of calls resolving together, or the hit rate simply not being steady. I can’t separate them from the public page.

Also note the page’s own mismatch. Its headline says 148 of 323, while the by-market table adds to 338 scored calls and 155 hits. I have used the by-market crypto line (48 of 94) throughout.

How many more misses would cross each line?

With 48 hits fixed, crypto accuracy falls under the 48.9% Bitget 1% line after 5 more misses (48 of 99, 48.5%), and under the 45.7% no-cost line after 12 more (48 of 106, 45.3%).

Line Scored calls where 48 hits drops below it More misses from today (94)
51.6% (Binance, 1% stop) Already crossed at 94 (51.1%) 0 (crossed on the 94th call; 48 of 93 was still 51.6%)
48.9% (Bitget, 1% stop) 99 (48.5%) 5
45.7% (no costs) 106 (45.3%) 12

The arithmetic is just 48 divided by 0.489, which is 98.2, so 99 calls is the first count under the line. Same for 48 divided by 0.457, which is 105.0, so 106.

New hits would push all of this back the other way. Each added hit is worth far more than a miss costs, because the whole record is only 94 calls.

What should you check before reading anything into it?

Before reading anything into a 10-call drift, check that the payoff ratio holds for crypto alone, that your own fills match the cost inputs, and that the record is dated.

  1. The 1.19 payoff ratio is an overall figure. The page does not split it by market, so I assumed crypto resembles it. If crypto’s true payoff is lower, every line above sits higher.
  2. Swap my $4 slippage for your own. Look at the gap between intended and filled price on your last 20 trades.
  3. The page states no fees in its numbers, and the index comparison uses daily closes. Real results sit below the scoreboard by the round-trip cost on every call.
  4. Take your own snapshot today. If the hit count is still 48, the story continues. If it moved, this post is out of date.

On the market-relative side, the page shows the overall average return per prediction at +0.05% against +2.12% for the market over the same windows, a gap of about 2.08 points.

Check it on FuturesAI

Tips

  • Save a dated screenshot of any scoreboard figure you rely on. It updates automatically and old values vanish.
  • Track hits and scored calls separately. A percentage alone hides whether the denominator or the numerator moved.
  • Use the lower end of the band for decisions, not the headline number.
  • Compare a hit rate with break-even after your own fees, not before.

Warnings

  • Not investment advice. FuturesAI makes no profit promise, and neither does this post.
  • Leveraged futures can lose your entire margin.
  • A 94-call record is small. Its 95% band is about 20 points wide.
  • The page’s headline and by-market totals do not match, so treat small differences between readings with care.

FAQ

Did FuturesAI’s crypto accuracy get worse in November 2026?

On the public scoreboard, crypto accuracy went from 57.1% (48 of 84) on October 31 to 51.1% (48 of 94) on November 15, 2026. The hit count stayed at 48 while 10 more calls were scored, so the drop comes entirely from new misses.

What win rate does a crypto trade need to break even at a 1.19 payoff ratio?

About 45.7% before costs. On a $10,000 position with a 1% stop it rises to roughly 48.9% at Bitget effective fees plus assumed slippage and about 51.6% at Binance effective fees plus the same slippage.

Does the scoreboard include trading fees?

No. The scoreboard says its results contain no fees and use frozen call-time prices against resolution prices. Any real trade would have the round-trip fee and slippage deducted from every call.

Sources

Next step: write down today’s hit count and scored count for crypto, then come back after the next batch and see whether the 48 moved.

Fact-checked against the FuturesAI scoreboard and payback pages as of November 15, 2026. Calculations are ours. Not investment advice.

📌 Hub guide: For the full earn-save-flip playbook — pricing, taxes, cashback, and collectible margins — see the Income & Smart Shopping Hub.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *