Offensive Rating
- Created by
- Renato Passos, Eng. de Software
- Reviewed by
- Renato Passos, Eng. de Software
Last updated: Apr 18, 2026
About this calculator
The Offensive Rating calculator estimates a basketball team’s offensive efficiency. It converts the total points scored by dividing by the number of possessions taken and multiplies the result by 100. The resulting value indicates how many points a team averages per 100 possessions, making it easy to compare performance across teams and seasons.
To obtain the offensive rating, simply enter the team’s total points and the number of possessions used during the period. The algorithm performs the division and applies the factor 100, following the formula: (Points ÷ Possessions) × 100. The tool is automatic and only requires basic data, no manual calculations.
This metric is valuable for game analysis, team performance evaluation in leagues, and designing game strategies. Coaches, analysts and fans can compare offensive productivity among teams in the same division or track progress over a season.
Be mindful of sample size; a small number of games can skew the rating. Accuracy also depends on the quality of possession and point data. Avoid making single decisions based solely on this metric without considering other indicators such as shooting efficiency, rebounds and fouls.
Frequently asked questions
What does the calculated value represent?
It indicates the average points a team scores per 100 possessions, reflecting offensive efficiency.
What data do I need to enter?
Only the total points scored and the number of possessions used during the chosen period.
Can I use the calculator for a single game or an entire season?
Yes, it works for any time frame, as long as the input data are accurate.
How should I interpret a low or high rating?
A high rating shows strong offensive productivity; a low rating may point to attacking difficulties or poor possession efficiency.
Do I need to adjust for game pace or period?
The calculation already accounts for pace using possessions, but comparisons across teams require context and game count awareness.