A line scan is a bot reading the odds board, over and over, looking for a price that moved before the market caught up. One player scanned a college football board 204 times in 47 minutes, starting at 5:05 in the morning. The scan itself is not a bet. It is the preparation for one, and books watch for it because the repetition is the signal.
What a line scan looks like from the book's side
From the book's side, a line scan is a flood of requests for the same board. One player scanned a college football board 204 times in 47 minutes, starting at 5:05 in the morning, and the same account had 19,869 total scans on NFL boards across the season. The scans arrive on a schedule a human would never keep: every few seconds, for the better part of an hour, before dawn.
Books run an hourly detection scan of their own, looking for exactly this pattern. The scan report lists the account, the board, the count, and the cadence, and it lands in a queue for review. The scanner is not betting yet. They are watching for the line to move, and the book is watching them watch.
Why repetition is the signal
A human checks the odds a few times before a game. They check the spread, they check the total, they come back after lunch. A scanner checks the board hundreds of times, and the checks cluster around line moves. The repetition is the signal because no human behavior looks like it: nobody refreshes a college football board 204 times in 47 minutes by hand.
The cadence gives it away even when the count does not. Human refreshes are irregular, with long pauses and short bursts. Scanner refreshes are regular, with a fixed interval between requests. The regularity is the fingerprint.
What books do with the report
A scan report rarely leads to a ban on its own. What it leads to is stake factoring: the book cuts the account's maximum stake to 25 percent, or to 1 percent, and watches what happens next. If the account keeps scanning and starts betting the moved lines, the limits tighten further. If the account stops, the report stays on file and the limits stay where they are.
The point is not to punish scanning. It is to price the information. A scanner who finds a stale line is an edge the book does not want to offer, and the cheapest way to remove the edge is to shrink the stake until it stops mattering.
What a scan cannot tell the book
A scan report is suspicion, not proof. Scanning a board is not betting, and a bot that scans but never bets is a bot the book cannot act against without banning the act of looking. The report becomes actionable only when the scan connects to a bet: the same account, the same line, the same move, within minutes of the scan.
That is why the books wait. The scan tells them where to look. The bet tells them what to do.
Keep reading
Related guides on this site: how bonus abuse rings run multi-account farms what a steam move says about sharp money how arbitrage betting ends in account limits More from Bot Protection For Sportsbooks.
Frequently asked questions
Is scanning the odds board illegal?
Usually not, on its own. Reading public odds is not a bet and not a crime. What gets flagged is the pattern: hundreds of scans in minutes, at hours no human is awake, from an account that then bets the moved line.
How many scans does it take to get flagged?
There is no fixed number, and books do not publish one. The flag comes from the pattern: scan cadence, time of day, and whether the scans cluster around line moves. One player was flagged after 204 scans in 47 minutes; another after 19,869 scans across an NFL season.
Do books share scan reports with each other?
Books do not publish scan reports, and there is no shared database of scanners. What they share is the behavior profile: the same device, the same cadence, the same accounts showing up at different books with the same pattern.
Can a human bettor trigger a scan flag by accident?
Yes, if you check the same board repeatedly before a big game. The difference is scale and timing. A human checks a board a few times an hour. A scanner checks it hundreds of times, at 5 AM, and bets only when the line moves.