TH Tector betting stats, splits & projections
Every figure below is counted from stored ball-by-ball deliveries — no estimates, no averages copied from elsewhere. Splits with fewer balls behind them are marked LOW sample and carry less weight in the model.
Record by format
Formats are never pooled: a twenty-over record tells you nothing about fifty-over scoring, so they are modelled and shown separately.
| overall | T20 | 7 | 121 | 85 | 17.3 | 142.4 | 23.5 | 35.3 | LOW |
Against each opponent
Head-to-head record by format. Small head-to-head samples move the model very little — read the sample column before leaning on a line here.
| Bangladesh | T20 | 3 | 87 | 54 | 29.0 | 161.1 | 27.8 | 29.6 | LOW |
By venue
Ground-by-ground record. Venue effects are real but slow to prove, so grounds with few balls are shown for transparency rather than used as evidence.
| Bir Sreshtho Flight Lieutenant Matiur Rahman Stadium, Chattogram | T20 | 3 | 87 | 54 | 29.0 | 161.1 | 27.8 | 29.6 | LOW |
By country
Conditions vary more by country than by ground; this is the broader pitch-and-conditions view.
| Unknown | T20 | 7 | 121 | 85 | 17.3 | 142.4 | 23.5 | 35.3 | LOW |
By match phase
Powerplay, middle overs and death. Phase splits drive the simulated scoring rate ball by ball.
| powerplay | T20 | 6 | 98 | 62 | 24.5 | 158.1 | 29.0 | 38.7 | LOW |
Against pace and spin
Record against each bowling type faced, rolled up when a finer category has too few balls.
| PACE | T20 | 6 | 86 | 56 | 21.5 | 153.6 | 26.8 | 39.3 | LOW |
How these splits are used
The same aggregates feed the ball-by-ball simulation behind every projection: format baselines, phase scoring rates, the bowling types a batter will face and the expected attack. See the current match projections on the cricket betting hub and the model's tested record on the cricket model performance page.