What is MOS and how is call quality measured?
When you want to know whether your connection can handle a call, checking three or four numbers separately is not practical. That is what MOS (Mean Opinion Score) is for: a single score that sums up how a call would sound.
Where MOS comes from
MOS was born in telephone quality testing. A group of people would listen to calls and each would rate them on a scale from 1 to 5. The average of those ratings was the MOS. The ITU (International Telecommunication Union) describes this kind of assessment in its Recommendation P.800.
The classic scale looks like this:
| MOS | Quality |
|---|---|
| 5 | Excellent |
| 4 | Good |
| 3 | Fair |
| 2 | Poor |
| 1 | Bad |
In practice, not even a perfect call reaches 5, because voice compression and the limits of the channel take something away. That is why the highest real-world values for a conventional voice call are around 4.3 or 4.4.
Estimating MOS without asking anyone
Having people listen to calls is no use for measuring a network in real time. So the ITU developed the E-model (Recommendation G.107), which calculates a score called the R-factor from network characteristics such as delay and packet loss. The R-factor runs from 0 to 100 and is then converted into a MOS value.
The idea is intuitive: start from maximum quality and subtract points for each problem.
- Delay costs little while it is low, but past a certain point it starts to cost a lot, because the conversation becomes awkward.
- Jitter is treated as extra delay, because the app has to wait longer to compensate for it.
- Packet loss costs a lot, because every lost packet is a piece of voice you never hear.
How SuperPing calculates MOS
SuperPing uses a simplified version of the E-model that is common in monitoring tools:
- It calculates an effective latency: average latency, plus twice the jitter, plus a small fixed margin for processing.
- It starts from a maximum R-factor and subtracts points based on that effective latency. While effective latency is low, it subtracts little; past a threshold, it subtracts much more.
- It also subtracts 2.5 R points for each percentage point of packet loss.
- It converts the final R-factor into a MOS between 1 and 4.5.
The result appears in Current quality, on each target's card and in the MOS chart in the Metrics section, with these colors:
| MOS in SuperPing | Color | What to expect |
|---|---|---|
| 4.0 or higher | Green | Clear calls. |
| 3.1 to 3.9 | Orange | Some noticeable gaps or delay. |
| Below 3.1 | Red | Calls that are hard to keep going. |
What SuperPing's MOS is not
It is important to be clear about its limits:
- It is an estimate. It does not analyze a real call, only the conditions of your connection.
- It uses browser measurements. SuperPing's latency includes the browser's work for each web request, which is usually a bit higher than for voice packets. So the MOS may come out a little lower than a professional tool would measure.
- It does not measure to your calling app's server. It measures to reference servers such as Google or Cloudflare.
Even with these limits, it works very well for what matters day to day: knowing whether right now is a good time for a call and spotting the hours when your connection gets worse.
How to use MOS day to day
- Before an important meeting, check MOS in SuperPing. If it is green, join with confidence. If it is orange or red, see what is dragging it down: if it is jitter or loss, try a cable or pause downloads.
- To find patterns, use the 24-hour view of the MOS chart. If it always drops at the same time of day, it may be congestion at your provider.
- To compare networks, measure MOS in different places or with different providers. It is a simple way to compare with a single number.
In short
MOS turns latency, jitter and loss into a single score from 1 to 5 that represents call quality. SuperPing estimates it with a simplified version of the ITU E-model: it is not a certified measurement, but it is a quick, useful reference to decide whether your connection is ready for a call.
To understand each ingredient on its own, read what is latency, what is jitter and packet loss.