A useful football statistic states what was counted, how it was calculated and when the source was checked. This guide provides a practical method for comparing African competitions without pretending their calendars, opponents or data coverage are identical. Official Ghanaian and Ugandan records serve as dated examples; the calculations describe observed results and do not predict a future match.
Freeze the source and the sample
The GFA report after Matchday 7 records 63 matches and 137 goals. Those numbers identify a specific reporting point, checked here on 23 October 2026. Save the URL, season, stage and review date before calculating anything. A later live table may contain more matches, so it should not silently replace the denominator in an older article. If a match is abandoned, awarded administratively or later replayed, follow the organiser’s treatment and document any change in the dataset rather than making an invisible editorial choice.
Show the arithmetic and round at the end
Dividing the cited 137 goals by 63 matches gives approximately 2.17 goals per match. This is a derived descriptive average, not a forecast that the next fixture will contain exactly that number of goals. Keep the original counts and perform rounding only for presentation. If comparing two reporting periods, calculate each average from its own numerator and denominator. Do not average two rounded averages unless they represent equal numbers of matches. A weighted calculation based on total goals and total matches preserves the contribution of each observation.
Compare common indicators
| Indicator | Calculation or evidence | Interpretation limit |
|---|---|---|
| Goals per match | 137 ÷ 63 ≈ 2.17 in the GFA snapshot | Observed sample, not a prediction |
| Home-win share | Home wins ÷ completed matches | Requires consistent venue classification |
| Points per game | Official points ÷ matches played | Not a replacement for league ranking rules |
| Clean-sheet rate | Matches with no goals conceded ÷ matches | Requires match-level records |
The table intentionally combines one verified numerical illustration with reusable definitions. It does not invent missing shot, possession or expected-goals data. If a league publishes only scores, the honest dataset contains scores and the measures that can actually be derived from them.
Account for games in hand
The official Uganda Premier League table observed during this review showed BUL with seven matches and Vipers with five. Unequal match counts complicate comparisons of total points or goals. Points per game can describe the current rate, but it cannot award points for unplayed fixtures or replace the official standings. Opponent strength and the home-away mix may also differ. Report the matches played beside every rate, then keep the official ordering as a separate field governed by the competition’s published rules.
Separate venue effects from explanations
Home results can be summarised by counts and rates, but those observations alone do not prove why the pattern exists. Travel, pitch familiarity, crowd support, team strength and scheduling are possible contextual factors requiring additional evidence. Record neutral venues and moved home fixtures consistently. Do not call every nominal home fixture a normal home environment if the game occurred elsewhere. A credible analysis distinguishes the descriptive statement, such as a higher observed home-win share, from a causal explanation that the available dataset cannot establish.
Respect differences between competition formats
CAF’s competition-regulations portal is a starting point for checking the rules relevant to continental events. A knockout run and a domestic league season offer different opponents, sample sizes and incentives. Keep normal-time scores, extra time and shoot-outs separate. Do not import a league points formula into a cup bracket or compare raw goal totals without acknowledging matches played. Expected goals require a defined model and suitable shot information; they cannot be reconstructed responsibly from a final score alone. Mark unavailable advanced metrics rather than assigning a plausible-looking value.
Check totals across related columns before publishing. In a complete league-match sample, wins plus draws plus losses for one team must equal its matches played under the chosen convention. For the whole competition, each match creates two team appearances. Confusing team appearances with matches would halve a goals-per-match calculation without changing the goal total.
Reproducible analysis checklist
- Save source URL, date, season and stage.
- Preserve raw counts before calculating rates.
- Show the denominator beside each metric.
- Round only the displayed result.
- Check games in hand and venue classification.
- Keep format and result conventions consistent.
- Separate observation from explanation or prediction.
Publish a short change note when an official correction affects the numbers. For a recurring dashboard, retain snapshots so readers can understand why an earlier article differs from today’s table. Reproducibility is not an elaborate technical feature: it begins with keeping the few inputs another person needs to repeat the calculation correctly.
Frequently asked questions
Does an average of 2.17 goals predict the next score?
No. It summarises the cited 63-match sample. Individual fixtures vary, and the average alone is not a predictive model.
Can points per game replace the official table?
No. It is a descriptive comparison when match counts differ. The organiser’s competition rules govern the actual ranking.
Can expected goals be calculated from the final score alone?
No. An expected-goals measure needs a defined model and appropriate shot-level inputs; a scoreline does not supply those details.
Sources and verification
- Ghana Premier League statistics after Matchday 7 — Ghana Football Association — 2026-10-23
- Uganda Premier League table and Rule 13 notice — Uganda Premier League — 2026-10-23
- CAF competition regulations — CAF — 2026-10-23