Binance Range Deviation Scanner
Loading...
Range Deviation Scanner

Scan Pairs Filters

Side Regime 4H state Min deviation percentile Min volume ratio Hide cost-dominated Show short-history pairs Show correlated duplicates

No scan yet

Run a scan to measure how far each of the top USDT pairs has moved from its range, with historical base rates attached.

Scan

Data source unreachable

The Binance API cannot be reached from this browser right now — a geo-block, an extension or an offline device would all look like this. Nothing else is affected.

Retry

Scan could not start

The venue refused the first requests. Wait a moment, then try again.

Retry

Scanning…

No qualified setups

Nothing passed the current filters — open Filters and relax them, or scan again after the next daily close.

Retry

Sort Find pair
Pair Side Deviation Residual rank Quantile band 10/90 (55d) 4H state Base rate Log

Skipped pairs

    Back

    Record paper trade Explain figures

    AI paraphrase

    Close

    A plain-words gloss of this pair's figures. The figures are the record; this is a paraphrase of them.

    Uses about 1 credit and sends only the figures shown.

    Retry

    Daily — candles with walk-forward band ribbon

    4H — same daily band, trigger markers

    Markers: 4H close beyond the band, and 4H close back inside it. The solid bright line is the current price.

    Forward log

    Above-band records are hypothetical shorts and below-band records hypothetical longs on a spot universe; borrow is not modelled.

    No records yet. Open a pair from the scan and record a paper trade to start the log.

      Hypothetical sandbox. Not advice, not a signal. It sees only the numbers on this screen and cannot change the scan, the forward log or the base rates.

      Find pair Pair from the last scan
      Open detail Speculate

      Uses about 1 credit per call. Only the figures shown are sent.

      No scan yet

      Run a scan first — the sandbox works from the last scan's rows.

      Hypothetical sandbox

      This is a hypothetical exercise, not advice and not a signal. It sees only the numbers on this screen. It never touches the scan, the forward log or the base rates.

      Continue Cancel
      HYPOTHETICAL measurement quality and flags — not a forecast

      Applicability flags

        Asserted conventions, not calibrated — they label the row; they do not change the measurement tier.

        Retry

        Decided by code — no credits were used.

        Levels are the row's stored levels — the same ones on the detail screen. Calls resolve like forward-log records: from the event onset, using this snapshot. Base rates measure the onset event; they are context, not a track record for a later entry.

        Sandbox scorecard

        Calls resolve like forward-log records. Reclaim calls are logged but not scored in v1 — no pre-registered outcome exists for that trigger.

        Settings

        Costs

        Taker fee per side (bps)

        Spot USDT pairs only in v1. Spread is read live at scan time and never applied to history.

        ER deciles — current scan

        Where the 0.30 / 0.50 cuts land on live data, instead of trusting them.

        Parameters

        Items marked “unvalidated default” are asserted, not validated, and are tuned only under the pre-registered protocol. Changing one starts a new config epoch.

        Engine self-tests

        Run self-tests

          Data

          Reset cached data

          Clears the cached universe and the last scan. The forward log is kept.

          Read-only. No API keys, no order endpoints, no writes to Binance — this is not a bot.

          Results and the forward log are stored in your app storage only.