From a 44-Match Notebook to the VAR Review Room: How Cricket's 'Easy Numbers' Mislead Us

I began with 44 matches, a Rangpur notebook, and a suspicion of easy numbers. In 2026, at sixteen, I hand-coded an entire Bangladesh Premier League football season at Rangpur Stadium — shot location, pass direction, minute, outcome — because no local outlet printed anything beyond goals and cards. That habit has not changed. Before every match report I attach a numbers sheet, and the first question I ask is: what is this number actually measuring? That question matters more in cricket than ever, because the sport has become more measurable while falling deeper into the trap of easy numbers. Strike rate, economy, dot-ball percentage, fielding conversion — each rests on assumptions nobody audits. And in the middle of the 2026 regular season, when sides play two or three matches a week and the table shifts daily, those assumptions decide who stays in the title race and who buckles under relegation pressure. My second lesson came in 2026. Watching all 64 Russia World Cup matches on a 21-inch television, I logged roughly 1,200 shot coordinates from open sources into an xG model built on the notebook's column logic. Croatia's three consecutive extra-time matches — Denmark, Russia, England — became my test case: 143.6 km covered in the England semifinal, the tournament's highest. A Dhaka football site published the 3,000-word breakdown and paid me 4,000 taka. The first paid byline taught me that a model is only as honest as its assumptions. Since then every piece carries a methodology footnote. In cricket, the clearest application is T20 strike rate. A batter holds a 145 strike rate across 20 innings off 400 balls. The number sounds excellent. But if those innings are mostly 11-ball cameos in matches decided inside five overs, what does the strike rate actually mean? Weight by balls faced or innings context and the picture flips, because a low-pressure 25 in the last over and a 40 in the powerplay cannot sit on the same scale. I saw this in the 44-match notebook: a batter brilliant in the powerplay sees his average strike rate inflated by short, fast cameos at the death. The same applies to dot balls — a dot in the first over and a dot at the death are scored on the same scale even though the stakes differ enormously. A second structural problem sits in signing-on fees for free agents. My reporting suggests scrutiny operates differently when a large fee arrives as a signing bonus rather than a transfer fee. Transfer fees are public and therefore criticised; signing-on fees and agent payments bypass the core mirror of financial fair play, which is supposed to regulate a player's market value. A club paying a bigger signing bonus than any transfer fee is described as 'within budget' in the language of financial rules, while the market is more distorted than before. This is entering cricket too, through IPL auction pre-emption retention fees and franchise bonuses. The problem is not the number but its classification. Then there is officiating. VAR has not reduced controversy; it has moved it from the pitch to the review room and the grey zones of the rulebook. Cricket's third-umpire system faces the same problem. UltraEdge tracking, ball tracking, overthrows — each carries a trust question: which data point counts as 'edge', which bone as 'stump'? Cricket exposes this most cleanly at LBW, where the ball's path must be projected — assumption inside the model, decision outside it. I regularly see umpire's call as a boundary marker where data is consistently placed as judgement but is not judgement. That zone has created a new game: the review lottery. Some sides use reviews to relieve pressure, others to increase it; not a numbers application but an index-wise expenditure. That is the real controversy: a review system built for a right/wrong binary produces ever more half-right verdicts. The biggest lesson of this notebook survey came in 2026. During the global sports hiatus I coded the 83 Bundesliga matches played behind closed doors; the home win rate fell from 43.3% to 33.3%. Supporters read that number as atmosphere; I read it as a variable. I wrote it up as a sociology term paper, 'The Twelfth Man Is a Variable'; two journals rejected it, but a blog post of the same argument was read by 9,000 people. My error then was treating the home-win rate as the sole frame for evaluating inferential decisions. I later understood that the fixture structure in empty-stadium matches was not the same: scheduling, travel and density had all shifted under pandemic conditions. So the number is correlation, not causation. Now I always run a model under three different setups and see how much the result depends on assumptions. What does this notebook survey of cricket's easy numbers deliver? First, public metrics like rankings and strike rates do not match base rates; their scale weighting is missing. Second, local data — Rangpur, eleven-city stadiums, empty-seat matches — reveal patterns that larger-league media discard as noise, yet those patterns are the system's deep structure. Third, three sectors — scoring metrics, financial fair play, and referee review — share the same structural flaw: the number is defined, but the classification or contract behind it is never written down. That is precisely why the sport has entered an era of measurable misconception. There is a counter-angle that keeps me out of my own contrarian-for-its-own-sake trap. We assume more data disclosure means better decisions. My 44 matches and the 2026 model showed the opposite can hold. More data means more models, and each new metric arrives with its own assumptions; the decision-maker must learn what to discard. In Asian Cricket Council and domestic leagues this is stark: selection committees now weigh a batter across five metrics at once, and the metric that stays consistently positive is often the one with the smallest sample. That low-data, high-confidence trap is the biggest driver of selection controversy. In Bangladesh domestic cricket it cuts deeper, because ball-by-ball public data barely exists; the coach's notebook and franchise scout reports are the only 'dataset' — not public, not verifiable, and often presented in the press as 'data-driven decision'. The duality matters elsewhere. Does an empty ground make the game data-friendly or data-blind? The 83 empty-seat Bundesliga matches produced clean numbers, but the variables that generated them — scheduling, travel distance, breaks — were never separately coded. That is a warning against my own model elegance: messy reality is always more complex than the model, and analysis that refuses to admit this is promotion, not analysis. Empty grounds lower the noise, not the accountability of decisions. That is why my reports always name the assumption I have not tested, and where the result could move if I did. What should we watch in the regular season under this frame? My notebook says title races are decided by numbers absent from the press — runs conceded in the last five overs, over-breaks in the middle, the sectoral distribution of dropped catches — outside the easy numbers but directly affecting the table. Next round I will watch the side that takes early wickets but sees its economy rise in the fourth and fifth overs, and ask what its recent strike-rate number is really saying. If that number does not match base rates, I will audit the assumption before the model. And that is cricket's largest question: are we understanding the game through numbers, or are the assumptions behind them rewriting the game for us?