Skip to content
Scan guide

VWAP Reclaim Scanner

Stocks that were below VWAP and have taken it back.

What the setup is

VWAP is the volume-weighted average price of the session so far. A stock above it is trading higher than the average price paid today, and a stock below it is trading lower.

A VWAP reclaim is a change of side. The stock was below VWAP, and it has now moved back above it. Traders read it as a failed breakdown: sellers pushed the stock under the average price and could not keep it there.

The word that matters is "was". A scan for stocks above VWAP returns every stock above VWAP, including the ones that never left. A reclaim scan has to confirm the stock was below the line a short time ago and is above it now.

The scan as a sentence

In Fastur you can describe the scan in plain English. For this setup the sentence looks like this:

was below vwap in the last 10 minutes and has reclaimed it

The assistant turns that into code you can read. The core of it is below. It is a fragment that shows the idea, not a complete script.

logicblock WasBelowVwap = m1.close[2:10].min < d1.vwap
logicblock VwapReclaim = WasBelowVwap and m1.close[1] > d1.vwap and trade.last > d1.vwap

What each part checks

m1.close[2:10].min < d1.vwap
At least one of the one-minute bars from two to ten minutes ago closed below VWAP. The stock was under the line recently.
m1.close[1] > d1.vwap
The last completed one-minute bar closed above VWAP. This is the reclaim, confirmed by a close and not only a tick.
trade.last > d1.vwap
The last trade is still above VWAP.

The choices that change the results

A close above, or a touch above
Requiring a completed bar to close above VWAP is slower and filters out stocks that poke through for a few seconds. Dropping that line catches the cross on the trade it happens.
How long it was below
One close below in the last ten minutes is a brief dip. Asking for several closes below describes a stock that really lost the level before taking it back.
Volume on the reclaim
A reclaim on a surge of volume is a stronger statement than one on a quiet drift. That is one more condition comparing the last bar with the bars before it.

Common mistakes

Scanning for "crossed above VWAP" on a timer
A cross is an event. If the scan only looks every minute, it either misses crosses that reversed or reports them late.
Forgetting that VWAP moves
This fragment compares earlier bars with the current VWAP, which is a close approximation over ten minutes. Over hours VWAP drifts, so long windows need more care.
Trading reclaims in a stock chopping around VWAP
A stock that crosses VWAP every few minutes produces a reclaim each time. A condition that it had been below for a while removes most of these.

Questions

What is a VWAP reclaim?
It is a move back above the volume-weighted average price by a stock that had been trading below it earlier in the session.
How is a VWAP reclaim different from a VWAP pullback?
A pullback comes down to VWAP from above and holds. A reclaim starts below VWAP and crosses back above it. The first is strength being tested, the second is weakness failing.
Can a scanner alert on a VWAP reclaim as it happens?
Yes, if it evaluates the condition on every trade and can check where the stock was a few minutes earlier. A snapshot of current values cannot tell a reclaim from a stock that was above VWAP all along.
Build the scan

Write a scan, then run it live

Create the logic once, run it live, and let scanner alerts tell you what changed.

LogicBlocks
Scanner-ready custom calculations
VWAP_HOLD
trade.last > d1.vwap and trade.last > m1.high[t"04:00":t"09:29"].max
in scan
REL_VOL
d1.volume / d1.volume[1:20].mean
column
GAP_PCT
(d1.open - d1.close[1]) / d1.close[1] * 100
filter
RANGE_PCT
(d1.high - d1.low) / d1.low * 100
saved
Used by VWAP Hold3 matches