Player Efficiency Calculator
Calculate basketball player efficiency metrics from box-score stats and compare scoring, usage, rebounds, assists, and per-minute production.
Interested in Advertising?
Tell us more, and we'll get back to you.
Contact Us
Calculate basketball player efficiency metrics from box-score stats and compare scoring, usage, rebounds, assists, and per-minute production.
Tell us more, and we'll get back to you.
Contact UsCalculate basketball player efficiency metrics from box-score stats and compare scoring, usage, rebounds, assists, and per-minute production.
Use the same sample as blocks for block success rate.
Used for per-100 possession offensive and defensive rates.
Share the current inputs or ask ChatGPT to explain the calculation in context.
Player Efficiency Rating (PER) has revolutionized how we evaluate basketball talent, moving beyond basic box scores to provide a more complete picture of a player's contribution. Pioneered by ESPN's John Hollinger in the early 2000s, this broad statistical metric measures a player's per-minute productivity by accounting for positive contributions (scoring, rebounding, assists, steals, blocks) while also weighing negative actions (missed shots, turnovers, personal fouls).
| Player | Peak PER | Season |
|---|---|---|
| Giannis Antetokounmpo | 32.12 | 2019-20 |
| Wilt Chamberlain | 31.82 | 1962-63 |
| Michael Jordan | 31.71 | 1987-88 |
| LeBron James | 31.67 | 2008-09 |
| Nikola Jokic | 31.28 | 2021-22 |
| Stephen Curry | 30.99 | 2015-16 |
Use the player efficiency calculator as a working estimate for box-score production, usage, true shooting, and per-minute basketball output. It gives you a clean number from the values you enter, but the answer is only as good as those inputs. Small entry mistakes can look like big changes when the formula uses ratios, logs, or repeated conversions, so the first job is to make sure the starting values describe the same situation.
Start with points, rebounds, assists, steals, blocks, turnovers, shooting attempts, free throws, and minutes. Write those values down before you change anything. If you come back later and cannot remember what you entered, the result is hard to check and easy to misread. A quick note beside the calculation often saves more time than another round of guessing.
The main result is efficiency-style ratings that summarize production from the entered stat line. Read it together with the inputs, not as a standalone truth. A number with no context can be technically correct and still point you toward a poor decision if the starting assumptions were too broad or came from a different source.
Minutes matter because per-minute formulas can exaggerate tiny samples. Use real playing time, also games played. This matters because unit mismatches are quiet. The calculator will still return a number, but it may be answering a different question than the one you meant to ask.
For a quick check, use a simple example: A reserve with 8 points in 6 minutes may look strong per minute, but the sample still needs context. A rough mental estimate like that helps catch decimal slips, unit mix- ups, and copied values that landed in the wrong field. It does not have to be exact. It only needs to be close enough to flag an answer that makes no sense.
A common mistake is comparing players across roles without looking at minutes, pace, defense, and shot difficulty. When the result looks odd, check that first. Most surprising answers come from a plain input problem rather than from the math itself. If the inputs pass that first check, then look at units, rounding, and whether you selected the right mode.
Change one input at a time when you are exploring options. If you change several fields together, you may not know which one moved the result. A calculator is more useful when it helps you see cause and effect, and that only happens when the comparison is controlled.
Keep a copy of the first result before testing another scenario. That makes comparisons easier and keeps you from chasing a moving target. If the second result is better, you can explain why. If it is worse, you can go back to the earlier assumption without rebuilding the whole calculation.
A rim runner, a high-usage guard, and a defensive specialist can help a team in different ways even when one rating is higher. Those outside factors do not make the calculator useless. They explain why the answer should be treated as an estimate until it is checked against direct measurement, professional guidance, or real-world results.
The calculator cannot know screen assists, defensive positioning, play calls, matchup difficulty, and many off-ball actions. Those details may matter in real life, so treat the answer as a starting point for judgment rather than the end of the work. The cleaner the inputs, the more useful the estimate, but the estimate still has boundaries.
For repeat use, record game date, minutes, opponent, pace, role, and whether the stat line came from a single game or a full season. A short note is enough. You do not need a perfect log, but you do need enough detail to recreate the calculation later. That habit is especially helpful when you are comparing several days, properties, samples, products, or plans.
Try a second scenario when the input is uncertain: compare a per-game line with a per-36-minute view when players have very different minutes. The gap between the two answers is often more useful than either single answer by itself. A narrow gap means the estimate is stable. A wide gap tells you which input deserves better data.
Round the result to match the decision. Extra decimal places can make an estimate look more exact than it is. Use more precision for lab work, engineering notes, or financial records, and less for everyday planning. A rounded number that is honest about uncertainty is better than a long number with false confidence.
If you share the result with someone else, include the inputs and units. The answer alone can be misunderstood, especially when two people use different conventions or reference points. A shared result should say what was entered, what unit was used, and what assumption would change the answer first.
Use plain language beside the number. A note such as "based on the current estimate" or "assuming the entered values are correct" keeps the result from sounding more certain than it is. That wording is useful when the result will be copied into a plan, message, report, or checklist.
Look for outside constraints before acting. Time, budget, safety rules, medical guidance, local codes, equipment limits, and data quality can all matter more than a tidy calculation. The calculator can narrow the question, but it cannot remove every constraint around the decision.
Be careful with contract value, awards, or roster moves. In those cases, use the calculator for preparation and discussion, then rely on a qualified professional, official source, direct measurement, or written standard for the final call. That is not a weakness in the calculator. It is a normal part of using estimates responsibly.
When comparing two results, ask whether the difference is large enough to matter. A tiny change may be noise, rounding, or normal variation. A large change deserves a closer look at the input that caused it. The practical question is usually not whether two numbers differ, but whether that difference changes what you would do next.
If the calculator supports several modes, choose the mode that matches your question. Do not force a problem into the nearest-looking formula just because the fields are available. If the mode feels awkward, step back and write the question in one sentence before entering values.
Check the scale of the answer. A result that is ten times higher or lower than expected usually means a unit, decimal, or reference point deserves another look. Scale checks are quick, and they catch many errors before they turn into bad plans.
Save the assumptions that went into the calculation. Future you will care less about the exact button clicks and more about why those numbers made sense at the time. This is especially true when prices, schedules, measurements, or health details change over time.
A good calculator result should make the next step clearer. It might tell you what to measure again, which scenario to compare, or which question to take to a professional. If the result leaves you more confused, simplify the inputs and run a smaller version of the problem.
Use ranges when the input is a guess. Enter a low estimate, a middle estimate, and a high estimate. If all three answers point in the same direction, you can be more comfortable with the conclusion. If they point in different directions, the input needs better evidence before the result should guide action.
Keep the result close to the task at hand. The player efficiency calculator answers a specific question about box-score production, usage, true shooting, and per-minute basketball output. It should not be stretched into a promise about outcomes, safety, profit, health, performance, or future behavior. Good use means knowing what the calculation can answer and what still needs human review.
A PER of 15.0 is considered league average. Ratings above 20.0 indicate All-Star level performance, while ratings above 25.0 are considered MVP caliber. The highest single-season PER ever recorded was 32.12 by Giannis Antetokounmpo in 2019-20. For context, most NBA starters have a PER between 15.0 and 20.0, while role players typically fall between 10.0 and 15.0.
While PER measures efficiency and productivity, Usage Rate shows what percentage of team plays a player uses while on the floor. A high Usage Rate (>25%) means a player frequently ends possessions through shots, free throws, or turnovers. However, a high Usage Rate doesn't necessarily mean high efficiency - a player can have a high Usage Rate but low PER, indicating they use many possessions but don't convert them efficiently.
True Shooting Percentage (TS%) is a measure of shooting efficiency that takes into account field goals, three-point field goals, and free throws. It's considered more broad than traditional field goal percentage because it accounts for the added value of three-pointers and free throws. The league average TS% is typically around 58%. Elite shooters often maintain a TS% above 60%, while anything above 65% is exceptional, usually achieved by efficient big men who take high-percentage shots near the basket.
Minutes played put a stat line in context. A player with strong numbers in a very small sample may look excellent per minute, while a starter carrying a larger role has to sustain production against more defensive attention.
No single box-score rating captures all defense. Steals and blocks are easy to count, but positioning, rotations, screen navigation, and shot deterrence often matter without appearing clearly in the basic stat line.