Skip to main content

Start here

How to research an esports bet

A price and a history are two halves of the same question. This is the order that connects them, and the five places the loop breaks.

Updated ResearchSample sizeOdds comparison

A bet has two halves. There is the number a book will pay you, and there is what happened the last twenty times the situation came up. Most betting research is one half with the other missing — a price with no history behind it, or a record with no price attached to it.

This page is the order that connects them. It is the same five steps whether or not you have money on the match: a fan asking whether a player's form is real and a punter asking whether 1.80 is a fair number are doing the same arithmetic, and only one of them has a receipt at the end.

The five steps

  1. 1.Start at the slate. Which matches are on, when, and at what tier. That decides which maps are relevant before any number is read.
  2. 2.Take one line — one player or one team, one statistic, one threshold. A line is not a player, and a threshold is not a statistic.
  3. 3.Fix the window. Last 5, 10 or 20 maps, on conditions that match the match you are looking at: same roster, same patch, same venue type.
  4. 4.Put a price on it. A stored snapshot where one exists for that book, otherwise the decimal or American price from your own.
  5. 5.Subtract. The price gives an implied chance, the stored maps give a hit rate, and the difference between them is edge.

edge = hit rate − implied probability

Implied probability = 1 ÷ decimal odds. 1.80 asks for 55.6%. Hit rate = hits ÷ maps counted.

Every number in that pair is arithmetic on numbers you can see. Nothing here forecasts a map, and the loop produces no picks — a positive edge is a comparison between a price and a record, not a prediction about the next one.

What each step needs

StepNeedsGives back
SlateA stored fixtureThe matches, and which maps count
LineThe statistic and the thresholdOne column of hits and misses
WindowStored maps on comparable conditionsA hit rate with a sample count
PriceA stored snapshot, or your pasted numberImplied chance
SubtractionBoth halves at onceEdge, in points

Where the loop breaks

  • A rate read over the wrong window. Twenty maps and five maps can describe the same player with a twenty-point gap between them — the window is why.
  • A rate treated as a forecast. It is a count of stored maps, nothing more. A 70% line still misses about three times in ten.
  • Conditions blended together. Online and LAN maps behave differently, and an average of the two describes neither one (LAN vs online).
  • A missing price read as missing history. When there is no stored snapshot the hit rate still ships; only implied and edge go blank.
  • A threshold taken from memory. Books post different numbers and move them, so the line that decides the bet is the one on your own book (player prop lines).

Putting the two halves together

Edge is only the name for the subtraction, and it exists only when both halves are present. That is why some rows carry a rate and no edge: the history is real, and the price for that book is not there. It is also why the break-even calculator is useful before any history exists — it takes a single price and returns the rate that price demands, which is the number the history then has to beat.

When the data is thin

The honest answer to insufficient data is empty. ClutchIQ omits a rate below five stored maps rather than printing a percentage four maps cannot support, flags five to nine as a small sample, and leaves a headshot rate blank when the source never recorded headshots.

Do it the same way twice

Most arguments about whether a number is any good are really arguments about which maps were counted. Name the statistic, the threshold, the window and the price together and the disagreement usually resolves into arithmetic — often with both people correct about their own sample.

If you have a price and nothing else, the break-even calculator will tell you what it needs. If a term on this page is unfamiliar, the glossary defines hit rate, implied chance, edge and the sample floor. Informational and entertainment use only. Not a sportsbook. 18+.

Questions

Where do I start if I have no price?
With the rate. Take the match, take the line, fix the window, and read the hit rate on its own. A missing price removes the subtraction, not the history. If the price is the only thing you have, the break-even calculator does the reverse and tells you the rate that price demands.
Why does the order matter?
Because each step depends on the one before it. A price means nothing until you know which line it prices, and a hit rate means nothing until you know which maps were counted. Doing the window last is how a rate ends up quoted over a sample nobody chose.
Is this the same as a betting model?
No. A model forecasts; this counts. ClutchIQ compares a stored or pasted price to stored results and shows the difference. It does not predict the next map, and a positive edge is not a guarantee of anything.
How many maps do I need?
Ten or more stored maps is treated as usable, five to nine is a small sample worth flagging, and below five ClutchIQ shows nothing at all. A stable roster, patch and map pool matter as much as the raw count, which is why the window is a judgement rather than a rule.
Can I research a book ClutchIQ does not price?
Yes. Paste the decimal or American price on the match page and the arithmetic runs on your number. ClutchIQ is not a sportsbook, does not hold funds, and does not link out to a book.

Read next

← All guides · Glossary