Goal
Calculate save percentage, shots not saved, concession percentage, and shots faced per save from a defined shot sample.
Goalkeeper Save Percentage Calculator
Calculate save percentage, shots not saved, concession percentage, and shots faced per save from a defined shot sample.
Key facts
- What it does
- Calculate save percentage, shots not saved, concession percentage, and shots faced per save from a defined shot sample.
- Formula
Shots not saved = shots faced − saves; save percentage = saves ÷ shots faced × 100; concession percentage = shots not saved ÷ shots faced × 100.- You enter
- Saves · Shots on target faced
- Worked example
- Save percentage = 75%, six shots not saved, and concession percentage = 25%.
A clearer path to an answer
From your question to a useful result
This page keeps the calculation transparent: define the goal, enter the matching values, inspect the method, and decide what the result means in your situation.
Inputs
Saves · Shots on target faced
Method
Shots not saved = shots faced − saves; save percentage = saves ÷ shots faced × 100; concession percentage = shots not saved ÷ shots faced × 100.
Next step
Calculate, review the assumptions below, then compare a related tool when the decision needs more context.
Goalkeeper Save Percentage Calculator
Calculate save percentage, shots not saved, concession percentage, and shots faced per save from a defined shot sample.
Open the Goalkeeper Save Percentage Calculator pageMore sports tools
Download PDFDownload Word (.doc)
Result
Enter your values above and choose Calculate to see the result here.
Calculation map
Follow the path from input to answer
01
Inputs (2)
- Saves Ready
- Shots on target faced Ready
02
Formula
Shots not saved = shots faced − saves; save percentage = saves ÷ shots faced × 100; concession percentage = shots not saved ÷ shots faced × 100.
Bounded, transparent calculation
03
Result
- Calculate to preview the result.
Recent runs
Your recent runs stay in this browser session only.
Formula, assumptions, and example
Formula: Shots not saved = shots faced − saves; save percentage = saves ÷ shots faced × 100; concession percentage = shots not saved ÷ shots faced × 100.
This calculator describes a defined sample of saves and shots on target faced. It checks that saves do not exceed shots, reports both sides of the rate, and avoids inventing a percentage when no shots were faced. Sport-specific providers may define events differently, so the event definition and competition must stay with the result.
- Saves and shots faced are whole-event counts from the same sample.
- Every save is counted against a shot on target under the chosen provider's definition.
- A shot not saved is computed as shots faced minus saves.
- Zero shots faced produces a displayed rate of zero rather than a division-by-zero claim.
- Penalty shootouts, own goals, deflections, blocked shots, and rebounds follow the chosen data provider's rules.
- The result is descriptive and does not adjust for shot location, difficulty, match state, or team defence.
- A season, match, tournament, training session, or video sample should not be mixed without being labelled.
- The percentage is not a complete measure of an athlete's quality or future performance.
Worked example: Save percentage = 75%, six shots not saved, and concession percentage = 25%.
Displayed input contract
- Saves · minimum 0 · maximum 1000000000
- Shots on target faced · minimum 0 · maximum 1000000000
The displayed limits are checked before the handler runs. Model-specific domain checks may also reject impossible or non-finite inputs.
Methodology: This calculator follows the WorldCalculate input, formula, precision, and boundary policy. Read the official methodology.
Calculator usage statistics
Usage of this calculator and related tools
This section counts anonymous successful Calculate submissions, not unique visitors. Counts and top tools appear only when trusted aggregate data is available; country analysis is shown only under the same condition and reporting threshold.
Total successful calculations
Top tools
Country analysis
Most-used tools
Where usage is reported
Answer-first guide
How to use the Goalkeeper Save Percentage Calculator for a real question
Calculate save percentage, shots not saved, concession percentage, and shots faced per save from a defined shot sample. Start with one clearly defined goal, enter values in the units shown, and keep the result attached to the assumptions below.
What this answers
This tool is useful when your question includes save percentage calculator, goalkeeper save percentage, hockey save percentage. It returns the outputs declared in the calculator contract rather than a live quote, approval, diagnosis, or professional sign-off.
What you enter
Saves · Shots on target faced. Keep the same time period, unit system, and currency wherever the form requires comparable values.
How to check it
Run the worked example first, compare its output with the page's example, then change one input at a time. This makes an unexpected result easier to trace to a unit, boundary, or assumption.
Three checks before you rely on the answer
- Match the question. Confirm that the result means the quantity you need, not a similar-sounding percentage, balance, rate, or estimate.
- Match the inputs. Use the requested units and period, and read each hint before replacing the example values with your own.
- Read the boundary. Review the assumptions and limits. Saves and shots faced are whole-event counts from the same sample.
Need a wider view? Browse Sports Statistics Calculators or compare the related tools below. The WorldCalculate methodology explains how formulas, examples, limits, and revisions are reviewed.
How to use the Goalkeeper Save Percentage Calculator
- Enter Saves (saves).
- Enter Shots on target faced (shots).
- Choose Calculate and read the result panel.
- Use Download PDF or Download Word to save a result sheet.
Formula
Shots not saved = shots faced − saves; save percentage = saves ÷ shots faced × 100; concession percentage = shots not saved ÷ shots faced × 100.
This calculator describes a defined sample of saves and shots on target faced. It checks that saves do not exceed shots, reports both sides of the rate, and avoids inventing a percentage when no shots were faced. Sport-specific providers may define events differently, so the event definition and competition must stay with the result.
Worked example
Save percentage = 75%, six shots not saved, and concession percentage = 25%.
Assumptions and limits
- Saves and shots faced are whole-event counts from the same sample.
- Every save is counted against a shot on target under the chosen provider's definition.
- A shot not saved is computed as shots faced minus saves.
- Zero shots faced produces a displayed rate of zero rather than a division-by-zero claim.
- Penalty shootouts, own goals, deflections, blocked shots, and rebounds follow the chosen data provider's rules.
- The result is descriptive and does not adjust for shot location, difficulty, match state, or team defence.
- A season, match, tournament, training session, or video sample should not be mixed without being labelled.
- The percentage is not a complete measure of an athlete's quality or future performance.
Who uses this calculator?
- Goalkeepers and coaches reviewing a defined match sample
- Sports students learning rate statistics
- Analysts comparing clearly labelled provider data
When is it useful?
- Calculate a goalkeeper's save rate from saves and shots on target.
- Show the complementary concession rate and event count.
- Check a box-score percentage before publishing or discussing it.
Context and background
Why sports rates need definitions
A sports percentage or rate depends on attempts, outs, minutes, shots, or another denominator. Matching that definition is necessary before comparing players, teams, or seasons.
Box-score analysis became more useful as raw events were expressed as rates that account for opportunities. These tools show the denominator so the result remains tied to the supplied record.
Research and review
How this guide was researched
Researched by Hassan ALRowaie, Founder and editorial researcher at WorldCalculate.
This guide follows the live calculator's declared inputs, formula, worked example, assumptions, validation boundaries, and source-backed methodology. The review date describes editorial review of the calculator explanation; it is not a promise that external facts or rates remain current.
A save percentage is a simple ratio only after the shot events have been defined consistently. This calculator takes saves and shots on target faced, checks that the numerator cannot exceed the denominator, and reports the complementary shots not saved and concession percentage. It is useful for a match note, a training review, or a statistics lesson, but the number must remain tied to the sport, competition, provider, and sample definition that produced the counts.
What the rate measures
The basic save percentage is the number of credited saves divided by the number of shots on target faced, multiplied by 100. If a goalkeeper makes 18 saves from 24 shots on target, the rate is 18÷24×100 = 75 percent. The complementary count is six shots not saved, and the complementary percentage is 25 percent.
The arithmetic describes the recorded events; it does not describe every action in a goal or crease. A goalkeeper may affect a play without receiving a save, and a shot may be counted or excluded according to the competition provider. Define the events before calculating so a neat percentage does not hide an inconsistent denominator.
Use a matching numerator and denominator
The saves and shots faced must describe the same sample. Do not combine a goalkeeper's saves from one match with team shots on target from another, or use a season numerator with a partial-season denominator. Label the date range, competition, team, opponent, and data source beside the two counts.
The denominator is particularly important. Shots off target, blocked before reaching the goalkeeper, crosses, and harmless touches may not belong in shots on target faced. The provider's definitions take priority. If two providers disagree, calculate both with their labels rather than averaging numbers that were created by different event rules.
The complementary numbers
Once saves and shots faced are defined, shots not saved are shots faced minus saves. The concession percentage is that count divided by shots faced. Reporting both percentages is a useful check because they should add to 100 percent when the denominator is greater than zero. The page also reports shots faced per save as a descriptive ratio.
A ratio is not a quality score by itself. Six shots not saved can mean six goals, six rebounds, an own-goal classification, or another provider-specific event. Confirm the label before writing the result into a match report. The calculator uses plain event arithmetic and does not reinterpret the provider's record.
Zero shots faced
When a goalkeeper faces zero shots on target, save percentage is mathematically undefined because the denominator is zero. This interface displays zero for the rate so a page can render a bounded result, but that display must not be described as a genuine 0 percent performance. The event count and the zero-denominator condition are the important facts.
For a report, write no shots on target faced or not rated rather than ranking the goalkeeper at zero. The calculator's note and the surrounding data record should preserve that distinction. Zero is a display convention for a missing rate, not evidence of a failed save.
Sport and provider differences
The phrase save percentage is used in several sports, but the event definitions can differ. Ice hockey statistics may include shots on goal and goals against in an official glossary. Soccer, field hockey, lacrosse, handball, and other sports can use different conventions for deflections, own goals, penalty situations, and team saves.
This page does not force a single sport rule onto every country. Select a provider, cite its glossary or match report, and keep the sport in the title of your analysis. If a league publishes a formal formula, follow that formula even if a local shorthand uses the same name.
Worked match example
Suppose the official match record credits 18 saves and 24 shots on target faced. Shots not saved are 24−18 = 6. Save percentage is 18÷24×100 = 75 percent. Concession percentage is 6÷24×100 = 25 percent, and shots faced per save is 24÷18 = 1.333 shots per save.
The example is complete only if the 18 and 24 came from the same match and the same definitions. If an analyst adds a video-coded save that the official provider did not credit, the numerator changes and the record should say why. Reproducibility matters more than making the percentage look higher or lower.
Season aggregation
For a season, add saves and shots faced across the matches first, then calculate the rate from the totals. Averaging each match's percentage gives every match equal weight and can differ from the true event-weighted season rate. A match with two shots should not count the same as a match with thirty shots when calculating the combined event rate.
Keep the aggregation rule visible. If a data feed already supplies a season percentage, compare it with the total-count calculation and investigate differences rather than silently replacing one. Rounding each match before adding can also create a small discrepancy; use whole event totals where available.
Shot difficulty and context
Save percentage does not adjust for shot distance, angle, traffic, rebound danger, breakaways, screens, player skill, or match state. Two goalkeepers can face the same number of shots but very different difficulty. A raw rate is therefore a starting descriptive statistic, not a complete evaluation.
Add context with care. A coach may pair the rate with video, shot location, expected-goal models, rebound control, communication, and team defensive actions. The calculator should remain one transparent column in a broader review rather than becoming a label attached to a person.
Match state and penalty situations
Penalty shots, shootouts, power plays, empty-net situations, and stoppage-time events may be recorded differently by competitions. Decide in advance whether they belong in the numerator and denominator. Do not mix regular-play and shootout events unless the chosen statistic explicitly requires that aggregation.
A clear data dictionary can list included event types, excluded event types, and treatment of deflections or own goals. When a competition rule changes, version the definition. A stable formula applied to a changing event definition does not create a stable statistic.
Training and small samples
A training session may have only a few shots, so one event can move the percentage dramatically. A perfect 3-for-3 rate is not equivalent to a perfect 30-for-30 rate in information content. Record the denominator beside the percentage and avoid ranking tiny samples without a minimum-volume rule.
A coach can use the raw rate to start a conversation about technique or decision-making, then inspect the video and shot context. The page does not provide confidence intervals or shrinkage estimates because those require a study design and a chosen statistical model. Small-sample uncertainty should be acknowledged explicitly.
Rounding and display
The underlying ratio should be calculated from integer counts and rounded only for display. Eighteen divided by twenty-four is exactly 0.75, while other samples may produce a repeating decimal. Use enough display precision for the purpose, but do not imply that a percentage such as 83.3333 percent is more accurate than the event coding.
If two reports disagree by a tenth of a percentage point, check whether one rounded before aggregation. If they disagree by several points, inspect the denominator and event definition. A calculator can reveal arithmetic differences, but a source audit explains data differences.
Comparing goalkeepers fairly
Before comparing two rates, align sport, competition, season, minutes or games, shot-count definition, and aggregation rule. A goalkeeper with a high rate from a small or easy sample may not be comparable with one facing a high volume of difficult shots. Use the denominator and context beside every rate.
Avoid treating the percentage as a prediction. Performance changes with opponents, defence, injuries, coaching, fatigue, and random variation. A fair review may use repeated samples and context-adjusted metrics, with the raw save percentage retained as a simple audit trail.
Data collection and video review
If official counts are unavailable, a video coding protocol should define what counts as a shot on target, a save, a goal, a deflection, and an out-of-play event. Have a second reviewer code a subset and reconcile disagreements. Record the video source and timestamp so a disputed event can be checked.
Do not mix manually coded counts with official counts without marking the boundary. Manual review can be valuable, but it introduces observer decisions. The rate is only as reproducible as the event list underneath it.
Privacy and athlete records
A performance statistic may be public, but a training log can contain personal, youth, health, or employment information. Store the result according to the team's or institution's rules and avoid entering unnecessary identifying data into a shared calculator. The page needs two counts, not a person's full profile.
When sharing a result, state the sample and source with a clear method description. A transparent definition protects athletes better than a sensational percentage detached from its context. The calculator is an arithmetic aid, not a scouting or medical decision system.
Common mistakes
Common mistakes include using total shots instead of shots on target, counting team saves against one goalkeeper, adding goals to saves, and dividing by shots faced after a different provider's exclusions. Another mistake is averaging match percentages when the question asks for a season event rate.
If saves exceed shots faced, the inputs are inconsistent and the handler rejects them. Fix the event table rather than forcing the number into a percentage. If shots faced is zero, preserve the no-rate meaning rather than reporting a misleading zero-quality conclusion.
A decision-ready match note
A useful match note states the sport and competition, date, provider, saves, shots on target faced, save percentage, shots not saved, and any special treatment for penalty or shootout events. Add the denominator next to the percentage so a reader can judge the sample size immediately.
If a coach or analyst needs a deeper decision, attach video and contextual metrics instead of asking this one ratio to answer every question. The calculator's job is to make the basic rate correct, bounded, and easy to reproduce.
Final checklist
Confirm that saves and shots faced are whole counts from the same sample. Confirm the event definition, competition, provider, and aggregation rule. Enter the values, inspect the complementary count and rate, and check whether zero shots or a small sample changes the interpretation.
Then report the percentage with its denominator and context. Use it as one descriptive measure, not a verdict about an athlete. A clear definition and an honest sample size are more valuable than a decimal with excessive precision.
Minutes and exposure
A rate based on shots faced does not show how long a goalkeeper played. A substitute may face few shots in a short appearance, while a starter may face many over a full match. If exposure matters, report minutes or matches separately and do not pretend that shots faced alone is a playing-time measure.
For a comparison, align the time window and identify partial appearances. A coach may care about rate per shot, rate per minute, or workload, but each is a different question. The calculator remains focused on the event-defined save percentage.
Expected goals and shot quality
Shot quality can vary widely by distance, angle, defensive pressure, body part, and rebound status. A raw save percentage weights every counted shot equally. An expected-goals or shot-quality model may add context, but its assumptions and training data must be documented separately.
Do not retrofit a quality adjustment into the two input fields. If a team uses an expected-goals model, keep the raw saves and shots as the audit layer and place the modelled metric beside it. This preserves the ability to explain where a difference came from.
Rebounds and second actions
A first save may produce a rebound that creates another shot. Some providers count the events in a way that makes a simple save percentage difficult to interpret, especially when the same possession contains several actions. Use the official event record or a written coding rule rather than trying to infer the denominator from a highlight clip.
For video analysis, mark the possession and the shot event separately, then decide whether the chosen statistic treats a rebound shot as a new shot faced. A consistent rule is more valuable than a larger count that cannot be reproduced.
Aggregating across competitions
A goalkeeper may play in league, cup, international, school, or training matches with different event definitions and quality levels. Do not merge them automatically. Calculate separate rates or create a documented common data dictionary before combining the counts.
If an organization needs one overall number, sum compatible event counts rather than averaging displayed percentages. Keep competition and opponent fields in the source table so a later reviewer can rebuild or filter the aggregate.
Confidence and minimum samples
A percentage from ten shots is noisy. A formal analysis can use a binomial confidence interval or a hierarchical model, but the correct method depends on the purpose and sampling design. This page does not choose a minimum sample or print an interval because those decisions belong to the analyst.
A practical dashboard can show the denominator beside the rate and flag small samples for review. That is often more informative than sorting athletes by a percentage alone. The count of opportunities is part of the result, not a footnote.
Provider reconciliation
When two feeds disagree, compare the match report, event timestamps, and glossary definitions. Differences may come from a blocked shot, a deflection, a penalty event, an own goal, or a correction after the match. Recalculate from the selected provider rather than silently blending values.
Keep a version date for downloaded data. Sports databases can correct historical events, and a rate may change without a new match being played. A transparent source note protects users from treating an old display as a permanent fact.
Athlete development conversations
A coach can use the rate to open a conversation about a defined group of shots, then ask what the video shows: positioning, set position, sight lines, rebound control, communication, or team pressure. Avoid attaching a person's identity or future to one number.
Use repeated, comparable samples and invite the athlete to review the event definition. The calculator is most constructive when it supports a shared question and a practical next step, not when it is used as a public ranking without context.
Publishing the result
A public result should state the sport, sample, numerator, denominator, source, date, and rounding. If the rate is not official, label it as manually coded. If shots faced are zero, write no qualifying shots rather than publishing a zero as if it were a performance value.
Use a stable link or archive for the source where possible and retain the raw count table internally. Readers should be able to understand what the percentage means without guessing whether it includes shootouts, training, or another goalkeeper's events.
Team versus individual events
Some sports record a team save or a defensive action that cannot be assigned cleanly to one goalkeeper. Confirm that the numerator belongs to the same individual as the denominator. A team total divided by one player's shots faced can produce a mathematically valid but meaningless rate.
When responsibility changes during a match, split the sample by goalkeeper or use the provider's official allocation. Keep substitutions and time intervals in the source table. The page cannot infer who was responsible for an event from two total counts.
Penalty and shootout treatment
A penalty event may be included in a match record, excluded from a standard statistic, or reported in a separate category. Shootouts can have their own rules and should not be added casually to regular-play shots. Choose the competition definition before entering the counts.
If a report presents both regulation and shootout numbers, calculate them separately first. Combining them may be useful for a specific question, but state the decision and keep the two denominators visible. A single percentage should never hide a material change in event type.
Opponent and venue context
A rate can change with opponent quality, venue, surface, weather, travel, and defensive system. These factors do not change the arithmetic, but they change what a comparison means. Keep opponent and venue fields in the dataset even when the calculator only needs two counts.
For development, compare like with like where possible and use a broader sample for conclusions. A high rate against one opponent is an observation, not a guarantee against another. The number should start a review of events rather than end it.
Data corrections and audit dates
Official match feeds can be corrected after a game. Save the source date and update the calculation when the provider changes an event. If a historical rate changes, explain whether the numerator, denominator, or event definition changed.
Do not overwrite an old published number without an audit note if people may have relied on it. A small version history preserves trust and makes the arithmetic easy to reconstruct. The calculator's simple formula is stable even when its source counts are revised.
A useful analyst worksheet
A worksheet can include match identifier, goalkeeper, minutes, saves, shots faced, goals, penalty events, provider, and notes. The calculator fills the rate columns from the compatible totals. Add a minimum sample flag and a context link so a reader can inspect the events behind a surprising result.
For a season report, present both event-weighted totals and a distribution of match-level rates when appropriate. Those views answer different questions. Do not use one average to replace the other without stating the aggregation rule.
Communicating a fair comparison
When sharing a rate with athletes, families, supporters, or readers, explain the denominator before the ranking. Say how many shots were faced, which events were included, and whether the number is official or manually coded. A percentage without that context invites the reader to assume more certainty than the data can support.
Use neutral language for small or unusual samples and separate descriptive reporting from coaching decisions. The calculator can make a rate reproducible, but fairness comes from the surrounding definition, consent, and context.
Close the analysis loop
After a review, keep the raw counts, the selected definition, the displayed result, and the action that followed. If the team changes its event-coding rule, start a new version rather than comparing incomparable historical values. A small audit trail helps future analysts understand why the percentage changed.
The best use of this tool is modest and clear: calculate one defined rate, show its denominator, connect it to the source, and combine it with richer evidence when a decision matters. That approach protects both the statistic and the person described by it.
Frequently asked questions
What is the Goalkeeper Save Percentage Calculator?
Calculate save percentage, shots not saved, concession percentage, and shots faced per save from a defined shot sample.
What is the formula for the Goalkeeper Save Percentage Calculator?
Shots not saved = shots faced − saves; save percentage = saves ÷ shots faced × 100; concession percentage = shots not saved ÷ shots faced × 100. This calculator describes a defined sample of saves and shots on target faced. It checks that saves do not exceed shots, reports both sides of the rate, and avoids inventing a percentage when no shots were faced. Sport-specific providers may define events differently, so the event definition and competition must stay with the result.
What do I need to use this calculator?
Enter Saves, Shots on target faced, then choose Calculate.
What are the limits of this calculator?
Saves and shots faced are whole-event counts from the same sample. Every save is counted against a shot on target under the chosen provider's definition. A shot not saved is computed as shots faced minus saves. Zero shots faced produces a displayed rate of zero rather than a division-by-zero claim. Penalty shootouts, own goals, deflections, blocked shots, and rebounds follow the chosen data provider's rules. The result is descriptive and does not adjust for shot location, difficulty, match state, or team defence. A season, match, tournament, training session, or video sample should not be mixed without being labelled. The percentage is not a complete measure of an athlete's quality or future performance.
Methodology
This calculator is part of the WorldCalculate library. Its formula, example, assumptions, input bounds, and output formatting follow the official methodology.
Use this calculator as part of a bigger plan
These WorldCalculate collections connect this tool with related questions while keeping each calculation separate and transparent.