Bitcoin Volume Profile POC Scanner for Crypto Alerts

Most traders who use Volume Profile apply it to three or four symbols they follow closely. They draw the profile, note where the Point of Control sits, and watch for price to return to that level. Across three coins, that workflow holds.

Across 300 active pairs, you need 300 Volume Profiles and 300 individual price alerts updated every morning. Nobody does that. The structural level gets missed on every coin you are not already charting.

AnomIQ is adding a POC distance filter. One filter, set once, watches every active pair and fires the moment price trades within a defined percentage of the previous day’s Point of Control.

If you want the live BTC reference before building a scanner rule, use the Bitcoin Volume Profile POC Current tool to inspect developing POC, previous-day POC, VWAP, value area, HVN and LVN levels on one page.

What Is the Point of Control?

The Point of Control (POC) is the price level, or narrow price band, where the most volume traded during a session. It comes from a Volume Profile: a histogram mapping volume to price increments rather than time. A candlestick chart shows volume per bar. A Volume Profile shows volume per price level. The bucket with the highest accumulated volume is the POC.

High-volume nodes attract re-engagement. Participants who traded in size at a price level tend to re-enter or defend that level when price revisits. The POC marks where the most prior commitment from a session sits.

Returning to POC does not guarantee a reaction. It establishes a structural condition. Aggressive directional flow at the same moment gives that condition weight.

Why Yesterday’s POC

AnomIQ uses T-1: the Point of Control from the prior complete UTC day.

The current session’s POC shifts with every trade. It takes hours to stabilize and keeps accumulating until the session closes. Basing decisions on it means anchoring to a number that is still changing.

Yesterday’s POC is settled. Every trade from that UTC day counted. The highest-volume node is fixed. That is what participants from the previous session are watching when price returns.

VWAP resets each session for the same reason: completed data anchors; in-progress data is still being written.

The 300-Chart Problem

Volume Profile access is not the problem. Drawing one and setting a POC alert is a per-chart manual operation. Fifty symbols means fifty profiles to maintain and fifty alerts to update each morning as the T-1 POC shifts. In practice, traders skip it and watch the same handful of coins they always do.

A mid-cap altcoin can spend two sessions testing its highest-volume node while nobody notices, because nobody drew that profile.

Set one condition in the scanner. It watches every pair and flags when the condition is met. You review the results.

The Adaptive Bucket Problem

Cross-market Volume Profile breaks on one constraint: bucket width.

A $5 bucket on BTC at $85,000 gives roughly 400 buckets across a normal daily range. Workable. Apply that same $5 bucket to a $0.40 altcoin and the entire instrument collapses into one bucket. Apply a $0.001 bucket to BTC and you get 85 million price increments, most empty, and the profile tells you nothing.

Fixed bucket sizes fail across instruments. Per-instrument manual calibration breaks every time an asset reprices. Neither works at scale.

AnomIQ sizes each bucket from the instrument’s own recent volatility.

The calculation:

1. Take the median 5-minute true range from T-2 (two days before the calculation date). The 5-minute true range captures intraday volatility without distortion from a single extreme bar. The median across all 288 5-minute bars in the day absorbs outlier spikes.

2. Divide by 10. Ten buckets per typical intraday move gives enough resolution to locate the high-volume node without making the distribution sparse.

3. Round to a clean tick increment. Dividing a floating-point true range by 10 produces something like 14.67 ticks. AnomIQ rounds to the nearest clean integer: 15 ticks, 20 ticks, 50 ticks. Buckets land on natural price increments for the instrument.

4. Clamp to valid range. Minimum 25 ticks prevents single-tick noise buckets during quiet markets. Maximum 20,000 ticks preserves resolution during low-volatility periods.

BTC, ETH, a $0.40 altcoin: the same formula, different output widths. Each instrument’s bucket size reflects how it actually moves. No manual configuration per symbol.

How AnomIQ Computes the T-1 POC

The sequence per symbol, each UTC day:

1. T-2 reference arrives. The previous day’s completed trade summary contains the median 5-minute true range. AnomIQ uses this to set the bucket width for the T-1 session. Trades arriving before this reference get queued and applied once the bucket width is confirmed.

2. Bucket width is fixed. bucketWidth = round_nice(medianTR / 10), clamped. Every trade that day assigns to buckets using this constant.

3. Each trade accumulates into its bucket. AnomIQ converts the trade price to ticks, integer-divides by bucketTicks, and accumulates volume at that bucket key.

4. POC updates with each trade. The bucket with the highest volume at any point is the running POC. At day close, it becomes the T-1 reference.

5. The result is a band, not a point. The output is bucketLowTick and bucketHighTick, a price range. Collapsing it to a single number claims precision that was never there.

The Filter: POC Distance Percentage

POC Distance % = |current price − POC midpoint| / POC midpoint × 100

Once live, set a threshold of 0.3% and the scanner returns every symbol where current price sits within 0.3% of yesterday’s POC.

POC distance identifies one condition: price is near a level that mattered yesterday. What happens at that level is what the other filters read. The starting point will look like this:

POC Distance % < 0.3

Most traders will add a second condition within the first session.

Building Confluence: POC Plus Flow

POC proximity tells you where price is, not what is happening there. These are the filter combinations planned for the first release.

POC proximity + Volume Z-Score

Today's Volume (Notional) > $500,000
AND POC Distance % < 0.3
AND Volume Z-Score (5m) > 2.0

Volume two standard deviations above this instrument’s 24-hour baseline, at the same price zone where the session’s highest volume traded yesterday. Price hitting the level with unusual activity. Z-score normalization defines “anomalous” relative to each instrument’s own history, so the same threshold calibrates across BTC and a micro-cap. For the volume-specific version of that math, see Z-Score Volume Anomaly Detection in Trading. The Today’s Volume (Notional) floor keeps the rule off illiquid symbols where thin order books inflate z-scores trivially.

POC proximity + Taker Imbalance Z-Score

Today's Volume (Notional) > $500,000
AND POC Distance % < 0.3
AND Taker Imbalance Z-Score (5m) > 2.5

Aggressive buyers or sellers initiating at an unusual rate at the price zone with the highest volume from the prior session. Net Taker Imbalance measures who is driving the tape. A reading above 2.5 puts that directional skew in approximately the top 1% of historical readings for this specific instrument — higher than a Gaussian interpretation would suggest, because crypto imbalance distributions are right-skewed with fat tails.

Three conditions together

Today's Volume (Notional) > $500,000
AND POC Distance % < 0.3
AND Volume Z-Score (5m) > 1.8
AND Taker Imbalance Z-Score (5m) > 2.0

Structural level, elevated volume, directional aggression. Three filters this tight fire rarely. When they do, each result has more behind it than a single-condition scan would surface.

For how these metrics interact across timeframes, see How to Detect Crypto Volume Anomalies in Real Time.

What This Is Not

The POC distance filter is a scanner condition, not a chart overlay.

AnomIQ embeds a TradingView widget for price action. Drawing a full Volume Profile inside that panel, with the bucket distribution and POC highlighted, requires TradingView integration work that is not in this release.

What will ship in the first release: POC distance as a scannable filter threshold. When the scanner surfaces a symbol, you open it in TradingView, pull up Volume Profile, and read the chart. Thirty seconds. The scanner watched 300 pairs. You review one.

For a live BTC-only view of those same POC, VWAP, value-area, HVN and LVN levels, open the Bitcoin Volume Profile POC Current tool.

POC vs VWAP: Two Different Questions

Both metrics use price and volume. They answer different questions.

VWAP and POC complement each other. VWAP tells you where price is relative to intraday fair value. T-1 POC tells you where the prior session’s highest-conviction trading happened. They often sit near each other in directional markets. When they diverge, the gap tells you something about how the current session differs from the prior one.

Frequently Asked Questions

What is the Point of Control in crypto trading? The price level where a session’s highest volume traded. A Volume Profile maps volume across price increments rather than time bars. The bucket with the most accumulated volume is the POC. Participants who traded in size at that level tend to re-engage when price revisits, which is why traders use it as a structural reference.

Why use yesterday’s POC instead of the current session’s? An in-progress POC shifts with every trade and takes hours to stabilize. T-1 is final: every trade counted, the level fixed. That is what participants from the previous session are watching when price returns.

How does AnomIQ handle bucket sizing across different assets? AnomIQ derives bucket width from the instrument’s T-2 median 5-minute true range, divides by 10, rounds to the nearest clean tick increment, and clamps to a valid range. BTC and a $0.40 altcoin get different dollar widths but equivalent resolution relative to each instrument’s daily range. No manual configuration.

What does POC distance percentage mean? How far current price sits from the prior day’s POC midpoint, expressed as a percentage. A reading of 0.2% means price is 0.2% from yesterday’s highest-volume node. Set a threshold and the scanner flags every pair meeting it.

How is POC different from VWAP? VWAP is a running average: the average price paid per unit of volume, updated through the session. POC is a structural node: the price band where the most total volume accumulated in discrete buckets. They often land near each other in a trending session. In accumulation and distribution phases they diverge, which is when the distinction matters.

Can POC distance combine with other AnomIQ filters? Yes. Common pairings: POC distance with volume z-score to catch anomalous activity at the level, and with taker imbalance z-score to catch directional aggression there. Multi-condition filters cut the noise.

Current Status

The T-1 POC calculation is built and tested. The backend computes a fresh Volume Profile for every active pair each UTC day and publishes the settled POC before the next session opens. That part works.

What is not live yet: exposing POC Distance % as a configurable threshold in the scanner builder. That is what this post is announcing. No release date. It ships to all existing users when it is ready — no action needed on your side.

If you want early access, sign up at AnomIQ. You will have it as soon as it goes live.