How does the MVP calculation work?

The CricHQ MVP Formula - explained        

CricHQ has developed a new MVP formula in conjunction with the New Zealand Cricket Players’ Association (NZCPA) to improve the accuracy of the rating formula for all players across all formats of the game.
The new formula shifts away from players being awarded MVP points based on the criteria used in the English first-class game, but now includes relevant data from all levels of the game.
The new formula recognises the format of the match and can quickly adapt to the situation of the game, rewarding players constantly through the game on events, as they happen.
This will ensure that all levels of cricket from International through to Junior Cricket will have a relevant rating system that fairly allocates points to players based on the game they are participating in.

Information on how the new formula calculates can be found below.
CricHQ have completed in-depth analysis and studies to gain vital MVP knowledge. We have analysed historical data of all International and First Class fixtures and from 100,000 recreational cricket matches on CricHQ.

The basis of MVP points allocation is that 25 runs has the same value as 1 wicket, therefore; 1 wicket = 2.5 MVP points & 10 runs = 1 MVP point

Think your matches MVP has been calculated incorrectly? Click here to see our FAQ on the most common causes.

Bowling Rules

Unassisted wicket (bowled/LBW/etc): 1 wicket = 2.5 MVP points. When the bowlers takes the wicket without the assistance of a fielder

Assisted wicket (caught/stumped/etc): 1 assisted wicket = 1.25 points to each participant, calculated on a 50/50 share of total MVP points available between bowler and catcher/stumper

Multiple wicket bonus: If the bowler gets more than one bowling wicket then they get a 10% bonus for every additional wicket. This is added on top of the bowler MVP points they already have.

Economy rate bonus: Bowlers are rewarded/penalised if their economy rates are lower/higher than their team's economy rate.

Par score bonus: If a batsman is dismissed for less than their par score, the negative points earned are converted to positive and shared amongst the wicket taker (s).

Base: Sum of bowling MVP points without bonuses.

Total: Sum of bowling MVP points including and bonuses.

Fielding Rules

Unassisted wicket (run out): 1 wicket = 2.5 MVP points to the person effecting the run out without assistance from any other fielder

Assisted wicket 
(includes run out assist): 1 assisted wicket = 1.25 points to each participant, calculated on a 50/50 share of total MVP points available between the first 2 people (limit 2 participants)

Multiple wicket bonus: If the fielder gets more than one fielding wicket then they get a 10% bonus for every additional wicket. This is added to any fielding MVP points they already have.

Par score bonus: If a batsman is dismissed for less than their required par score, the negative points earned are converted to positive and shared amongst the wicket takers. (i.e. All the points can go to the fielder or split 50/50 with the bowler)

Base: Sum of fielding MVP points without bonuses.

Total: Sum of fielding MVP points including bonuses.

Batting Rules

Runs base: 25 runs = 2.5 MVP Points

Strike rate bonus: Batsmen are rewarded/penalised if their strike rates are higher/lower than their team's strike rate.

Par score bonus: If a batsman scores higher than their batting positions "Par Score", they attract a bonus on all runs scored thereafter.

Total: Sum of batting MVP points including bonuses.

Batsman Strike Rate and Par Score Bonuses

The MVP formula balances the importance of strike rates and advancing the game within shorter matches, with batting time and achieving above par scores in longer matches. 

In a 50 over match both aspects are equally valuable with both attracting a 6% bonus, whilst a T20 match the SR bonus is 10% compared with a 2% bonus for par score.  Screen_Shot_2021-10-29_at_1.06.24_PM.png

Par Score Bonus

The below table provides indicative weightings to what each batting position contributes on average to the amount of total runs scored in an innings. 

These averages vary slightly depending upon the match type being played.

An example would be if a team scores 300 runs the batsman at number 4 would normally has the opportunity to score 12% of the team’s runs (36).

Think your matches MVP has been calculated incorrectly? Click here to see our FAQ on the most common causes.

Was this article helpful?
37 out of 44 found this helpful
Have more questions? Submit a request


  • 0
    Stephen Walker

    So if I understand this correctly, under this new MVP points system, dismissing an opening batsman or a number 11 earn the bowler the same points? That would make this completely wrong in my book and not worth looking at anymore.

  • 0
    Jimmy McLellan

    Hey Stephen,

    From what I read above the below comment answers what you are concerned about:

    Bowlers are compensated for getting out top order batsman, as opposed to lower order, through the Par Score bonus. So the quicker you get a top order batsman out before they get their expected Par runs, the more you are rewarded.

    An example would be getting an opening batsman out for 5, would give you plenty of bonus points. The more time it takes the less points you get. If you get them out after they already achieve the runs expected of them then you only get points for the wicket, as the damage is already done.

    The higher in the batting order the higher the expected par score from your innings would be.

    "Par score bonus: If a batsman is dismissed for less than their par score, the negative points earned are converted to positive and shared amongst the wicket taker (s)."

    I think this makes for a far better MVP platform, ensuring you are not rewarded for getting a top order batsman out, even though the team already let them smash 150 off you.

  • 0
    Stephen Walker

    If a first change bowler gets an opening batsman out 1st ball, but the opening bowlers have gone for plenty of runs, then the bowler will get few points. Doesn't seem right.

    Anyway it's not doing what they say anyway. Only one fielder got any points for catches. The other seven were just ignored.

    CricHQ is a great concept, but it remains full of bugs, many of which have been there for years!

  • 0
    Jimmy McLellan

    Always happy for discussion around such formula's, everyone has their own views on how they should work which is what makes them a great talking point.

    Always good to raise such issues with the CricHQ support team, else they will hang around until someone else does.

    Thanks for your interest!

  • 0
    Stephen Walker

    So let's forget the MVP formulas. When will the bugs get fixed?

    Examples: Look at game 440425

    Not all fielders got points for catches. Other games do. Inconsistant, even between innings.

    Download the match report.

    MVP page has bad formatting

    Look at the bowling page.

    After 1 over of 5 runs the RPO is 3.75!

    Quality control!

    I would love CricHQ if it was accurate.


  • 0
    Jimmy McLellan

    Just get in touch with the support team via the chat on the site, or email when you find anything you think is wrong. They would love to hear about this and get it sorted for you.

  • 0
    Sushreyo Misra

    Hi. This page was quite helpful for some work that I am doing. Basically, I am trying to develop a predictive model for International T20s based on historical data. I need a metric to score players per game and this definitely gives me a way forward. I have two questions though:

    1. In the current framework, isn't a bonus of 10% on economy rates a bit too low for T20s. If I understand this framework correctly, it gives huge weightage to wicket-takers. So a bowler taking 3-40 in 4 overs is likely to score more than someone taking 2-16 in 4 overs, whereas the latter may be more desirable. What are your comments on this?

    2. What exactly is the par score? Is it the average team total for all teams batting first, or with filters such as who is the opponent and where is the game being played? How exactly does this work?

  • 0

    This is some feedback we have had about MVP from a member:

    Dear CricHQ
    I think there is a problem on the AL Brown MVP - CricHQ > Leaderboards > MVP page/view:
    The problem is some of the metrics are resolving as negative values.  
    I appreciate this may currently be due to the way these metrics are calculated however from a mathematical, user experience, common sense, logical and intuitive point of view the algorithm for calculating these metrics should not be able to produce negative values as negative values implies it is possible to score a negative amount of runs, wickets or catches in one or more matches.
    For example it makes no sense that a player was able to score an average of -0.9 runs in 13 matches or -3.11 wickets in 9 matches.
    My suggestion would be to change the calculations so that it is not possible for it to produce negative values for these metrics regardless of number of matches played. 
    I hope you find this end user feedback is helpful.
    Kind Regards
  • 0

    Unfortunately this 'One size fits all' MVP calculation doesn't work very well for junior formats from Y5/6 and below, as they are T20 games where the kids have to bat in partnerships only lasting 4-5 overs, meaning they will generally only face 12 to 15 balls at best. To say 25 runs in this context is the same as getting 1 wicket seems a bit far fetched. I would think 20 runs should give you a bonus point and a strike rate bonus should be easier to obtain, given the small amount of balls a batsman will face at this level.

  • 0
    david aitkenhead

    Dan is right.  For T20 with a 9 ball grace period, retiring at 18 balls, net economy rate (runs conceded less 3 for each wicket taken) is the only thing that matters for bowlling statistics.  The number of wickets can be almost irrelevant, except as producing a -3 penalty for the batting team (although I note this is now changed to +3 for the bowling team, which is the same).  CricHQ should treat a wicket the same way it is in a game i.e. minus 3 for the bowler, which then becomes part of their economy rate.  

    This is slightly inconsistent for dismissals between the 9th and 18th ball, but I think -3 is still a better treatment for these dismissals than a whopping 25 runs as is the case now.

    The current 25 run treatment means that a bowler could get smashed all around the park, bowl all wides and no-balls, basically lose the game for their team, but still end up on MVP due to taking a couple of wickets.  This might be ok in a test match, but not in junior cricket with grace periods. 



Please sign in to leave a comment.







CRM + Reporting



Social + Profile

Match Centre




Terms & Conditions

Contact Us


 Wellington NZ