Every figure on this site is built from two spreadsheets the club maintains: a match-by-match record of batting, bowling, fielding and wicketkeeping, and a separate sheet tracking Man of the Match and Player of the Month. Nothing is estimated or guessed at the point of entry — it's transcribed from real scorecards.

Every time the data is updated, new records are checked against what's already here rather than just appended — catching duplicate rows, inconsistent opponent names (e.g. "Welton" vs "Welton CC"), and the odd typo'd date, before anything is merged in.

Ball-by-ball data wasn't recorded for a meaningful share of older innings — particularly before 2022. Rather than showing those as a misleading Strike Rate of 0 (which would drag down every average that includes them), the balls faced are estimated from that player's own genuine career pace, but never allowed to exceed the real number of balls actually bowled in that innings — so the estimate always stays consistent with the true match record. Innings built this way are flagged internally, and a genuine duck always keeps its real Strike Rate of 0 regardless.

Cricket records overs in base-6 notation — 4.3 means 4 overs and 3 balls, not a true decimal. Every total on this site (career overs bowled, economy rates, strike rates) is built by converting to a real ball count first and only turning it back into the 4.3-style notation for display, so combining figures across matches never produces an impossible value like 7.7 overs.

The 2026 season is complete, so the League Table page now shows final standings only — final points, final position, and whether the club was promoted or relegated. Earlier in the season this page ran a live promotion/relegation simulation that updated automatically as results came in; that's been retired now there's no more season left to project.

Both 1st and 2nd XI are combined into one club season. Every player is classified by role from their own numbers that year — genuine wicketkeepers need to have kept in at least 3 separate matches, not just filled in once; everyone else is split into Batter, Bowler or All-rounder by how much of each they actually did.

To make the team at all, you need to have played a meaningful share of that season's matches (scaled to how much cricket was actually played that year, so shorter seasons aren't unfairly emptied out), and to have cleared a genuine output bar for your role — batters need both a real run total and a real average, not just a padded total built from a lot of failures; bowlers need a real wicket haul; all-rounders need a genuine amount of both.

The XI is then filled to a normal cricket template — 5 batters, 1 keeper, 2 all-rounders, 3 bowlers — and shown in batting order, not ranked by score.

Up to the end of 2026 (and any earlier seasons added later), awards come from the club’s Impact formula: a weighted score of 60% batting, 30% bowling and 10% fielding. These awards are final and are never recalculated.

From 2027, Man of the Match is decided by Match Value: each contribution is measured in runs gained for Hessle, judged only against that match. Batters get their runs, with a bonus or penalty for scoring faster or slower than the match; bowlers get 15 runs per wicket plus runs saved against the match run rate; a catch or stumping earns a quarter of a wicket and a run-out half. Ties go to most wickets, then most runs.

Player of the Month goes to the highest Match Value total across all XIs, three days after the month ends. Man of the Match can still change for three days after a game, so scorers’ corrections count; after that every award is kept — a later scorecard correction never changes a winner.

Captains can still overrule either award if a performance the scorecard can’t show deserves it.

WAR is borrowed from baseball. It asks one question about each player: how many extra wins did they give the team compared with a replacement-level player — the kind of player the club could always find to fill a spot at short notice?

Every contribution — batting, bowling, fielding and wicketkeeping — is first measured in runs above replacement, added together, then converted into wins. A positive WAR means a player added value over a stand-in; a negative WAR means a stand-in would likely have done better over the same amount of cricket.

Replacement level is set relative to the club’s own players, not an outside benchmark. A replacement batter scores at 70% of the average strike rate and gets out 30% more often per ball. A replacement bowler concedes 30% more runs per over and takes wickets 30% less often. Fielders and keepers are expected to take dismissals at 70% of the average rate.

1st and 2nd XI are measured separately. The two teams play at different levels — the 1st XI scores noticeably faster, for example — so each player is compared with replacement level for the team they were actually playing for that season. A player who appears for both XIs gets credit from each, judged against the right peer group.

Scoring: runs actually scored, minus the runs a replacement batter would have made from the same number of balls.

Wicket preservation: in cricket, getting out costs the team one of only ten wickets, however quickly you were scoring. So batters are also credited (or charged) for being dismissed less (or more) often than a replacement batter would be over the same balls faced. Without this, a batter averaging 60 and one averaging 30 at the same strike rate would be valued identically.

Containment: runs saved compared with a replacement bowler’s economy rate across the same overs.

Wicket-taking: wickets taken above what a replacement bowler would manage in the same overs, each valued at the season’s average runs per wicket. Baseball has no real equivalent here — a cricket innings can end early if wickets fall — so this is counted separately rather than left to show up only indirectly through economy. It is what lets a big wicket-taker with an ordinary economy rate still score highly.

Fielding: catches and run-outs, compared with what a replacement fielder would take in the same number of overs fielded (not matches — a 45-over innings offers far more chances than a 17-over one). Run-outs count 1.5× a catch, as they rely less on the bowler creating the chance.

Wicketkeeping: keepers are compared with a keeper-specific baseline (around 1.5 dismissals per match kept), not the general fielding rate, because the keeper is involved in every ball. Only dismissals above that expected rate count as genuine extra value.

Runs above replacement are converted into wins using a runs-per-win figure of …, derived from the club’s own results: it measures how much one extra run shifts the chance of winning a typical match, using every decided match on record. It is deliberately fixed across all seasons and both XIs — recalculating it for a single season gives a wildly unstable number whenever that season over- or under-performs its run difference.

Player of the Season (one per XI) goes to the highest WAR that season. Most Improved goes to the biggest rise in total WAR from one season to the next.

WAR here is a from-scratch adaptation, not an official statistic. The replacement thresholds, the 1.5× run-out weighting and the per-wicket value are reasonable choices rather than the only correct ones, so small differences between players in the middle of the table shouldn’t be over-read.

It also only sees what the scorebook records — it can’t credit a match-winning partnership in a tight chase more than the same runs in a dead game, or a dropped catch that cost a match.