Gap and Go Scanner
Stocks that gapped up and are trading above their premarket high.
What the setup is
A gap is the difference between where a stock opens and where it closed the day before. A stock that closed at 10.00 and opens at 10.60 has gapped up 6%. Gaps usually come from news that arrived while the market was closed: earnings, an FDA decision, a contract, an upgrade.
Gap and go is the name for a gapper that keeps going after the open. The usual test is the premarket high. During premarket trading the stock sets a high, and if it trades above that high once the regular session starts, buyers are still in control at higher prices.
A scan for it needs three facts at once: the size of the gap, the highest price from 04:00 to 09:29, and the current price after 09:30. The second one is a fixed window of time, which is the part most filter menus cannot express.
The scan as a sentence
In Fastur you can describe the scan in plain English. For this setup the sentence looks like this:
gapped up more than 4% and is now trading above its premarket high
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.
| 1 | GapPct = (d1.open - d1.close[1]) / d1.close[1] * 100 |
| 2 | PmHigh = m1.high[t"04:00":t"09:29"].max |
| 3 | logicblock GapAndGo = GapPct > 4 and clock.time >= 34200 and trade.last > PmHigh |
What each part checks
- (d1.open - d1.close[1]) / d1.close[1] * 100
- Today's open compared with yesterday's close, as a percentage. This is the gap, and you can show it as a column.
- m1.high[t"04:00":t"09:29"].max
- The highest high of the one-minute bars from 04:00 to 09:29. This is the premarket high, and it does not change after the open.
- clock.time >= 34200
- Only from 09:30:00 on. The clock is in seconds since midnight Eastern.
- trade.last > PmHigh
- The last trade is above the premarket high. This is checked on every trade.
The choices that change the results
- How big the gap has to be
- Four percent is a common floor for small and mid-size stocks. Large stocks rarely gap that much, so a lower number suits them.
- Whether volume has to be there
- A gap on little premarket volume often fades. A floor on volume traded so far, or on relative volume, removes thin gappers.
- Which level counts as "go"
- The premarket high is the standard. Some traders use the high of the first one or five minutes after the open instead, which is an opening range break on a gapper.
- Price and float
- Gap and go traders often limit the list to a price range. Add it as a condition so the list is the one you would trade.
Common mistakes
- Measuring the gap from the last premarket price
- The gap is from yesterday's regular close to today's open. Using the latest premarket price before 09:30 gives a number that keeps changing.
- Treating every gapper as a gap and go
- Most gaps do not continue. The break of the premarket high is what separates the two, so a list of gappers alone is only a watchlist.
- Scanning before the open and not after
- A premarket gap list tells you what to watch. The setup itself can only be true after 09:30, which means the scan has to keep running.
Questions
- What is a gap and go?
- It is a stock that opens well above the previous day's close and then continues higher after the open, usually confirmed by a move above its premarket high.
- How much should a stock gap for gap and go?
- There is no fixed rule. Many day traders look for gaps of 4% or more on small and mid-size stocks, with enough premarket volume to show real interest. Test the threshold on the stocks you trade.
- What is the premarket high?
- It is the highest price a stock traded at between the start of premarket trading at 04:00 Eastern and the regular open at 09:30.
Read next
- Why time-based conditions matter in a stock scanner
- Why snapshot stock scanners miss the best trades
- Opening Range Breakout Scanner
- VWAP Pullback Scanner
- Relative Volume (RVOL) Scanner
- Premarket High Breakout Scanner
- High of Day (HOD) Scanner
- VWAP Reclaim Scanner
- The fastur/1 scripting docs
- How plain English scans work
Write a scan, then run it live
Create the logic once, run it live, and let scanner alerts tell you what changed.